Fresh 2026

Auto-provision and de-provision

How to auto-provision and de-provision employee permissions based on HRIS data using the Merge HRIS API.

---

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.

In your backend, write logic to assign permissions in your system. Logic can be built based on fields such as:

• job_title
• manager
• In the Group Object type=DEPARTMENT or BUSINESS_UNIT
• work_location or home_location
• termination_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.

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.

Integrate today or talk to our sales team to learn how Merge unlocks hundreds of integrations in days - not years.

Get a demo

• Field Mappings