Building Identity Search Queries

Key Takeaways

  • Choose the Search category before translating the requirement into fields and values.

  • Use one nested clause when several predicates must describe the same account or access item.

  • Use explicit uppercase logical operators, parentheses and quoted phrases when needed.

  • Check identity data, correlation, index timing and record visibility before interpreting an empty result.

Last updated: November 2026

Choose a record type, then fields

SailPoint Search has different categories, including Identities, Events, and Account Activity. Start by naming the result requested. For a list of people with some current access, use the Identities category and its model. For an audit event about a configuration change, use the Events model. Account Activity addresses operations on third-party systems. Combining fields from different categories as if they were one record can return no result even when both facts exist. Category also guides the output, such as an identity row versus a timestamped operation row.

Under Identities, first-level fields like status or displayName describe the identity, and a field like manager.name describes an associated object. The manager must be correlated to a valid identity for the relationship to be searchable. An identity's mapped custom attributes are under attributes. Check the actual field in Searchable Fields or the sample data and whether a site-specific attribute is configured for Search. Field names are case sensitive. Ordinary terms are case insensitive, and the documented .exact form can match the exact form when applicable. Double quotes keep a multiword phrase together. Write AND, OR, or NOT explicitly, because the default between ordinary query terms is OR. Use parentheses wherever grouping determines the result.

Question about identitiesExample query
Who has the Active status value?status:ACTIVE
Who has a manager whose name is sam.lee?manager.name:"sam.lee"
Who has an account on the exact source Warehouse Directory?@accounts(source.name.exact:"Warehouse Directory")
Who has a privileged item from Warehouse Directory (source ID warehouse01)?@access(source.id:warehouse01 AND privileged:true)
Who has a searchable end-date value in the expected format?_exists_:attributes.endDate

status:ACTIVE refers to the documented identity status field. Use the appropriate lifecycle field and recorded value if the requirement concerns a lifecycle state. A login status and a configurable lifecycle-state name can describe different facts about the same identity.

Work the nested match

Suppose the audit asks for identities who hold a privileged item from Warehouse Directory (source ID warehouse01) and whose manager is sam.lee. Use manager.name:"sam.lee" AND @access(source.id:warehouse01 AND privileged:true). The predicates for source and privilege describe one item within the access collection. The manager predicate describes the parent identity. If someone has an unprivileged warehouse item and a privileged finance item, the two item conditions are satisfied by different objects. The query with a single nested clause correctly excludes that person. Two separately nested access clauses can be satisfied by independent items and would answer a different question.

Start with the source name or object ID alone and confirm several results against actual identity records. Add privilege, then manager. Sample a known match and a known exclusion. If the requirement changes to identities with both a warehouse account and a separate access item, combine the two different nested object clauses, @accounts(...) and @access(...). If one field must match either of two acceptable values, group the alternatives inside the clause for that same object. Confirm result count and categories before using a saved query as the scope of a certification, or exporting results for review.

Diagnose missing data before changing the query

First confirm that the account was successfully aggregated and correlated. Uncorrelated source accounts are not entries in Identity Search's correlated account collection. Inspect the source inventory if the expected account has no attached identity. For an expected manager, inspect that relationship as well as the raw employee-side attribute. Then check the category, exact source name or actual ID, field spelling, and record access of the person or client performing the search. Data Segmentation can restrict the records returned on supported surfaces. Compare access with the intended scoped identity and an authorized baseline to isolate a visibility difference.

SailPoint documents that ordinary identity-related updates usually appear quickly, with possible delays under load. Certain changes that do not directly result in identity changes can wait for a nightly indexing job. Confirm when the upstream change was recorded and how it reaches the index. For fresh or disputed access, reconcile with the native source and the relevant activity record. A search result answers a model query against the data present and visible in that index at the time.

See SailPoint's Search overview, query syntax, searchable fields, index timing, and Data Segmentation.

Test Your Knowledge

Which identity query requires a privileged item to come from the Warehouse Directory source with ID warehouse01?

A

@access(source.id:warehouse01) AND @access(privileged:true)

B

attributes.source:"Warehouse Directory" OR @access(privileged:true)

C

@access(source.id:warehouse01 AND privileged:true)

D

@accounts(source.name.exact:"Warehouse Directory") AND @access(privileged:true)

Test Your Knowledge

An account is present in the source inventory but has no correlated identity. What is the expected result of searching for it within the Identities category using @accounts(...)?

A

It is absent from that identity-based match until associated. Check the source account inventory and correlation.

B

It appears as an identity row with no account details.

C

It automatically appears if the identity query uses an OR operator.

D

It is returned only if the calling user filters the Account Activity category by last modification date.

Sections you finish are checked off in the contents.