Selecting SailPoint Administrative User Levels
Key Takeaways
User levels grant permissions within SailPoint. Target entitlements grant access on external sources.
Match duties such as campaign administration, reporting, source management, and request management to documented user levels.
Use the applicable source or record scoping and verify what tenant features change its enforcement.
Test one allowed and one out-of-scope action with the actual user level.
Determine where the permission acts
A SailPoint user level authorizes platform capabilities such as managing certifications, editing access models or viewing administrative reports. The right to edit a payroll group in the payroll system is an external permission on the managed source. An access item in a request, an assigned campaign reviewer, and a tenant user level can all concern the same person. Each has a distinct effect. Decide whether the person needs a platform action, an external application permission or a specific work assignment before selecting access.
Start from the exact action and resource. Determine whether the operator needs to view, create, change or approve. Then check the current user-level permissions and matrix. Grant a level that covers the required action with the appropriate scope. Product licensing and enabled features can affect which controls and resources are present in the tenant. Validate configuration in that actual tenant instead of assuming another organization’s role setup applies.
| Task | User level to evaluate first |
|---|---|
| Create and administer certification campaigns | Cert Admin |
| View and download supported reports and view permitted activity | Report Admin |
| Configure associated sources and their access profiles | Source Sub-Admin plus appropriate source association in the documented governance-group model |
| Manage roles with access from associated sources, or with neither access profiles nor entitlements | Role Sub-Admin and the documented source associations |
| Filter, search and view access requests without changing them | Access Request Read Only Admin |
| Reassign or take other authorized administrative actions on requests | Access Request Administrator |
| Assist with supported password resets and account unlocks | Helpdesk |
Check which sources the operator can reach
Suppose a source operator needs to manage configuration and access profiles on one warehouse source. In the documented governance-group model, configure the Source Sub-Admin user level and ensure the identity belongs to the group associated with that source. Check the permissions for the requested action, including the documented limits on assigning source configuration assignees. Test access to the warehouse source and to an unrelated finance source using the operator’s own session. An Org Admin session would not measure that source boundary.
If tenant Data Segmentation is enabled, consult its record-level access settings. SailPoint applies assigned segments to record access for source and role administrators and sub-administrators. Org Admin retains global record access, and SailPoint documents an exception for Identity Graph. Check the actual behavior on the surface the user will use. Verify both the action the level permits and the records it can reach.
Choose evidence for a delegated operator
Suppose a support team must find pending access requests and report ownership, with no authority to reassign or complete them. Use Access Request Read Only Admin for that documented purpose. Test filtering the request queue and viewing a test request. Separately confirm that the operator cannot reassign it. For a designated role authorized to do reassignment, test the appropriate Access Request Administrator path on a controlled request. This separates the inquiry task from operational control. If the same operator needs to help users with passwords or unlocks, evaluate the Helpdesk capabilities as a separate grant. Review its complete documented action set and verify those duties before assigning it to a request auditor.
Review additional grants when testing a permission. SailPoint documents combinations of user levels that cannot coexist and advises against combining Org Admin with subordinate elevated levels. An identity whose access comes from multiple assignments may have broader effective rights than intended in the case. Check all user levels and compare the observed action against the requirement. If a user level is added temporarily, agree on when to remove it and verify that the previously allowed elevated operation is denied afterward. For automation, also inspect endpoint-specific authorization and scope instead of inferring API rights solely from a screen.
You can verify a delegated grant by recording what task should be possible, the selected user level, how data access is scoped, and one denied operation outside that job. Check the same native target permission separately if the person also needs application access. These checks make it possible to explain a denial by either role capabilities or resource scope.
See SailPoint’s user-level permissions, permission matrix, Data Segmentation settings, and access overview.
An operator must filter, search, and open access requests but must have no administrative ability to reassign them. Which documented user level meets that narrow need?
Access Request Administrator
Access Request Read Only Admin
Org Admin
Cert Admin
A Source Sub-Admin must manage only an associated warehouse source. The tenant uses the documented governance-group model without Data Segmentation. Which test best demonstrates the source boundary?
Use Org Admin to edit the warehouse and finance sources
Inspect the user’s successful sign-in and skip testing a source
Use the operator’s own session to verify the required warehouse action and denial for an unrelated finance source
Grant a native payroll role and assume it determines SailPoint source permissions
Sections you finish are checked off in the contents.