> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/business-guides/employee-lifecycle-management/changes-to-employees.md).

# Changes to employees

{% hint style="info" %}
**Note:** Users can also be modified using **API v1**. However, for user and contract integrations, we strongly recommend using **API v2**, and this guide therefore describes user changes using API v2 only.

If you need to modify users using API v1, please refer to the [**API v1 OpenAPI specification**](https://docs.samesystem.dev/api-v1-reference/) for the available endpoint, request parameters, and data model.
{% endhint %}

SameSystem API v2 can be used to maintain employee data through the **Users** and **Contracts** endpoints.

Typical employee lifecycle operations include:

* Updating employee information
* Updating contracts (changing departments, titles, or employment information)

Employee information in SameSystem is divided between the **User** and **Contract** resources. User data represents the person, while contract data represents the employee's employment details.

When building an employee integration, it is therefore important to determine whether a field belongs to the user or to a specific contract.


---

# 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.samesystem.dev/business-guides/employee-lifecycle-management/changes-to-employees.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.