Hi @s_tartaglione,
Please find below inline commands
- How can we synchronize changes to an Identity or Account attribute with multiple sources? In Source Create Account Profile if you use Identity attribute to map account attribute you can use OOTB Attribute Sync
- If the solution involves using a Workflow, what steps should be taken to ensure the attribute change is accurately reflected on the source?Attribute Sync can be able to sync account attribute if there is change in Authoritative source Identity attribute
- How can we configure Standard Connectors to effectively propagate this information? Most of OOTB connectors have this feature
you may refer this Synchronizing Attributes - SailPoint Identity Services
I need guidance on how to manage the propagation of actions after an Access Request has been approved for application X, particularly to ensure that the request is communicated to several other applications, such as W, Y, Z, and so on. If this Access Request is approved for Source level then it should only have entitlements for that source X, it can’t have other source for (Access Profile & Entitlement), Then there won’t be any link to other sources as W,Y,Z and so on. This is possible if we have Role in place where we can add multiple entitlements from multiple sources here approval won’t belong to source level. In this case if user A request role ABC which has Source X W Y Z entitlement, if user doesn’t have accounts in source X Y W Z we need configure create account profile for these sources before access got approved, Then ISC will create account first and provision these access to those sources. If user A has accounts in these sources ISC will provision entitlements accordingly
-Vasanth