> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/portal-quick-setup/organizational-setup/automated-hr-sync.md).
# Automated HR Sync
HR Sync connects equipme with your HR system and keeps both employee data and organizational structures aligned automatically. Instead of manually creating and maintaining users, locations, cost centers, or similar structures, changes made in your HR tool are transferred to equipme in a structured and consistent way.
In practice, this means that new employees can be created in equipme as soon as they appear in the HR system, role or department changes stay in sync, and leavers can be handled cleanly without manual follow up work. At the same time, organizational elements such as locations or cost centers can be kept up to date automatically, ensuring that assignments, reporting, and billing related processes are always based on current data.
Within equipme, HR Sync is used to automate onboarding and offboarding related data flows and to maintain a reliable organizational structure. This creates a single source of truth between your HR system and equipme and significantly reduces manual maintenance over time.
This quick guide explains what HR Sync does and why it is relevant in equipme. For detailed instructions on how to set up HR Sync, please refer to the dedicated HR Sync setup article in the documentation.
{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/FpFh13aNgLrcXlWyES5D" %}
[HR-Sync overview](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/integrations/hr-sync-overview)
{% endcontent-ref %}
---
# 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://hub.equipme.io/classes/portal-quick-setup/organizational-setup/automated-hr-sync.md?ask=&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.
