There are 3 possible ways to get the user's information in sync with other databases, in which you need to decide which is the 'true' source.

1. LDAP Server

Suppose you have Active Directory in your organisation and intend to use them as the 'true' source is from active directory. In that case, most user's fields in people's profiles such as 'city' can be updated using Active Directory Sync.

AD (master) - Claromentis (slave)

2. REST API from Claromentis

Suppose you have user information in Claromentis as the 'true' source and would like to allow third-party databases to read this data. In that case, Claromentis provides Rest API for user profiles that can be used to read users' data. Read more about People REST API here

Claromentis (master)  - Third party is pulling data using Rest API

3. Database replication

In this situation, some of the user's data is stored in an external database while you wish Claromentis to keep its data in sync with it.

This approach requires database replication which can be scheduled periodically (such as daily replication) to keep user data in sync with Claromentis or vice versa.

Please note that synchronising between multiple databases requires unique common attributes such as 'employee code' that exist in both databases, in addition, there will be a delay in which prior sync process and the data in one of the systems will be out-of-date.