Predicting Provisioning Transaction Outcomes

Key Takeaways

  • Identify the identity, source, target account and entitlement before predicting the operation.

  • A grant on a supported direct-connect source can create a missing account. Later grants can modify that account.

  • For concurrent entitlement requests on a source without an account, SailPoint documents one initial account creation while other entitlement requests wait.

  • Track approval, account activity and the effective target result as separate evidence.

Last updated: November 2026

Read the initial state

Start by identifying the person, the source and the specific target account. Check whether the source has a writable connector for the operation and whether an account associated with the identity already exists. Then read the business action, such as grant, remove or disable. Record the entitlement IDs too. A display name can label two different groups, and two accounts associated with one person can have different permissions.

In Identity Security Cloud, access requests, qualifying roles and lifecycle assignments can all initiate provisioning. An approved request records authorization. Provisioning uses that authorization to change the target when the request becomes executable. If the source is flat file, SailPoint tracks the required change as a manual task. The operator must perform it on the source and record completion. For a request with automatic writes, confirm the action in Account Activity and inspect the target after processing.

Starting state and instructionExpected path when the stated operation is supported
No account on a write-enabled direct-connect target, grant an entitlementCreate an account using the source’s Create Account definition and fulfill the grant
One existing account, add a standing entitlement that is absentUpdate access on the existing account
One account, remove one role assignment while another assigned role grants the same entitlement on that accountThe still-assigned role preserves its entitlement
Account on a flat-file source, approved access changeWork item for a person to carry out the change on that source
Existing account, revoke its only role and entitlement with no explicit account actionProcess the access removal while the source account remains

Read the conditions behind each row. An error after some writes can leave a new account with incomplete access. A removed role can leave the account and shared entitlements. Additional lifecycle account actions such as disable or delete have their own configuration and support requirements. Determine whether the case describes access supplied by another role or by a second standalone access profile. Under SailPoint’s documented standalone profile behavior, two profiles can share an entitlement. Revoking one then removes its entitlements, including the shared item. The identity can lose the other profile as a bundle and retain its remaining distinct entitlements individually. Verify the source access model before applying either overlap rule.

Work a concurrent entitlement request

Consider a test identity with no account on a write-enabled finance source. The team requests two individual standing entitlements, Ledger Read and Invoice Export, at about the same time. Both requests become eligible for provisioning. SailPoint documents that the first becomes an account creation request. The other waits for the new account so its entitlement can be added through an update. If Ledger Read is first, the expected successful result is one account with Ledger Read and Invoice Export. The order given here is an input to the example. Use actual activity records to determine which request started account creation.

Suppose the target shows an account with Ledger Read, and the Invoice Export activity is pending. Record the creation and first grant as observed, and leave the second grant open until its own operation completes. If Invoice Export later fails because the integration account lacks the relevant write permission, examine the failed operation, remediate the permission through the approved process and verify the resulting access. A second account creation would be an inappropriate recovery when the first already succeeded.

Trace the request through to the target

Reconcile three snapshots. First, use the access request or role record for the authorized change and the grant origin. Second, use Account Activity or the Provisioning Activity report to find the relevant source operation, status and errors. For manual fulfillment, inspect the task with the account and source. Third, confirm the actual account and entitlement membership on the target. For the worked case, a successful account create satisfies a different assertion from the export permission. Check both using the target identifier.

When an observed resource differs from the expected snapshot, follow the narrowest discrepant operation. A completed role assignment can coexist with an unrelated entitlement another role still supplies. A later aggregation can help reconcile the platform view with confirmed native state, where the source supports that retrieval. It does not replace the evidence for which provisioning transaction succeeded. Preserve the initial state and the final native state so another engineer can reconstruct the outcome without repeating the write.

See SailPoint’s account creation behavior, parallel entitlement request behavior, role revocation behavior, access-profile removal, and provisioning monitoring.

Test Your Knowledge

An employee with no account on a write-enabled source requests two individual entitlements at nearly the same time. Both are approved. What does SailPoint do with the second request while account creation is in progress?

A

Creates a separate account for the second entitlement

B

Waits for account creation so the second entitlement can be added to the new account

C

Changes the approval to a lifecycle-state assignment

D

Discards the second grant because only one entitlement can be requested

Test Your Knowledge

A worker’s only role and its exclusive entitlement were successfully revoked. No other action targets the account itself. What remains?

A

The account is always deleted

B

The account moves to a different identity profile

C

The source is converted to flat-file provisioning

D

The source account remains without the revoked entitlement

Sections you finish are checked off in the contents.