What are the possibilities with a Datamapper User Provisioning?

Datamapper is a method for User Provisioning where user information and access rights are managed using a data mapping system. Plek exchanges data using a ClientID and ClientSecret from the client application and retrieves data through an Application Programming Interface (API). This system acts as an intermediary layer between Plek and the organization's application, allowing data to be mapped, transformed, and synchronized. It uses mapping rules to convert data from one format to another.

This way, data such as names, email addresses, and other attributes can be mapped from your application (for example, an HR database) to Plek. This process can be automated and standardized, making the management of user information and access rights easier.

Please note! User Provisioning based on Datamapper is always custom work. Setting it up will always take place on a project basis with a kick-off to outline your wishes, determine the expected duration, and figure out which data the client application works with.

1. Automatically create users in Plek
   When a new employee joins your organization and is added to the Active Directory with the correct access permissions, Plek will automatically create a user account for them, granting them immediate access. This is done using a unique value from the Active Directory, which Plek uses as a mapping key.
   
   The mapping key must be a unique value in the Active Directory that will never be changed for a user. If it is changed, conflicts may arise with individual accounts, such as duplicate accounts, users not synchronize,  or login issues.
2. Synchronize profile data
   Link fields from the Active Directory to the profile fields in Plek, so that changes are automatically updated upon the next login. This ensures that the profiles in Plek remain consistent and up-to-date.
   
   - Note: We do not offer synchronization support for (birth)dates and profile pictures for Plek profiles.
   
3. Deactivate users 
   When an employee leaves the organization and is removed from the Active Directory, Plek will automatically deactivate their user account, denying them access to the platform and associated information.
   
   The automatic removal of users will by default be based on a value in the Active Directory. For example: leave date or active=true or false. This value must remain in place before the synchronization takes place. 
   
   For other forms of user deactivation, additional customization will be provided upon consultation.
   
4. Automatic addition to groups 
   Based on certain profile fields, users can be automatically added to specific groups within Plek. This can be useful for organizing teams or departments within the organization. Users are added to the group after the next successful synchronization.
   
   - For example:
   All users with function X can be automatically added to group Y.
   All users with function A or B can be automatically added to group C.
   
   - Group mapping is by default  based on a profile field. The correct profile field in Plek must be linked to the correct attribute in the Active Directory.
   - Users are by default not removed from groups when the value in a field changes. Group mapping via Single Sign-On only adds users. For example, if your function changes from X to A, the user will be added to group C but not removed from group Y.
   
   For other forms of automatic addition to groups, additional customization will be provided upon consultation.