Active Directory Group Synchronisation

If your organisation runs Active Directory and its groups and users meet your business needs, synchronising with Claromentis system groups makes perfect sense as it reduces maintenance and complexity.

Typically there are 2 types of synchronisation adopted by companies, and in both cases Claromentis is the "slave". This means any changes to the Active Directory groups in Claromentis won't be synchronised back to the Active Directory server.



Partial Synchronisation

Partial synchronisation allows Active Directory Groups and Claromentis system groups to exist side by side.

This is useful if you would like to use system group structure in Claromentis to manage certain functions that are only applicable in Claromentis. For example, you may create a Claromentis system group called Content Managers, with Jo and Anne as members. Their main responsibility is to manage content within Claromentis, and so this group does not currently exist in the Active Directory structure. 


Full Synchronisation

Full synchronisation, on the other hand, will disregard groups that you have created manually in Claromentis and update them based on the Active Directory structure.

For example, you may have a group called Content Manager in Clarometnis that Jo and Anne are members of, which you have added manually from the People Admin Panel.

Anne is also a member of Group called Marketing in Active Directory.

When full synchronisation is performed, Anne will be no longer be a member of the Content Manager group, because it doesn't exist in Active Directory.

Full synchronisation does not automatically delete manually created system groups in Claromentis because it may have already been used in another part of the app, such as a Holiday Planner group.

It is advisable to review manually created system groups in the People Admin Panel, which you may have created as part of your training or testing, and delete unused system groups prior to performing or setting up full synchronisation with Active Directory.



Created on 24 January 2018 by Michael Christian. Last modified on 7 November 2019

Was this helpful?  

1 Like