Release 3.6.1197

Release date: 9 Oct 2019

New Features

App Permissions can be defined based on assigned Group

App permissions define the permitted operations that the app can perform. In this release, App permissions can be defined based on the group it is assigned to. In this way, users can tightly control what operations an app can perform within a specific group.

To define app permissions at the app level, go to Apps, click on the app to edit. This will bring up details of the app. Click on App Permissions to edit. Each group (that the app belongs to) can have a different set of permissions assigned to it.

App permissions can also be defined at the group level. Go to Groups, click on the group which the app has been assigned to. Under the apps tab, click on the permissions of the selected app to edit it.

Enhancements to existing functions

Improvements to Approve/Reject Request for Sensitive Operations

Previously, if the requestor and approver is the same person, approval for sensitive operations can be skipped. Now, an explicit request is created for all sensitive operations. If the user requests for a sensitive change that needs to be approved, and he himself is an approver, he needs to explicitly approve the change before it can happen.

Display Deactivated and Compromised Security Objects

By default, the security object table view will only display Pre-active and Active states. In this release, when you click on Show all, Deactivated and Compromised states will be displayed as well.