> 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/rehire-employee.md).

# Rehire employee

{% hint style="info" %}
Only available in API v2.
{% endhint %}

When a previously terminated employee returns, the existing user should be rehired rather than creating a new user. This preserves the employee's history in SameSystem.

Rehiring requires a new contract and can cover two main scenarios:

* **Gap between contracts**\
  The previous employment has ended, and the employee returns at a later date.
* **Consecutive contracts**\
  A new contract follows the existing contract without a gap in employment.

Depending on the scenario, you can use **Rehire User** or create a **new contract** directly.

> **Important:** The **Employments flow** setting must be set to **Sequential employments** in General Settings to use the rehire functionality.

The following guides describe the different rehire scenarios and their date requirements.


---

# 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/rehire-employee.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.