Hi Team,
We are currently testing Access Segments in our POC environment. Before raising this question, we reviewed the SailPoint documentation and searched the developer community for similar issues. However, we are still experiencing unexpected behavior.
What we tried
-
Created an Access Segment and added 3 entitlements to the segment.
-
Verified that the segment was correctly applied and the entitlements were visible in the Access Request page.
-
Deleted the Access Segment from the environment after completing our testing.
-
Verified that no segments currently exist in the tenant.
-
Waited for propagation (segments were deleted on Friday and verified again on Monday).
-
Logged out and logged back into the tenant to rule out UI caching issues.
Current behavior
There are no explicit errors displayed in the UI.
However, the Access Request page still displays only the same 3 entitlements that were originally defined in the Access Segment, even though the segment has been deleted.
Expected behavior
After deleting the Access Segment, the segment-based restriction should no longer apply, and users should be able to see all available requestable entitlements in the Access Request page.
Question
Could anyone please help us understand why only the previously segmented entitlements are still visible even after deleting the Access Segment, and if there are any additional steps required to refresh or re-index the Access Request catalog?