> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/cregis-wallet-guide/zh-tw/accountmanagement/members.md).
# 成員
## **新增成員**
您可以通過輸入成員的郵箱來添加成員。邀請成員後，受邀成員的狀態將變為“待處理”。受邀成員將收到一封電子郵件或消息通知，提示他們註冊或登錄Cregis客戶端以加入團隊。
點擊“確認”後，您可能需要完成Google驗證。完成後將彈出成功提示。
## **刪除成員**
您可以通過團隊成員旁邊的圖標刪除該成員。
確認刪除成員後，您需要完成Google驗證。
---
# 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://support.cregis.com/cregis-wallet-guide/zh-tw/accountmanagement/members.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.
