In rare cases, you may find that a user does not appear within certain ‘Assign’ dropdowns within individual Improvement Logs, or that they cannot complete certain actions that you would expect to be available to a user with their permission level. For example, you might find that:
- they can raise Improvement Logs, but can’t edit, cancel, or close them;
- they can edit Improvement Logs, but can’t mark them as ‘approved’ or ‘under review’;
- they can close Improvement Logs, but can’t reopen them;
- they can set up Effectiveness Assessments, but can’t complete those assessments;
- etc
Under usual circumstances, all of the above actions should be available to anyone who has ‘Edit’ or higher permissions to the Improvement Log module and who can access the specific Improvement Log they are attempting to modify. However, uniquely amongst Activ’s modules, the Improvement Log module includes a set of secondary permissions that can prevent users from completing specific actions, if those secondary permissions are modified.
By default, the module’s secondary permissions are set up to match the expected behaviours of Activ’s standard permissions, meaning that all of the actions listed above can be completed by any ‘Edit’ user, and deletion rights are given to all ‘Admin’ users. However, each of these settings can be modified such that:
- the relevant actions become locked to ‘Admin’ users;
- the relevant actions become locked to the Improvement Log’s creator or owner; or
- the relevant actions become locked to one or two specifically named users within the system.
Where this is the case, only those who match the new criteria will be able to complete the corresponding actions. For example, if ‘permission to edit improvement logs’ is locked to ‘owner’, the Improvement Logs within your system will only be editable by the user that they have been assigned to. Similarly, if ‘permission to close Improvement Logs’ is locked to ‘Bob’, only Bob will be able to close your system’s Improvement Logs.
It is important to be aware that these settings impact all Improvement Logs within your system, and that there is no way to mark certain logs as ‘exempt’ from the secondary permissions. As such, if you have modified the Improvement Log’s module-specific permissions and need to enable a user to complete additional actions, you will need to either:
- restore the relevant secondary permission to its default setting; or
- modify the relevant secondary permission to include the user within the list of authorised individuals.
See Action Specific Permissions for more information.
