How Does ISC Handle Attribute Sync for Long-Term Terminated Identities

Hi everyone,

I had a question regarding lifecycle states and attribute sync behavior in ISC.

If an identity is moved to “Inactive(long-term)”, does ISC automatically stop attribute synchronization/updates from sources (e.g., HR aggregation)?

Or do we still need to explicitly handle this using transforms or rules to prevent updates for those identities?

I came across documentation suggesting long-term terminated identities are excluded from processing, but I want to confirm whether that applies only to lifecycle events/provisioning or also to attribute sync.

Link I referred to: New Capability: Management of Inactive Identities

Would appreciate any clarification or real-world experience on this. Thanks!

As per the SailPoint latest capability, SailPoint will not perform attribute sync for the long-term disabled identities.

I think, with the help of APIs you can still perform the Attribute Sync for those users. You can try and check.

Thanks, Manish. We are looking to stop attribute sync for these identities and are not seeking any updates to the identities unless they are rehired. So, we are good with SailPoint not updating. Thankyou.

@ebesamuel2 If it solves your problem, then please mark it solution.

Thanks