The permissions required for the people who participate in document reviews, depend on the part they play in the process. They are grouped by these activities here:
Administrators who manage the setup of the review processes in their organisations will need to configure document review workflows and other settings in the Administration area. For this they require Administration Editor privileges.
In particular, these permissions are required:
Unless adjusted, document owners are automatically granted full permissions over their documents. The setting which controls this is described below
(Allow Document Owners to perform any action on their documents, regardless of permissions).
If this setting is disabled, document owners will only have the permissions they are granted through user group membership in the OU where the document resides. ‘Editor’ roles like Global Editor (excluding admin) (for all types of documents) or SOP Editor, Document Editor, H&S Editor, etc. (for specific types of documents), include the permissions they will need to perform their job.
Users with the permissions below don’t need to be document owners to manage reviews and review settings but they won’t be directly notified unless they are added to the ‘Notification List’.
Two groups of permissions are particularly relevant:
Permissions to ‘manage review tasks’ -
There is one of these permissions for each type of document (for example, ‘Policies:Manage Review Tasks’, ‘Documents:Manage Review Tasks’, etc.). These permissions are needed to,
Permissions to ‘schedule reviews’ -
Document owners are also the first to be informed when a document becomes due for review so they need permission to view the workflow and intervene in some steps. There is also one of these permissions for each type of document, for example, ‘SOPs:Schedule Reviews’. They are needed to,
Users added in review rounds of a workflow only require ‘viewer’ access to the document that generates a ‘review feedback’ task for them. They can complete a review feedback task by requesting changes to the document (as anyone with viewer access to a document can) or they can state that no changes are required.
Users added in approval step of a workflow only require ‘viewer’ access to the document that generates a ‘review approval’ task for them.
Only users added to the approval step in a workflow can complete a ‘review approval’ task. This makes it easy and safe when a lab director is required to sign off document reviews. No special permissions need to be granted and only the people added in the approval step can perform this step.
There are some settings which predetermine how the system will handle document reviews. They are all configurable at Organisational Unit level and they are discussed in more detail in the user guide, Organisational Unit Preferences. The following preferences are all found by navigating to Administration > Settings > Organisational Unit Preferences.
The Document Control area includes three preferences of interest:
When this preference is ticked, change requests will only require approval. If it is un-ticked, a verification step will be added after any change request is approved.
As stated above, users with permissions to ‘manage review tasks’ can verify an approved change request.
To make the process more traceable, it is also possible to nominate one or more users as ‘verifiers’ and appoint them in the Settings area. When a change request is approved and the verification step is enabled, these users will receive a task to verify the change request (Change Request Verification task). Please see Review Feedback below.
The default workflow for new documents can be set for each type of document in this area.
It is also possible to enforce and lock the chosen workflow on any existing documents of the relevant type in the OU selected.
This is also the area where the review window is set for each type of document. A number of days can be entered to define when to start a review cycle ahead of the next review date.
When the preference, Disable verification step for the document reviews is un-ticked (i.e., the verification step is enabled), a list of verifiers can be set for each type of document in the OU of interest. They will then be issued a task to verify any change requests which have been approved. If this feature isn’t used, no tasks will be generated for change request verifications.
Details on how to set this up can be found in the section, Review Feedback of the use guide, Organisational Unit Preferences.