> 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-hk/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-hk/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.