> 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/register-employee.md).
# Register Employee
## 1. Function Description
* After adding new employees, you need to invite them to sign up and use the APP.
① Operation steps: \
\[Employee] > \[Employee List] > \[Advanced Search] > \[Unregistered]\
② Search for all unregistered employees. \
③ Taking employee Peter as an example, after confirming that he has filled in his work email address, the admin can \[Send invitation].\
④ The system will send an invitation email to the employee. After receiving the email, the recruit may click \[Enter the system] to proceed.
* If the recruit is not registered yet, he needs to click \[Register] to enter the following page to complete the registration process.
* Please be reminded that the email address must be the same as the employee profile in the system. Take Peter as an example, would be . After successful registration, he can log in to the system.
* After logging in and rechecking Peter's record, his registration status will be changed from unregistered to registered. This means that he can login to the backend panel (also needs to set administrator permissions) and the App.
* To protect the privacy of employee accounts, the administrator cannot change the employee's information after the employee is registered. If employees need to make changes, please login to the backend panel first and click \[User center] on the top right.
---
# 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/register-employee.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.
