> 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-to-use-company-team-invitation-qr-code-to-invite-new-hires-to-join-team.md).

# \[员工登入] 如何使用公司／团体邀请二维码邀请入职者加入团队？

加入团队功能，能使新入职者透过表格自动加入系统，管理员不用在系统中另外新增员工。&#x20;

如管理员已于已于系统中新增员工，则不用邀请加入团队。

流程如下：

1. 获取加入团队码&#x20;
2. 管理员可在 APP 内获取团队码二维码分享给申请者，使申请者能透过二维码申请加入团队，再由管理员审批加入。&#x20;
3. APP → 通讯录 →［＋］→ 公司／团队二维码

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

2\.  新使用者登记

新使用者下载YOOV WORK APP后，可选择以电邮注册／电话号码登录（**只有电话号码登录等同注册**）。

<br>

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/73019309677/original/tZcFr4lORlZgdv1Km8DLVVZ9wcprCSkO-w.png?1659928211)![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/73019309675/original/0ttrcEWucmnobFpidlCLazMtZccVom5kqw.png?1659928210)

3\.  加入团队

完成注册后，便会进入加入团队页面，可选择以二维码／邀请码加入团队。然后填写申请表，此资料会生成在系统中的员工资料，如有需要管理员亦可之后于系统更改。

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/73020592213/original/FA4cZmyT4sWqeMr2slHq6WnSjAqbTDb-AQ.png?1660631377)


---

# 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-to-use-company-team-invitation-qr-code-to-invite-new-hires-to-join-team.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.
