Access Segments deleted but still restricting entitlement visibility in Access Request

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?

Hi @Yashwanti

This usually happens when the Access Request catalog hasn’t refreshed after the Access Segment was deleted.Even though the segment is removed, the catalog can still keep the earlier configuration, so it continues to show only those entitlements

Run a Catalog Refresh from the Access Request.If the issue still persists, run an Application Aggregation so the entitlements are re-indexed.

After the refresh, the Access Request page should show all requestable entitlements again instead of just the three from the deleted segment.

1 Like

Thank you @kallajayaram

How do I perform this catalog update? I couldn’t find this option in the menus

Hi @victorzx123
Reset the entitlement status, and the issue should be resolved

If I perform a reset entitlements on the source, will they be removed from my roles and access profiles?

Hi @victorzx123 ,

Reset entitlements won’t remove your Roles or Access Profiles

Hi @kallajayaram

Jaya, maybe I’m not understanding, but if I perform a reset of entitlements on the source, all entitlements are deleted and consequently removed from access profiles and roles. Which reset are you referring to? Could you please help with screenshots and the documentation?

1 Like

Is that even a thing, or did your AI hallucinated?

1 Like

I’m referring to the entitlement reset at the source and reaggregation into SailPoint
The reset temporarily clears entitlements, and after aggregation they are imported again from the source. This does not delete Access Profiles or Roles, but entitlements and their associations may change based on the source data.