> 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/tech/identity-and-access.md).

# 身分與權限

- [成員開通：SCIM／邀請／SSO](https://docs.maiagent.ai/tech/identity-and-access/member-provisioning.md): 讓您的人員成為 MaiAgent 組織成員的三條路：SCIM 開通 API（適合客戶 IT 與 ISV 代管）、後台邀請、SSO 登入自動開通；以及與 MaiGPT 成員身分嵌入的銜接
- [即時同步：在使用者事件中呼叫](https://docs.maiagent.ai/tech/identity-and-access/member-provisioning/member-event-sync.md): 您的產品是 Web 服務時，在新增／修改／停用使用者的事件中即時呼叫 SCIM，讓 MaiAgent 組織成員與您的系統隨時一致；附可直接引用的 client 與接法
- [名單同步工具：CSV／JSON／資料庫](https://docs.maiagent.ai/tech/identity-and-access/member-provisioning/member-roster-sync.md): 沒有 IdP 也能自動開通成員：一支現成的名單同步工具，吃 CSV、JSON 或從資料庫匯出的名單，透過 SCIM 建立、更新、停用組織成員，可排程執行
- [SSO 與身分整合總覽](https://docs.maiagent.ai/tech/identity-and-access/sso-overview.md): MaiAgent 支援的登入與身分整合方式總覽：內建帳號、SAML、EIP、Keycloak、Cloudflare Access、LDAP 帳密登入與 Google 帳號登入，各自的適用情境、設定入口，以及和成員開通的搭配
- [SAML SSO 單一登入整合](https://docs.maiagent.ai/tech/identity-and-access/sso-overview/saml-sso.md): SAML SSO 單一登入整合：IdP 與 SP 的架構、Email 正規化、帳號自動建立與衝突處理、配置步驟、限制與疑難排解。
- [MaiAgent 作為 OAuth 授權伺服器](https://docs.maiagent.ai/tech/identity-and-access/maiagent-oauth-server.md): 讓 Claude 等 MCP 客戶端以 OAuth 2.1（授權碼＋PKCE）連線 MaiAgent MCP：端點、應用程式註冊、Redirect URI、權杖效期與輪替，以及 scope 的實際作用
- [知識管理權限(Query Metadata / 查詢元資料) 總覽](https://docs.maiagent.ai/tech/identity-and-access/zhi-shi-guan-li-quan-xian-query-metadata-cha-xun-yuan-zi-liao-zong-lan.md): 透過 Query Metadata（查詢元資料）控管 Agent 可檢索的知識範圍，詳細設定方式見「開始建構」子頁
- [開始建構—使用 JSON 格式](https://docs.maiagent.ai/tech/identity-and-access/zhi-shi-guan-li-quan-xian-query-metadata-cha-xun-yuan-zi-liao-zong-lan/json-interfaces.md): 若您想要撰寫更複雜的篩選條件，可使用 JSON 格式直接以各層級 (如知識庫、單一文件等) ID 指定


---

# 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/tech/identity-and-access.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.