> For the complete documentation index, see [llms.txt](https://docs.peoplelogic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peoplelogic.dev/guides/synchronizing-org-charts.md).

# Synchronizing Org Charts

Add Merge.dev support for broader HRIS integrations.

Everything around talent management relies on knowing your organization's structure.  Fortunately, nearly all of our partner integrations support synchronizing the org chart (employees and teams and their hierarchy).  

For most customers this will be enough, but for those that need direct integration with their HRIS or external Directory, we have partnered with Merge.dev to provide a broader set of integrations.

<figure><img src="https://214419501-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJnTEn53Z4ZTCjCdmENZ2%2Fuploads%2FM09xbGBJOhwQa4SGeXe3%2FScreenshot%202025-07-10%20at%205.31.09%E2%80%AFPM.png?alt=media&amp;token=11e1d5c3-40f2-4e2b-83d8-8f18a0422675" alt=""><figcaption></figcaption></figure>

### Working with Merge.dev

{% hint style="danger" %}
Today, connecting an HRIS through Merge requires contacting our support team to ensure that the connection is established and syncing correctly. &#x20;
{% endhint %}

Connecting to a broader set of HRIS integrations is just like working with any other [App](/guides/key-concepts/apps.md) in the Directory that manages your Talent Cloud. To start the connection process, you need to request a Magic Link from Merge.

```http
GET https://api.peoplelogic.dev/api/v1/app/merge/start-link
Authorization: Bearer {{yourOrgToken}}
```

Calling this endpoint will produce a Merge Magic Link that you can open in your browser.  Once you complete the connection process, it will produce a linked account token that you'll use to make the call below.

```http
POST https://api.peoplelogic.dev/api/v1/app
Content-Type: application/json
Authorization: Bearer {{yourOrgToken}}

{
  "type": "pl:sync:merge:hris",
  "internal": true,
  "name": "Demo Connection with MS Entra",
  "externalId": "entra-merge-hris",
  "secretData": {
    "accountToken": "{{entraLinkedAccountTokenFromMerge}}"
  }
}
```

A 201 response code indicates that the setup is complete.  Your employees will start to sync immediately into Merge and then to Peoplelogic.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peoplelogic.dev/guides/synchronizing-org-charts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.