Auto-provision and de-provision
Auto-provision and de-provision
Auto-provision and de-provision
You have already followed the Onboard Employees use case to ingest Employee data into your system.
In your backend, write logic to assign permissions in your system. Logic can be built based on fields such as:
job_titlemanagertype=DEPARTMENT or BUSINESS_UNITwork_location or home_locationtermination_dateUse 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.
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.
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.