...
Specific permissions such as Edit Next Review Date, Last Review Date and Review Frequency must be present after activating the setting ‘Control Review’ within the Role Management > Controls Product Tree. Previously if the Control details > Edit permission is ticked, then by default, the new permissions will also be ticked for the user. If the setting is deactivated from Control settings, the new set of permissions will be disappeared from the Role management.
...
Specific permissions such as Edit Next Review Date, Last Review Date and Review Frequency must be present after activating the setting ‘Control Review’ within the Role Management > Risk Product Tree. Previously if the Control > Edit permission is ticked, then by default, the new permissions will also be ticked for the user. If the setting is deactivated from Control settings, the new set of permissions will be disappeared from the Role management.
...
Specific permissions such as Edit Next Review Date, Last Review Date and Review Frequency must be present after activating the setting ‘Control Review’ within the Risk Settings > Standard Roles > Control node. Previously if the Control > Edit permission is ticked, then by default, the new permissions will also be ticked for the user. If the setting is deactivated from Control settings, the new set of permissions will be disappeared from the Standard roles as well.
Further these permissions will be extended to Compliance > Controls Object User Role and for the ‘Control Creator’ static role.
A new snippet named ‘Review Frequency’ is introduced within controls notifications area when during the design of the templates.
...
Permissions will be restricted for the specific user in union of the roles he/she has in place, hence for example when ‘Control Review’ is activated editability of the i.e. Next Review Date can be restricted for the user to be editable.
Further, the control review frequency value can be utilized for your control email notification templates.
...