2.2 Schema and Account Correlation

Key Takeaways

  • The account schema describes the fields SailPoint collects and identifies its Account ID, Account Name and entitlement fields.

  • Schema discovery is available on some source types. Inspect the resulting schema and confirm stable account identifiers before the first aggregation.

  • Standard account correlation uses ordered equality criteria. The default fallback compares the source Account Name with the identity name.

  • An unmatched account is uncorrelated. Updating matching data or using documented manual correlation can link that account to the correct identity.

Last updated: November 2026

Separate the record from its owner

A source’s account schema describes the data SailPoint stores for external accounts. The tenant uses the Account ID to reference a source account. The Account Name identifies the account by the selected name attribute. Set both appropriately for the connector before aggregating. SailPoint strongly discourages changing them afterward because doing so can break references or produce duplicates. Choose a stable identifier the source consistently returns. If that field must change because the target was redesigned, evaluate a connector-specific migration before relying on a routine schema edit.

Several sources define a default account schema as part of their connector configuration. Some support a Discover Schema operation that can load attributes from the target. Others require manual changes. Even when discovery is available, check the field type, whether a field can contain multiple values, and which field represents accounts’ entitlements. A regular account aggregation uses the configured schema. Do not assume it will automatically add every newly available upstream attribute.

QuestionSetting or evidence to inspect
Which record is this source account?The schema’s Account ID and Account Name fields and their source stability
What values can that record hold?Configured account attributes and their data types or multi-valued settings
Does the group value link to entitlement details?Entitlement flag, matching entitlement type name, and matching Entitlement ID value
Which person is this account associated with?Correlation criteria between account and identity attributes and actual matching values
What populates the person’s department?The chosen identity profile’s department mapping, independently of the account schema

Follow the standard correlation criteria

Account correlation associates a source account with an identity. Each standard criterion compares a selected account attribute with a selected identity attribute using Equals. The configuration considers the criteria in order. Use attributes whose values identify the correct person without collisions, and test representative patterns before broad use. Two criteria express alternative ways to make a match. They do not require two values to match together as a composite key. SailPoint describes matching as case-insensitive by default, with a configurable ignore-case setting for each source correlation configuration. A separately configured cloud correlation rule runs before standard account correlation.

Suppose a manufacturing source returns workerRef=E1049 for an account, and the intended identity has personNumber=E1049. If that identity attribute is available for correlation and identifies one person, pairing these fields can associate the existing account with the correct person. A matching source attribute and identity attribute can have different names. If both a normal and elevated account carry that same person reference, both can be associated with the same person while retaining distinct Account IDs. The scenario’s source accounts remain separate records.

If the source criteria find no match, SailPoint tries its default fallback. It compares the source’s Account Name with the identity’s name case-insensitively. This fallback is separate from the source criteria you can edit. For example, a source Account Name of lee01 can match an identity named Lee01 even when a configured employee number criterion finds no match. An account with no match after applicable rules and fallback remains uncorrelated. Inspect whether the identity already exists, whether the right attribute was loaded, and whether the values differ. If the correlation criterion changes, use an unoptimized aggregation for an applicable direct connection to revisit unchanged accounts. If the account was manually correlated, SailPoint documents that the link persists when source data changes. To reassociate a manually linked account, remove that link using the supported procedure before assigning it elsewhere.

Trace an entitlement detail

An account’s group membership contains role-a27. To link the value to a separately aggregated entitlement, mark the account attribute as an entitlement, use the corresponding entitlement type name, and verify that role-a27 matches the entitlement’s ID. Matching the friendly display label alone will not achieve that link. A connector can load accounts successfully and still have a mismatch between its membership values and entitlement IDs. Check the two datasets instead of changing the criteria that match accounts to people.

If a connector returns a list of group IDs, mark the membership field as multi-valued where required by its schema. The account entitlement attribute and the entitlement type need the same name for SailPoint’s documented linking behavior. A Boolean setting such as whether an account is enabled cannot be marked as an entitlement. The enabled flag and a group membership are both useful account data, but the schema represents them differently.

Review the counts of correlated and uncorrelated accounts and inspect sample matches. After a broad data or mapping change, include representative elevated accounts, new accounts and known exceptions in the test. A high match rate with ambiguous source identifiers can still conceal wrong associations, so check expected identities as well as the total.

See SailPoint’s source account schemas, account correlation, and account aggregation methods. SailPoint also documents the cloud Correlation Rule.

Test Your Knowledge

A non-authoritative source loads an account successfully, but neither its configured criteria nor the default fallback find an identity. There is no custom rule or manual link. What is the result?

A

The source automatically deletes its account

B

SailPoint automatically creates a new identity profile for that account

C

The cloud drops the account from the source inventory

D

The account is listed as uncorrelated and has no associated identity

Test Your Knowledge

An account has a group membership value team-73. The source aggregated a matching entitlement name, but the entitlement ID is group-91. What should the engineer verify to link the records?

A

That the identity’s display name matches the entitlement label

B

That the membership value matches the entitlement ID and that the schema marks the right entitlement type

C

That the source’s Account ID is changed to team-73

D

That the identity profile is given a higher priority

Sections you finish are checked off in the contents.