Skip to main content


Share account fields between target systems

If you have multiple target systems, you may want to access a user's account attributes from one target system in another target system. For example, suppose you want to pull usernames from Active Directory to reuse in a Google Workspace PowerShell target system, or in Notifications. In this case, AD is the shared system, and Google Workspace is the dependent system.

HelloID accomplishes this by mapping the shared fields not only into target accounts, but also back into the corresponding Persons objects. The shared fields become available to map in other target systems, as if they had been mapped onto persons in Source mappings.

To get started:

To view all shared fields for a given person, View a person's target accounts.

If you attempt to access a shared attribute for a user who doesn't have an account in that system, the value will be empty. Plan your user deployment accordingly, and/or use complex mappings or scripting to handle empty values.

During Enforcement, the entitlement actions of the shared system are resolved before the entitlement actions of dependent systems. This ensures that the attributes are available in time. For more information, see Dependency order.


Do not make two systems dependent on each other. This creates failure and/or race conditions during enforcement.