What permissions are required to Create Change Requests from Reviews using RSA Identity Governance and Lifecycle?
Originally Published: 2019-03-14
Article Number
Applies To
RSA Version/Condition: All
Issue
Resolution
Change Requests may be generated from a review in one of two ways:
- Automatically, or
- Explicitly by Owner.
The "Generate Change Request: Explicitly by Owner" is an implicit permission that is granted to the Review Owner. It allows some different grouping to be selected when creating the Change Request for review items that reviewers select to revoke. There is no need for any additional permissions to be added.
The "Generate Change Request: Automatically" option allows the Change Request to be created when the Reviewer or the sign-off person saves the Review. The person who saves the review will be the Requestor of the change request. There is no need for any additional permissions to be added.
Monitors that have write_access or admin can also perform the review and when they save the review a change request is created using the revoled items. No need for any additional permission as well.
Related Articles
Impact of missing information on creation of Profiles by Risk Engine 25Number of Views Supported browsers to access the RSA Web Threat Detection user interfaces 13Number of Views SELinux support for RSA Authentication Agent 7.1.0.1 for PAM on Red Hat Enterprise Linux 56Number of Views RSA Identity Governance and Lifecycle Change Request created without required Create Account item 120Number of Views Change Requests Do not Include Indirect Entitlements When Users Are Removed From Roles via Rules, Reviews, or User Access … 44Number of Views
Trending Articles
How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?