> 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-login/how-do-employees-log-in-after-being-added-in-backend.md).
# \[员工登入] 在后台新增员工后，员工要如何登入？
请员工在手机下载YOOV WORK应用程式，根据管理员为员工在系统绑定的联络资讯进行注册／登入。
**不同绑定方法注册及登入程序**
电邮地址： 先点击＂邮箱注册＂页面，输入邮箱资料，以电邮接收验证码然后登入。
**＊使用手机号码登入，无需注册＊**
**电话号码：先点击＂手机登入＂页面，无需注册，以手机短讯接收验证码然后登入。**
---
# 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-login/how-do-employees-log-in-after-being-added-in-backend.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.