Choosing Access Request Approvers
Key Takeaways
Standard Manager approval uses the access recipient’s manager.
An owner stage resolves against the requested item. All Owners means any one eligible configured owner, and a governance group stage can be decided by one eligible member.
Required reviewer stages run in the configured order. A denial ends the review for the item.
For default self-approval protection and a missing reviewer, test the documented alternate routing with real identity data.
Choose the reviewer by responsibility
Pick the approver from the business question. A manager evaluates whether the recipient needs access for their job. The requested item’s owner can assess whether the access is appropriate for the system or policy it represents. A governance group gives an eligible member authority to act for that group. For a standard role or access profile request, choose Reviewer in the item’s Access Requests configuration, select the reviewer types, and order the stages. For an individual entitlement request, confirm whether the global entitlement approval or the individual entitlement’s configuration applies. The set of choices depends on the item and approval mechanism.
| Requirement | Standard role or access profile reviewer category |
|---|---|
| Determine whether a worker needs the access | Manager of the identity receiving the access |
| One accountable role or profile owner must act | Primary Owner of the requested item |
| Any configured owner may act | All Owners, with one required decision from a primary or additional owner |
| A secondary owner should act | Additional Owners, with one required decision at that stage |
| An independent team should review | Governance Group, with one eligible member making the group decision |
Place the recipient’s manager first if the owner should see only requests that pass the business-need check. Add a separate stage for the owner, and retain independent oversight if the design calls for it. Sequential routing sends the request to reviewers in the chosen order. It requires approval at each required stage before access can be granted. The assigned member or owner acts for their stage. If that reviewer denies the request, stop expecting a target grant for that item.
Work an owner and manager route
Suppose an employee in Procurement submits a request for an eligible Finance analyst. A standard role’s approval order is Manager and then Primary Owner. The analyst’s manager is the first reviewer under that setting. The role’s owner is second after approval. If that role contains a Ledger Read access profile whose own request settings use a different owner, the role request still uses the role process. Requesting Ledger Read directly would call for checking the profile’s own configured review path. Automated profile grants from a lifecycle state or automatically assigned role follow the assignment trigger, without that direct access request approval.
If the requester or recipient is assigned as an individual reviewer, the documented default self-approval protection reassigns the review to that person’s manager. If they are a member of a governance group reviewer, exclude them from that review under the default behavior. When that leaves no eligible group member because they were the only member, the assignment goes to their manager. If requester and recipient are the only two members, both managers receive reassigned reviews. SailPoint also documents an optional application programming interface (API) setting called autoApprove for applicable requester reviews. Inspect the actual policy when a review appears to pass automatically, including whether non-skipped required stages still apply.
Resolve a missing reviewer and identify alternate mechanisms
An initially unresolved reviewer has different routing from an idle reviewer waiting for escalation. SailPoint documents the first valid candidate in this order: the missing reviewer’s manager, the next new identity in the escalation chain, the fallback approver, the requested item’s owner, and an org admin other than the default support admin. An already assigned approver is skipped in this resolution. Verify the access object’s owner and the actual manager relationship when testing this branch. Separate this from the timeout schedule after a valid reviewer receives the work.
If the requirement needs conditional routes, a compatible enabled Workflow with an Access Request Submitted trigger can be selected for role or profile approval. In applicable tenants, Access Request Policies in Policy Center can also determine a decision or approval route for matching requests. Check whether such a policy applies and whether it honors the existing static configuration. Scope a lab example to one mechanism and verify the actual reviewer in Access Request Activity. A workflow reviewer selector or a request policy can have different choices from the standard reviewer list shown above.
See SailPoint’s role and profile approval options and routing, entitlement approvals, and access request policies.
An eligible requester submits access for another employee. The requested role uses Manager as its first reviewer. Both people have distinct managers, and no self-approval or other override applies. Who receives the first review?
The manager of the employee receiving access
The requester’s manager
The source service account owner regardless of the item
All members of the requester’s segment
A request uses an independent governance group first and the role’s primary owner second. One eligible member approves for the group. What happens next in the configured review sequence?
All group members must now approve before the request advances
The access is already fulfilled, and the role owner gets a receipt
The role’s primary owner receives the next required review
The recipient chooses the next reviewer in the source account selector
Sections you finish are checked off in the contents.