> 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/employee-management/add-pending-entry.md).

# 新增待入职员工

## 1. 功能描述 <a href="#id-1-feature-description" id="id-1-feature-description"></a>

* 如需新增 「即将加入公司的员工」&#x20;
* 操作步骤: \
  ［员工管理］>［员工列表］>［新增员工］>［新增待入职］
* &#x20;填写资料后，该待入职员工将会显示在入职管理栏中。
* &#x20;在填写资料后，管理员可选择是否现在邀请员工注册。若开启 「现在邀请」 按钮，按下 「保存」 。管理员就能透过员工登记的电邮 \[发送邀请] 给该待入职员工。该 「待入职员工」 就能凭电邮邀请登记帐户，自行输入资料。

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

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

* 待入职员工填妥资料后，便能在入职管理中帮助该员工办理入职。&#x20;
* 操作步骤: \
  ［员工管理］>［员工状态管理］>［入职管理］>［办理入职］&#x20;
* 按下 ［办理入职］后，管理员能选择入职日子并按［确定］。
* &#x20;辨理入职后，员工档案可以看见入职状态转变为 「正式」 。

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

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

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


---

# 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/employee-management/add-pending-entry.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.
