A newly created entitlement is not showing up in Identity Security Cloud.

Waiting for an identity refresh is not the correct remediation for a missing source entitlement. Identity processing and entitlement aggregation perform different functions. Identity processing recalculates identity-related information and access relationships based on information already known to Identity Security Cloud; it does not independently discover a newly created entitlement that has never been successfully loaded from the external source.

New entitlement objects are discovered through entitlement aggregation or through supported account aggregation behavior, depending on the source and connector. SailPoint defines entitlement aggregation as the process of loading entitlement data from an external source into Identity Security Cloud. The completed aggregation records how many entitlements were discovered.

If an expected entitlement is absent, the administrator should inspect the source's entitlement configuration and schema, review aggregation status/history, confirm that the external entitlement exists, and run or troubleshoot an entitlement aggregation. SailPoint's troubleshooting guidance specifically directs administrators to perform entitlement aggregation when entitlement metadata is not being imported correctly.

Study Guide Reference: Sources — Entitlement Aggregation, Entitlement Schemas, Aggregation Troubleshooting and Identity Processing.