> 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/employee-management/add-pending-entry.md).
# Add Pending Entry
* If you need to add "employees who are about to join the company"
* Operation steps: \
\[Employee] > \[Employee List] > \[Add Employee] > \[Add Pending entry]
* After filling in the information, the employee to be hired will be displayed in the onboarding management column.
* After filling in the information, administrators can choose whether to invite employees to register now. If the "Invite Now" button is enabled, click "Save". The administrator can \[send invitation] to the employee to be hired through the employee's registered email. The "employee to be hired" can register an account with an email invitation and enter the information by himself.
* After the onboarding employee fills in the information, the employee can be assisted in the onboarding process in onboarding management.
* Operation steps: \
\[Employee] > \[Employee Status Management] > \[On-Boarding] > \[Apply on-boarding]
* On the date the staff join, administrators can click "Apply on-boarding" and select the joining date and click "OK".
* The system will remind administrators on the outstanding information.
* After joining, the employee profile can see that the joining status changes to "Formal".
---
# 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/employee-management/add-pending-entry.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.
