2.5 Planning and Checking Account Aggregations
Key Takeaways
Optimized aggregation reads accounts and skips unchanged records when evaluating correlation. Use an unoptimized run to revisit unchanged records after changing matching criteria.
Delta aggregation depends on support from the selected connector and on the kind of source change.
A single-account aggregation refreshes account data without synchronizing identity attributes or provisioning changes.
Use an appropriate deletion safeguard when a full source aggregation may remove stale account records.
Plan the run from its intended outcome
Account aggregation loads account data from a source into SailPoint. The run can also collect those accounts’ entitlement values when the account schema identifies them. Entitlement aggregation can load the source’s entitlement catalog, including items no account currently holds and attributes such as names and descriptions. Decide which data is needed before starting either process. A run that updates account memberships may still leave catalog descriptions incomplete. An account run does not delete the entitlement catalog when a membership disappears.
- Verify the intended source, schema, connection and account correlation configuration. Where supported, establish the account and entitlement types before the first broadly used collection.
- Select a direct connection run or the correct flat file import. For a direct connection, choose the appropriate method for the task and ensure the source supports it.
- Set an appropriate schedule, scope and deletion controls, then start or schedule the run. A queued run can start after its nominal time when other work is ahead of it.
- Inspect aggregation history for status and counts. Compare a sample of account ownership and access against the target. Check any unexpected deletions or uncorrelated records before using the inventory for access decisions.
| Use case | Suitable operation |
|---|---|
| Routine updates for a direct source | Use the default optimized path when unchanged accounts need no reevaluation |
| Reapply corrected correlation criteria to unchanged accounts | Use an unoptimized direct source aggregation |
| Collect incremental changes from a connector that supports the particular change | Configure supported delta aggregation |
| Refresh the visible data for one existing account | Use the single-account action when available |
| Refresh a flat file source | Upload the applicable file manually |
Determine what gets reevaluated
A default optimized run retrieves records, checks for changed data and skips unchanged existing records for account and manager correlation. After correcting a source’s correlation pairing, those unchanged records need to be processed again. SailPoint’s direct connect API procedure accepts the form field disableOptimization=true for that run. Set it for each API call that needs the non-default behavior. The ordinary scheduled or manually initiated user interface run uses optimization. Check the job history to confirm the mode before concluding that a new rule did not work.
Delta operation depends on connector-specific behavior. For example, SailPoint documents that Microsoft Active Directory delta aggregation does not handle moves between organizational units (OUs). Use a full account aggregation after a move between OUs to reduce the risk of duplicate accounts or other unexpected results. If the actual objective is reevaluating an unchanged account under updated matching logic, also choose the method with optimization disabled. The run scope and its rule reevaluation are distinct decisions.
Validate a limited refresh and manage removals
Consider a help desk ticket about an account whose lock status changed in the target. A single-account aggregation reloads that account’s data and status. It does not synchronize the new value into identity attributes or trigger provisioning. Account deletions are processed during full source aggregation. If the target account is missing on a single-account lookup, the existing SailPoint record remains unchanged under the documented single-account procedure.
When account deletion is enabled, check the Percentage of Deleted Accounts Allowed threshold. Compare likely removals to normal and anomalous changes before setting it. A faulty export or query can look like large numbers of accounts disappeared. SailPoint documents rounding the threshold to a whole account for small sources. A value that rounds to zero only stops a run when all accounts would be deleted. If the threshold represents too few records, a normal omission could stop the run. Treat a threshold alert as a reason to verify which records the source actually sent before changing protections.
For example, a full run sees 85 returned rows for a source that had 100 accounts. Assume the 15 missing accounts would all qualify for deletion and the configured threshold corresponds to five accounts. Fifteen exceeds five, so expect the safeguard to stop the run. Compare the missing identifiers to the source extract before treating the omissions as intentional.
Review the job history after the run. An account scan count describes the work performed. It does not guarantee that each account was mapped to the intended person or that the entitlement catalog contains every record. Confirm expected samples and investigate any deltas against the prior known-good inventory.
See SailPoint’s account aggregation and safeguards, entitlement catalog loading, and entitlement deletion behavior.
A direct source has new correlation criteria, but its account records are unchanged. Which run forces the existing records to be reconsidered?
An entitlement aggregation only
A routine optimized run started from the schedule
A direct source aggregation with disableOptimization=true
A delta run limited to changed source records
A help desk administrator selects Aggregate Account for one existing identity account following a target-side unlock. What should the administrator expect?
The account data updates. The operation does not synchronize identity attributes or run provisioning.
All source accounts and entitlement names are reloaded.
The identity’s profile changes automatically to the source that owns the account.
A missing target account is deleted from SailPoint by this operation.
Sections you finish are checked off in the contents.