Assign each step in the workflow an approval level that reflects your organization's decision process and hierarchy. For example, if you review first for readability, grammar, and spelling, then for graphical appearance, then for legal compliance, and require a final approver before publishing, you would assign the copy editing group approval level 1, designers level 2, the legal department level 3, and the publisher level 4, the highest approval level. You can use as few or as many additional levels as needed, to support your organization's processes, as shown in the Approval Levels dialog, or use none at all.
For example, a collection of "internal-only" pages might require level 1 copyediting approval only or none at all.
Members of a group that's responsible for approval can approve on submit.
If two or more groups are final approvers on a page, one member of each group must approve the page before it can be published.
Once the highest level approver OKs a change and submits it, content is published and available to all users with read access. When there are multiple groups within each level, one person from each group needs to approve it to pass that level or to publish.
Best Practice Notes:
Note that assigning the highest level approver status to multiple individuals or groups requires approval from each approver before content can be published. For this reason PaperThin recommends using groups to implement an approval hierarchy to forestall bottlenecks and prevent unexpected behaviors.
For example, when you want *either* of two groups to be final approver, create an approval group that includes both groups in it.
Related Links
You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).
For technical support: