Applying Access Request Segments
Key Takeaways
Segments connect mapped identity criteria to visibility of requestable roles, access profiles and entitlements.
An ordinary requester can see items in their matching segments and requestable items assigned to no segment.
Visibility follows the requester. A separate policy controls on-behalf eligibility, and org admins have a documented Request Center exception.
Before disabling a segment, check whether another enabled segment still includes each affected item.
Use a segment when the catalog should differ by audience
A segment groups identities by mapped attributes and limits the visibility of designated access items for ordinary users in the Request Center. Use it when only a defined audience should see a specialized requestable role, access profile, or entitlement. A location-specific inventory system is a typical example. A common company directory profile can remain outside all segments so otherwise eligible requesters can still see it. The item must be requestable and the access request service must be available for the example to work.
Keep the business question concrete. If warehouse staff should see a specialized inventory item, use a segment for the request catalog. If every active warehouse worker should receive the item automatically, design the applicable role assignment or lifecycle configuration. If the organization needs separation of duties before granting an item, use the appropriate conflict policy and review process. Catalog segmentation alone establishes which requests can be discovered and submitted within the documented Request Center setting. Fulfilled access and eligibility on someone else’s behalf are separate. For a requirement about which records delegated administrators can see, evaluate the tenant’s separate Data Segmentation feature. The Request Center audience rule applies to requestable items.
Configure criteria and access
Go to Admin > Access Model > Segments. Create a named segment, add mapped identity attribute values under Define Segment, and inspect the resulting member list. If the necessary attribute is absent, map it into the identity profile first so it can be used for segmentation. SailPoint supports one value per identity attribute in a segment and directs administrators to use separate segments for OR comparisons. Under Define Access, find the appropriate item and add it. Review identities and access together, save, and enable the segment.
Consider an item named Inventory Batch Reconcile, which should be visible to ordinary requesters with Region East or Region West. Define East and West as separate enabled segments and place the same requestable item in both. Leave the independently requestable Company Directory item outside all segments. The example assumes the requester tests the Request Center after changes have taken effect and that no separate restriction affects the two items.
| Requester or change | What to expect for the two items |
|---|---|
| Ordinary East user | Sees Batch Reconcile through East and sees the unsegmented Directory |
| Ordinary West user | Sees Batch Reconcile through West and sees Directory |
| Ordinary North user | Sees Directory only |
| Org admin in North | Can see and submit for segmented items in the Request Center under the documented org-admin exception |
| East segment disabled, West still includes Batch Reconcile | Batch Reconcile remains restricted by West |
| Both segments disabled and no other segment includes Batch Reconcile | Batch Reconcile is visible to otherwise eligible requesters as an unsegmented item |
An East manager allowed to make requests for their direct reports can see Batch Reconcile and can submit it for a direct report authorized by the on-behalf setting. That report might have a different Region. Segment visibility follows the requester’s membership, so use a separate approval or eligibility control if the recipient’s region must also be enforced. Test the recipient restriction separately from the visibility test and verify the exact account selected for the request.
Verify changes with real user roles
After editing a segment, SailPoint says changes may take about 20 minutes depending on activity, volume and the item type. Entitlement visibility can take longer to synchronize than roles or profiles. Check that the segment is enabled and that the requester’s mapped attribute value has the expected data. Verify the item really belongs to every intended segment. Use a non-admin member, a non-admin nonmember and an org admin control to isolate the documented exception. If there is a second segment, inspect that membership and its status before interpreting visibility as a defect.
Disabling or reclassifying a segment is a catalog configuration change. Check who may newly see and request the item before making that change. For someone who already holds the entitlement, use the assignment record and appropriate revocation path to address current access. Confirm the requester’s visibility, ability to submit on behalf of a given person when relevant, and approval behavior as distinct tests after enabling the final design.
See SailPoint’s segment configuration and exceptions, requests for others, access request overview, and Data Segmentation settings.
An ordinary East manager can see a profile limited to the East segment. Requests for others are configured for managers and their direct reports. A North worker is this manager’s eligible direct report. What follows from the documented access request visibility rules?
The profile is hidden from the manager because the recipient is in North
The profile must be granted automatically to the report
The report’s North membership cancels the manager’s authority to submit a request
The manager can submit for the report because the manager can see the item and is authorized to request on the report’s behalf
A requestable item appears in two enabled segments. An admin disables one, and the other still contains the item. What is the visibility result for ordinary Request Center users?
The item becomes available to all ordinary users immediately
The remaining enabled segment continues to restrict item visibility
Existing assignments for disabled-segment members are automatically revoked
The item is moved into an identity profile
Sections you finish are checked off in the contents.