> For the complete documentation index, see [llms.txt](https://docs.coreway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreway.com/coreway-hr/zh-cn/faq/employee-management/how-to-handle-if-employee-was-terminated-by-mistake.md).

# \[员工管理] 不小心错误地把员工离职,应如何处理?

如果管理员不小心错误地把员工离职或因公司需要有必要安排员工重新入职, 可参考以下的处理方式：

\[员工管理]-> \[员工列表]->\[已离职]->点选相关员工档案->右上角"..."->重新入职

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/gwFzXScEEFa0xaf7dVCC/1.png" alt=""><figcaption></figcaption></figure>

<br>

员工的资料会保留于员工档案,此时管理员需要决定是否修改员工编号以前往下一步。

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/ZgZxZv5oZCEmnK9Hc2zO/2.png" alt=""><figcaption></figcaption></figure>

<br>

&#x20;

不修改员工编号:&#x20;

员工会保留原有的在职资料及重新入职。

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/PESEH2H3AfR00qP7t34W/3.png" alt=""><figcaption></figcaption></figure>

&#x20;

&#x20;

修改员工编号:

员工会作为”新员工”重新入职，此员工不会存在任何在职数据。

以往的在职资料只会维持于原员工编号的记录中。

<figure><img src="https://content.gitbook.com/content/2rAQKEhs5Y3QzByAJWJc/blobs/Sdpe3TFklxRAaFwZqIXA/4.png" alt=""><figcaption></figcaption></figure>

<br>


---

# 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.coreway.com/coreway-hr/zh-cn/faq/employee-management/how-to-handle-if-employee-was-terminated-by-mistake.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.
