Auto-provision and de-provision
1. See previous use case
You have already followed the Onboard Employees use case to ingest Employee data into your system.
- This Workflow will assume Employee data from Merge is being synced in your backend.
2. Write provisioning logic
In your backend, write logic to assign permissions in your system. Logic can be built based on fields such as:
job_titlemanager- In the Group Object
type=DEPARTMENTorBUSINESS_UNIT work_locationorhome_locationtermination_date
Use Webhooks to be notified when an Employee model is Created or Updated in Merge’s system.
Field Mapping should be used if you wish to pull in fields not part of Merge’s Common Models, such as custom fields.
3. Reflect changes to your users
Reflect changes for changed employees in your app’s frontend, by either removing them from your system or revoking permissions. Look for changes in the above fields.
4. Ensure your user's security
With permissioning logic handled, your app can deprovision exiting employees to safeguard company data, prevent unauthorized access, and maintain compliance, reducing security risks and administrative overhead.