> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/org/roles.md).

# 角色與權限

角色是 MaiAgent 控制「誰看得到什麼、誰能做什麼」的單位。這一組頁面從設定到規劃，依序說明角色怎麼用。

角色決定成員看得到哪些功能、能不能新建、以及看得到哪些 Agent 與知識庫。依你要做的事挑頁面：

<table><thead><tr><th width="260">想做什麼</th><th>看這一頁</th></tr></thead><tbody><tr><td>認識角色類型、建立角色、勾功能權限</td><td><a href="https://docs.maiagent.ai/org/roles/role-permission.md">角色權限管理</a></td></tr><tr><td>把同一份權限設定一次套用到多個角色、查成員的權限來自哪個角色</td><td><a href="https://docs.maiagent.ai/org/roles/role-batch-permissions.md">批次設定角色權限</a>、<a href="https://docs.maiagent.ai/org/overview/member.md#effective-permissions">檢視成員的有效權限</a></td></tr><tr><td>控制某個角色看得到、用得到哪些 Agent 與知識庫</td><td><a href="https://docs.maiagent.ai/org/roles/group-resource-access.md">角色資源存取權限</a></td></tr><tr><td>在成員列表依角色篩選</td><td><a href="https://docs.maiagent.ai/org/roles/group-member-filtering.md">角色成員篩選</a></td></tr><tr><td>分不清角色與聯絡人</td><td><a href="https://docs.maiagent.ai/org/roles/contact-role-comparison.md">角色和聯絡人的差異</a></td></tr><tr><td>同仁會自建 Agent，分享要走申請、逐層上架</td><td><a href="https://docs.maiagent.ai/org/roles/role-design-guide.md">角色權限規劃指南</a></td></tr><tr><td>限制客服轉交其他同事正在服務的對話</td><td><a href="https://docs.maiagent.ai/org/roles/transfer-others-permission.md">轉交他人對話權限</a></td></tr></tbody></table>

{% hint style="info" %}
**簡單理解：**

規劃指南講「角色該怎麼切」，其他頁講「按鈕在哪、怎麼設」。第一次規劃組織的角色，先讀規劃指南，再回來照各頁設定。
{% endhint %}

## 批次設定權限與成員有效權限 <a href="#role-permission-governance" id="role-permission-governance"></a>

角色一多，逐一修改容易漏改，也很難一眼看出某位成員的權限是哪個角色給的。角色列表與成員列表各有一個入口，兩者都需要組織概覽權限（能進入 <mark style="color:blue;">編輯角色權限</mark> 與成員管理頁的管理者）：

* **批次設定權限**：在角色列表點 <mark style="color:blue;">批次設定權限</mark>，先編好一份權限設定（可從空白開始，或取用既有角色的設定），再勾選要套用的自訂角色，也可以同時新增角色。套用前會逐一列出每個角色會新增、收回哪些項目，確認後一次寫入。操作說明見 [批次設定角色權限](https://docs.maiagent.ai/org/roles/role-batch-permissions.md)。
* **檢視有效權限**：在成員列表點成員操作欄的盾牌圖示，查看這位成員所有角色合併後實際擁有的功能權限、MaiGPT 使用範圍與資源，以及每一項由哪些角色授予。操作說明見 [成員管理：檢視成員的有效權限](https://docs.maiagent.ai/org/overview/member.md#effective-permissions)。

<figure><img src="https://1593648278-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fmzb5NG9GDzFP2YDKeYVl%2Fuploads%2Fgit-blob-288b2e260222c37bc1837a1447ef6314b72898bc%2Frole-batch-permissions-entry.png?alt=media" alt="角色列表右上方的批次設定權限按鈕"><figcaption><p>角色列表右上方的批次設定權限入口</p></figcaption></figure>


---

# 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.maiagent.ai/org/roles.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.
