> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/cn/yi-biao-ban/yao-qing-xin-tuan-dui-cheng-yuan.md).
# 邀请新团队成员
了解如何邀请成员加入团队、入职流程是什么样的，以及使用控制面板的团队成员受到哪些限制。
要邀请新团队成员：
1. 前往 [仪表板](https://dashboard.oxylabs.io/en/): **设置 → 团队**.
2. 点击 **+ 邀请团队成员**.
3. 输入队友的电子邮件地址并发送邀请。
受邀者会收到电子邮件邀请。如果他们已经有账户，还会在仪表板中收到通知。接受邀请后，他们的状态将变为 **已激活**.
你可以随时重新发送待处理的邀请或移除团队成员。
### **团队成员入职流程**
一旦你发送邀请，团队成员需要先接受邀请并完成入职流程，才能访问团队仪表板。
1. 受邀者会收到电子邮件邀请。
2. 他们点击 **接受邀请** 以打开仪表板。如果他们还没有账户，需要先注册。
3. 接受邀请后，他们可以访问所有仪表板功能，但以下功能除外 **订阅管理** 和 **团队邀请**.
4. 他们可以随时在以下位置查看成员资格详情或退出团队： **设置 → 团队**.
### **团队成员限制**
团队成员资格附带一些限制，决定谁可以管理团队、最多可加入多少成员，以及现有计划和订阅如何处理。
只有 **团队所有者** 可以邀请新成员。一个团队最多可有 50 名活跃成员。
如果某位用户在 **带有欢迎额度的免费计划** 中加入团队，他们的免费计划将被移除，转而获得团队仪表板和产品的访问权限。
如果用户有有效订阅，在加入团队之前必须先在以下位置取消： **计费与支出** 在加入团队之前。
一次只能属于一个团队。要创建新团队，他们必须先退出当前团队。
---
# 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://developers.oxylabs.io/help-center/cn/yi-biao-ban/yao-qing-xin-tuan-dui-cheng-yuan.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.