A Document can be pushed on to in the workflow/ rejected back to specific status at various stages in the Approval Cycle.
The available options for users in the current review cycle can vary depending on which roles you have set up in your document/ document type.
An Author can:
- Download the Document (unless this option is blocked)
- Edit the Document roles
- Edit the Document
- Update permitted Document Settings
- Set to Under Signing by Reviewer/ Under Signing by Approver/ Under Signing by QA/ Set to Approved not Published
A Reviewer can:
- Download the Document (unless this option is blocked)
- Edit the Document roles
- Edit the Document, (whether edits are made or not by the Reviewer the Author will move to Undersigning by Author status should the Author make further edits before the Reviewer signs off).
- Update permitted Document Settings
- Print the Document
- Set to Under Signing by Approver/ Under Signing by QA/ Set to Approved not Published
- Reject to Draft
An Approver can:
- Download the Document (unless this option is blocked)
- Edit the Document roles
- Edit the Document
- Update permitted Document Settings
- Set to Undersigning by QA/ Set to Approved not Published
- Reject to Draft (the Author)
- Reject to Under Review (if you have a Reviewer role)
A QA can:
- Download the Document (unless this option is blocked)
- Edit the Document roles
- Edit the Document
- Update permitted Document Settings
- Set to Approved not Published
- Reject to Draft (Author)
- Reject to Under Review (if you have a Reviewer role)
When a Document is rejected, a Reason must be given for rejecting the Document.
Users who have a role in the Document will receive notification by email, the email will include the details on who rejected the Document and the reason why it was rejected.
Besides the email notification Users can also consult the Audit Trail to see when a Document was rejected, by who it was rejected and for what reason.
Relevant for: Administrators / Managers / Regular Users