Hi All,
I am aiming to perform manager correlation for few accounts where the source data is not clean. Any suggestions on how can we manually perform manager correlation for few accounts?
Hi,
Unless anyone knows differently, what you are asking is not feasible
Hi @AsGoyal
You need to configure the manager correlation in your auth source and then trigger the account aggregation task.
Performing manually is not feasible as of I know.
You can perform single account aggregation of a source through UI under accounts page of the source.
You can also use the manager correlation rules to achieve that : Manager Correlation Rule | SailPoint Developer Community
Echoing @baoussounda re Manager Correlation Rule. However, you are not going to want to hard code the mappings in the rule, so I would suggest creating a delimited connector to contain the mappings for the few accounts then referencing that in the Manager Correlation Rule.
You didn’t say - is this a one-off exercise, ie future records will have correct managers? Also, when you say source data not clean, do you mean it correlates to an incorrect Identity or doesn’t correlate at all?
@AsGoyal When the source (authoritative) data is not clean, there are very limited options to reliably perform manager correlation.
From my understanding, the only possible workaround is to use a Manager Correlation Rule. However, please note that this is a cloud-based rule and should ideally be treated as a temporary or exception-based solution rather than a long-term fix.
The recommended and more sustainable approach is to clean and correct the authoritative source itself. I understand this can be a significant pain point, but if the source of truth is incorrect, any downstream correlation logic will eventually face accuracy and consistency issues.
Hi @AsGoyal ,
Manager correlation is performed by configuring the attribute mapping in manager correlated tab, if that is not possible, we have to go with the manager correlation rule. But the manager correlation rule is cloud rule.
@AsGoyal You can explore leveraging a transform rule together with a secondary authoritative source.
The transform rule can be used to check whether the secondary source contains a manager ID for the user. If present, this value would override the one from the HRIS.
As part of the process, once the data is corrected in the HRIS, the manager value can be removed from the secondary source, allowing the system to fall back to the HRIS value.
This seems to be the feasible solution, IN some case if the attribute is null maybe you can map them to a default user
Thanks all for your inputs.
I have submitted this as idea https://ideas.sailpoint.com/ideas/GOV-I-5105
@aaron_andrew , Thanks for updating
If source data is not clean, best approach is to use a custom correlation rule or manually update manager attribute through identity profile mappings/transforms based on a reliable attribute like employee ID or email.
For very few accounts, you can also update the manager value directly in the source/account data and run aggregation again, since ISC manager correlation mainly depends on clean authoritative source data.