> 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 控制「誰看得到什麼、誰能做什麼」的單位。這一組頁面從設定到規劃，依序說明角色怎麼用。

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

<table><thead><tr><th width="260">想做什麼</th><th>看這一頁</th></tr></thead><tbody><tr><td>認識角色類型、建立角色、勾功能權限</td><td><a href="/org/roles/role-permission.md">角色權限管理</a></td></tr><tr><td>控制某個角色看得到、用得到哪些助理與知識庫</td><td><a href="https://github.com/Playma-Co-Ltd/maiagent-user-guide-gitbook/tree/main/zh-tw/org/group-resource-access.md">角色資源存取權限</a></td></tr><tr><td>在成員列表依角色篩選</td><td><a href="https://github.com/Playma-Co-Ltd/maiagent-user-guide-gitbook/tree/main/zh-tw/org/group-member-filtering.md">角色成員篩選</a></td></tr><tr><td>分不清角色與聯絡人</td><td><a href="https://github.com/Playma-Co-Ltd/maiagent-user-guide-gitbook/tree/main/zh-tw/org/contact-role-comparison.md">角色和聯絡人的差異</a></td></tr><tr><td>同仁會自建助理，分享要走申請、逐層上架</td><td><a href="https://github.com/Playma-Co-Ltd/maiagent-user-guide-gitbook/tree/main/zh-tw/org/role-design-guide.md">角色權限規劃指南</a></td></tr></tbody></table>

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

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maiagent.ai/org/roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.