Role Assignments, Provisioning, and Removal
Key Takeaways
Identity Security Cloud supports standard roles and dynamic roles with dimensions.
Standard Criteria, Identity List, and access requests produce role assignments with different removal paths.
Removing an assignment preserves entitlements supplied by another assigned role, and entitlement removal leaves the source account.
Role access removal propagation applies to certain definition edits on enabled roles. Check it separately from removing an identity’s assignment.
Separate the role’s content from the assignment
A role groups related access for a job or function. It can include entitlements and access profiles from multiple sources. A standard role supplies the configured access for its assignments. A dynamic role can add access through dimensions, such as providing a retail role’s shared access plus the access appropriate to a particular store. Determine who should receive the role separately from which access is included. Role discovery can use observed access patterns to propose candidate roles. Have the business owner validate proposed access and remove unnecessary items before assignment. For instance, if copying the observed access of similar analysts suggests an infrequently used administrative group, review that group with the entitlement owner before adding it. Existing usage can reflect exceptions or historic assignments. Test the proposed role against the current job requirements and include an explicitly excluded person.
| Assignment origin | How access is granted | How to remove that assignment |
|---|---|---|
| Standard Criteria | Identity processing finds that the person meets configured conditions | Change the relevant identity input or criteria so the person no longer qualifies, then verify processing |
| Identity List | Administrator lists specific identities for automatic assignment | Remove the person from the list, then verify processing |
| Access request | Authorized request for the role follows its configured approval and provisioning | Use an eligible revocation action, such as Revoke Assignment, a manager removal request, or a suitable certification decision |
To configure automatic assignment, edit the role in Admin > Access Model > Roles, use Define Assignment, and choose Standard Criteria or Identity List. For example, Standard Criteria can use a mapped Department and an enabled lifecycle state’s technical name. For an Identity List, maintain named membership. Requests have a separate role setting and approval route. Check actual assignment details before removing access. An employee may retain access through another role or through a separate assignment, so verify the applicable source accounts and grant origin.
Work a temporary assignment and an overlap
A worker is on the Identity List of a short-term Audit Support role. The role supplies Ledger Read and Batch Export, and the worker’s separate Finance role supplies Ledger Read to the same account. When the audit ends, the administrator removes the worker from that list. Once identity processing calculates the removal and the connector completes it, Batch Export should be gone given that no other path grants it. Ledger Read is still supplied by the Finance role. The target account remains.
If Audit Support instead came from an approved request, use the supported revocation for that particular assignment. Editing the role’s Identity List would not remove a requested assignment. If the worker received it through department criteria, removing one membership requires changing the relevant criterion or data so the worker stops matching. For all three cases, validate the chosen assignment, fulfillment status, and the native access. If the business wants to disable or delete the account, that requires a separately supported account operation.
Handle edits to access in an existing role
Editing access within a role definition is distinct from removing a person’s assignment. For example, removing Batch Export from the enabled role itself exercises the tenant’s Enable Role Access Removal Propagation setting. When enabled, specified changes such as removing a directly assigned entitlement or an access profile from an enabled role can propagate removals. SailPoint documents a daily 6:00 p.m. tenant-local propagation schedule and an Apply Changes option on the Roles page. This is a separate processing purpose from the ordinary identity processing windows. Access edits to a disabled role do not propagate when the role is later re-enabled. Verify affected entitlements and any overlapping assignments.
If the propagation setting is disabled, use an explicit removal plan. SailPoint describes assigning a replacement with access that should be retained, removing the old assignment through its actual grant path, and verifying the resulting access before deleting the old role. Disable or delete prevents further assignment and removes role association, while previously granted entitlements can remain. The role disappearing from the catalog is therefore insufficient evidence of revocation. Use the assignment record, processing result, provisioning evidence and target account to finish the check.
See SailPoint’s role management, assignment settings, and role discovery.
A worker is removed from the Identity List of an enabled role. Entitlement E is also supplied to the same account by another assigned role. What is the expected result after successful processing?
Both roles are deleted and the account is disabled
E is revoked because one role no longer includes the worker
E is moved to the worker’s other accounts on every source
E is retained through the other assigned role and the source account remains
An enabled role will stay assigned, but one directly listed entitlement is removed from its definition. No other assignment supplies it. What setting should the engineer check to predict automatic removal after the edit?
The account aggregation deletion threshold
Enable Role Access Removal Propagation for the tenant
An identity profile’s numeric priority
The source’s multiple-account comparison operator
What input can Role Discovery give an access model designer?
A reason to skip reviewing proposed entitlements
Proof that target provisioning for a new role is complete
A proposed role based on access patterns among similar users
A replacement for the target’s account creation policy
Sections you finish are checked off in the contents.