> This page is for Unified.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Auto-provision and de-provision

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

---

#### 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.

#### Write provisioning logic

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`

> **Note**
>
> Use [Webhooks](/merge-unified/reading-data/webhooks/merge-webhooks) to be notified when an Employee model is Created or Updated in Merge's system.

> **Note**
>
> [Field Mapping](/merge-unified/supplemental-data/field-mapping/overview) should be used if you wish to pull in fields not part of Merge's Common Models, such as custom fields.

#### 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.

#### 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.

#### Get started auto and de-provisioning with Merge

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](/merge-unified/supplemental-data/field-mapping/overview)

\
\
\