For Customers with ‘Workflows’ enabled, content changes can be controlled so that Users who do not have publishing rights can pass their changes to Users with publishing rights for review and approval.

Content edits made by some Users may be subject to an approvals process prior to publishing, if ‘Workflows’ are enabled on a Site. Workflows force content changes made by Users without publishing rights, such as Project Authors, to be submitted for review to Users with publishing rights, such as Project Leads, Team Leads, and Site Administrators.

The Workflow process is as follows:

1. The ‘Requester’ (e.g. Project Author) submits proposed changes as part of a new page version by selecting on ‘Submitting to Workflow’.
2. The ‘Approver’ (e.g. Project Lead) receives an email notification alerting them that changes have been submitted to them for review.
3. The Approver visits the amended page (e.g. by following the link in the email or navigating to the ‘Workflow’ area of the Dashboard) where they can compare the proposed version with past versions, ‘approve’ the changes, or ‘reject’ the changes.
4. If a Requester’s changes are approved by the Approver, the changes will be published and the Requester will receive a notification of the successful approval. If the changes are rejected, the Requester will receive a notification of the unsuccessful changes, with the Approver able to provide a message to the Requester letting them know why the changes have been rejected.