Designing Access Request Tests

Key Takeaways

  • Test visible and hidden items using ordinary requester identities in the relevant segments.

  • Test requests for self, authorized direct reports, and someone outside the configured on-behalf scope.

  • Capture the expected approval sequence for the requested item and verify the target independently.

  • An allowed request for a person with multiple source accounts requires a separate account selection check.

Last updated: November 2026

Start with who can request what for whom

Write the expected outcome in terms of a requester, recipient, requestable item and account. The requester acts in the Request Center. The recipient is the person for whom the target access is intended. In a request for oneself they are the same person. For a request submitted for another person, check whether the requester may see the access item and submit on behalf of that recipient. Those decisions depend on different tenant settings.

In the following sandbox, ordinary payroll users can see the Payroll Inquiry access profile because it is requestable and included in an enabled payroll segment. Requests for others are configured as By Managers for their Team. The standard profile approval sequence is the recipient’s manager followed by an independent payroll governance group. Assume no customized workflow, Policy Center rule, or automatic approval applies. This makes the intended sequence explicit. Pilot a normal requester and a payroll manager with a confirmed direct report. Include an ordinary user outside payroll and an active person outside the manager’s team. Use an ordinary session for each requester case. Org admins have a documented visibility exception that would invalidate a negative visibility result.

TestExpected evidence
Payroll worker requests for selfItem visible, submission identifies that worker as requester and recipient
Nonpayroll worker opens Request CenterPayroll Inquiry absent for this ordinary session
Payroll manager selects a direct report in scopeReport selectable; submitted request records manager and report separately
Same manager tries an unrelated active workerUnable to select or submit for that person under the stated on-behalf setting
All required reviewers approveApproval record shows the sequence and the approved item proceeds to its configured fulfillment path
A required reviewer deniesDenial closes the approval chain for that item; compare native target membership with the baseline
Direct report has two target accountsRequester chooses the intended account by account name and ID; verify the other account is unchanged

Choose the reviewer case deliberately

The payroll manager can request for their direct report, but also happens to be the configured first reviewer for that report. Under default self-approval prevention, the individually assigned review is reassigned to the manager of the original reviewer. Test with that identity present. Confirm the alternate reviewer, then confirm the independent payroll group receives its step only after the first required approval. One eligible member acts for a standard governance group step. Use a separate request with a different requester to test the ordinary unmodified sequence. A missing manager relationship would introduce yet another routing condition, so confirm the exact identity context before comparing results.

If the thing submitted is a role composed of Payroll Inquiry, use the role’s configured approval, rather than assuming the profile’s direct-request approval applies. Request the profile directly to exercise its own approval path. Hold the actual assignment type constant across a test of reviewer rules. For an automatically assigned role or lifecycle profile, plan a separate test of the trigger and resulting write.

Verify access and failure at the right stage

Record the submission and decision in Search > Reports > Access Request Activity or with the access-request events. Match the request to the recipient and item. Inspect Account Activity or the relevant manual task when diagnosing fulfillment. Read the native payroll source and compare both accounts to the expected result. A reviewer action alone establishes the approval decision. A direct connector can still encounter a write failure. If the assignment is scheduled to start later, check the actual start date before calling a lack of immediate provisioning an error. Use a standing grant with no future start date if the purpose is to test immediate eligibility for fulfillment. For a separate timed-access case, record the actual selected end date, time, and time zone. The documented Request Center allows quarter-hour time selection and defaults the zone to the browser’s, which the requester can change. Verify actual removal against the saved access end time. Use approval history separately to establish how the request was reviewed.

A current Policy Center Test Impact simulation, if available, is useful for matching inputs to a single access request policy. SailPoint documents that the simulation evaluates that policy alone. When using the feature, also execute a representative request through the applicable path to capture interactions with other policies and native delivery. Keep expected outcomes separate so a successful simulation, or a test using an admin session, does not stand in for user-visible acceptance.

See SailPoint’s access request flow and policy simulation, requests for others, role and profile approvals, segments, provisioning tracking, and Request Center time selection.

Test Your Knowledge

A standard Payroll Inquiry profile request for a direct report has passed every required approval. The requester selected the report’s ordinary account from two choices. Which evidence completes the fulfillment test?

A

The submitted request appears in the manager’s history

B

The payroll governance group was contacted

C

The provisioning result and native readback show the intended change on the ordinary account and no change on the other account

D

The privileged account was visible in the list of choices

Test Your Knowledge

Requests for others are limited to By Managers for their Team. An ordinary payroll manager can see a profile and wants to test the boundary. Which cases should they compare?

A

Request for their own direct report versus a comparable active employee outside their team using the same visible item

B

Request for two direct reports with the same source account

C

Compare a profile approval and a role approval for the same direct report

D

Test only with an org admin session

Sections you finish are checked off in the contents.