I created a custom User Level, however I am not able to view it as an Entitlement, add it to an AP, etc. I can add directly to a user though under the User Level tab. Is anyone else having this issue?
From what I understand, custom User Levels don’t always show up as entitlements in the same way as standard access items, which is why they’re not visible when trying to add them to Access Profiles.
Being able to assign them directly under the User Level tab but not use them in APs usually indicates they are handled differently in the model.
You might want to double-check if there’s any additional configuration or mapping required to expose them as entitlements, or if this is a limitation of how custom user levels are treated.
@michael_mckeehan We created a custom user level in our tenant, and it does show up under Entitlements, but it appears with the custom user level ID instead of the name.
Could you please check if it’s the same in your case?
This is actually expected behavior in SailPoint Identity Security Cloud.
Custom User Levels are not treated as entitlements, so they won’t appear:
In Entitlement catalog
In Access Profiles (APs)
In role composition
They are managed separately and can only be:
Assigned directly to users
Managed via the User Level tab
That’s why you’re able to assign it to a user but not see it elsewhere.
If your goal is to include this in access requests or roles, you’ll need to model it as an entitlement (e.g., group/permission from a source) instead of a User Level.
So nothing wrong with your setup — it’s just how ISC currently handles User Levels.
Sharing an update that’s relevant here. Custom user levels can now be requested through Entitlements as part of the new enhancement SailPoint announced here: Enhancement: Custom User Levels. But the Production rollout has been pushed to TBD. Sandbox has it as of Apr 20, Production will follow whenever SailPoint reschedules.