Access Profiles and Multiple Target Accounts
Key Takeaways
An access profile bundles entitlements from a single source and can be used in roles, lifecycle states, and configured access requests.
For an automated grant, Multiple Account Options should identify exactly one account when the identity has multiple accounts on that source.
With one account, SailPoint bypasses the profile’s multiple-account filter. In an access request, the requester selects from the available accounts.
Treat account ownership, automatic account selection, and native access verification as separate checks.
Build the access unit from the source catalog
An entitlement can represent a group membership or permission on a source. Aggregation and appropriate schema configuration bring supported entitlements into the catalog. Identify items by the relevant source and native entitlement value so two similar display names do not lead to the wrong grant. An access profile groups related entitlements from one source into a unit, such as the ledger read and export permissions of a finance system. A role can assemble access from multiple sources. A lifecycle state can also grant an access profile directly, and a profile can be configured for requests when the feature is available. These paths have different triggers and approvals.
Before configuring an automated grant, inspect the identity’s accounts on the profile’s entitlement source. The profile selects among accounts already correlated to that identity. Account correlation establishes which identity owns each account. Use consistent account classifications in the schema when a person has a daily account and a separate privileged account. Identity department might determine who receives a role, while a field on the source account can determine which account receives its access profile.
Configure one qualifying account
| Situation | Account selection behavior |
|---|---|
| One correlated account and an automated role or lifecycle grant | Use the one account without applying the multiple-account filter |
| Multiple correlated accounts and exactly one match for the automated grant | Grant to the matching account |
| Multiple correlated accounts and zero or several matches | Automatic selection fails. If manual account selection is enabled, the source owner can choose the target in a task |
| Access request where the recipient has multiple accounts | Requester selects the intended account by account name and ID in the Request Center |
Open Multiple Account Options in the access profile. Select the account attribute, comparison, and value. Supported options include Equals, Does Not Equal and Contains, and the configured value is case-insensitive. Multiple criteria can be grouped. The platform uses the other Boolean operator between groups. If criteria within groups use AND, groups combine with OR. Review a table of actual account values before relying on the filter for automated access.
For example, assume one user has two accounts on an application source. Native account U-410 is classified as employee and standard. U-410A is classified as employee and privileged. An automated grant for Basic Ledger Access should use the first. If the filter only checks population = employee, both accounts qualify and the filter fails to select one. Add tier = standard with AND within the group. Only U-410 now satisfies both. If an old aggregation leaves both tiers blank, neither qualifies. Suppose a separate temporary account type is also allowed for another workforce population. Under an AND-within-groups configuration, add a separate group for that permitted population and account type. Recheck how many accounts satisfy either group. Each additional group can introduce a second match even when each group looks specific on its own. Check the source values and the intended account type before resubmitting the grant or completing a manual selection task.
Check exceptions before activation
Test the person with two matching accounts and the person with no match. If manual selection is enabled, verify the source owner can recognize the correct account and knows which fulfillment actions are still required after choosing it. Also test an identity with one account whose attributes would fail the same filter. The filter will be bypassed for that identity. If your policy must exclude that single-account situation, design and test an appropriate eligibility control before using the grant, rather than relying on the multiple-account filter as a general access gate.
For an ordinary request through the Request Center, verify which account the requester chose. A profile already held by the identity cannot be requested for a different account as the same profile. If the business needs the same permission on two accounts, consider the documented alternatives of requesting individual entitlements or using roles. Test the exact accounts and assignments separately. Confirm the target account ID and its actual permissions after provisioning, and verify that the privileged account was left untouched in the worked case.
See SailPoint’s access profiles and multiple account options, account correlation, entitlement aggregation, and access requests.
Which design correctly bundles Ledger Read and Ledger Export from the same source for repeated provisioning?
Assign both entitlements to one access profile from that source and use that profile in the intended assignment path
Group them in a new identity profile because access profiles perform identity correlation
Replace their source catalog data with a virtual appliance setting
Declare the target account names as entitlement types
A lifecycle state grants a profile on a source with two accounts for one worker. Both match the profile’s current selection criteria, and manual account selection is disabled. What should the engineer expect?
The connector grants the profile to both accounts
The source selects the older account automatically
Automatic selection fails until the criteria and account data identify one matching account
SailPoint asks the worker to choose in their original Access Request
Sections you finish are checked off in the contents.