New article
Recently updated
12.0 Permission developments
Who is this article for?Users who want to learn more about 12.0 permission enhancements.
No elevated permissions are required.
This article highlights the latest developments in permission management introduced in 12.0. With enhanced features, users gain more precise control over access rights and administrative functions, contributing to improved system security and streamlined user management processes.
1. Audit users
1.1 Annual planning permissions
| Permission | Description |
|---|---|
| Allow read-only access to Key Risk mapping |
Allows users visibility of Key Risks under any Status. Editing of Key Risks is not possible. Entity Access Restrictions will affect which Key Risks are available, based on the level of mapping applied. |
| Allow read-write access to Key Risk mapping |
Users have editability of Key Risks under any Status. This includes the ability to change the status to Active. Entity Access Restrictions will affect which Key Risks are available, based on the level of mapping applied. |
1.2 Audit creation and review permissions
| Permission | Description |
|---|---|
| Delete audit associated attachment prior versions | Allows users access to this component of the Manage audit associated data utility, where users are able to clear the revision history of all audit attached files. Please note that performing this activity for Closed audits will require the additional permission: Manage audit associated data for closed audits. |
| Permanently delete audits |
Allows users access to Help, Customer Support, Ideagen Support then Permanently delete audits from the database. Important: Once audit data is permanently deleted, it cannot be restored. |
1.3 Audit creation and review section access
| Permission | Description |
|---|---|
| Mapped Key risks | Allows users visibility of the Key risks tab within a standard audit file layout. This area of the system is read-only by default. |
1.4 Maintenance permissions
| Permission | Description |
|---|---|
| Configure key date methodology |
Allows users editable access to Tools, Methodologies and Key Date Configuration, where all settings related to Key Dates are stored. Note: This permission replaces two previous permissions: Key Date Maintenance and Key Date Rules Maintenance. |
1.5 Permanent file permissions
| Permission | Description |
|---|---|
| Allow read-only access to permanent files | Allows users visibility of Permanent Files from any supported Attachments tab in the system. Editing of Permanent Files content and details is not possible. Entity Access Restrictions will affect which Permanent Files are available, based on the entity link applied. |
| Allow read-write access to permanent files | Allows users editability of Permanent Files content only from any supported Attachments tab in the system. Entity Access Restrictions will affect which Permanent Files are available, based on the entity link applied. This new permission does not automatically inherit the ability to Delete permanent files or Edit permanent file details. These tasks remain governed by standalone permissions. |
1.6 Recommendation and action tracking permissions
| Permission | Description |
|---|---|
| Access to Recommendation reports | This permission has been removed in Version MK 12.0. Due to the migration of all Recommendation reports into Template Designer then Reports, governance over their use is therefore controlled via Generate access rights on a User, Role or Team basis. |
| Remove Recommendation editable access lock |
Only available when using the client application, this permission allows users the ability to remove the local editable copy of a Recommendation (or Risk Action) from the current editor. Note: With new lock management efficiencies this applies to items opened within the client and online and should never be used unless the local editable copy cannot be recovered from the current editor via best practice Secure backup procedures (or via Update and Close online). |
| Request Recommendation update note | Allows users access to the Request update functionality within Update Notes. When disabled, users will have visibility of the button, though it will be greyed-out for use. |
2. Risk users
2.1 Approve risks
| Permission | Description |
|---|---|
| Draft, Submit & Require Approval | This option ensures that, following the initial Approval of a new Risk, where users make further changes to the Risk is must be Approved again before Assessments can be carried out |
2.2 Recommendation and action tracking permissions
| Permission | Description |
|---|---|
| Enable Implement Control | Allows users to perform the Implement function against Proposed Controls, moving them to the list of active Controls. |
| Move recommendations to a different entity | Allows Risk Actions to be moved and associated to a different Risk. |
| Remove Recommendation editable access lock | Only available when using the client application, this permission allows users the ability to remove the local editable copy of a Recommendation (or Risk Action) from the current editor. Please note that with new lock management efficiencies this applies to items opened within the client and online and should never be used unless the local editable copy cannot be recovered from the current editor via best practice Secure backup procedures (or via Update and Close online). |
| Request Recommendation update note | Allows users access to the Request update functionality within Update Notes. When disabled, users will have visibility of the button, though it will be greyed-out for use. |
2.3 Risk details permissions
| Permission | Description |
|---|---|
| Allow removal of user reassignment on submitted risk assessments | Allows users the ability to Remove user assignment within the risk assessment details page, when Risk Assessments have been sent to a specific person for approval. |
| Allow removal of user reassignment on submitted risks | Allows users the ability to Remove user assignment within the risk details page, when newly created Risks have been sent to a specific person for approval. |
2.4 Search and logging permissions
| Permission | Description |
|---|---|
| Search the system | Allows users access to Support, Internal Audit Tools and Search the System, which is an online tool that offers the same functionality provided in the client application.Note: Search results shown here will also relate to Audit activity and, where attachments are found, these can be downloaded and viewed by the user. |
3. Business users
3.1 Recommendation and action tracking permissions
| Permission | Description |
|---|---|
| Access to Recommendation reports | In Version MK 12.0, access to Recommendation reports has been removed. All Recommendation reports are now migrated to Template Designer then Reports, where access is controlled via Generate access rights on a User, Role, or Team basis. |
| Allow deletion of Recommendation attachments | This permission grants users the ability to delete existing and/or new attachments. When disabled, the Delete button is completely removed from the screen. |
| Allow standard reports | The permission to access standard reports has been removed in Version MK 12.0. Similar to Recommendation reports, standard reports are migrated to Template Designer then Reports, and access is managed via Generate access rights on a User, Role, or Team basis. |
| Allow business user to access Planet MK | Enables access to the Planet MK Home page, Online Support videos, and Planet MK Forum where various user manuals and technical installation guides are available for download. |
| Remove Recommendation editable access lock | This permission, available only when using the client application, allows users to remove the local editable copy of a Recommendation (or Risk Action) from the current editor. It should be used cautiously and only if the local editable copy cannot be recovered via Secure backup procedures or Update and Close online. |
| Request Recommendation update note | Grants users access to the Request update functionality within Update Notes. When disabled, users can see the button but it will be greyed-out and unavailable for use. |