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

# Identity and Access

- [Member Provisioning: SCIM / Invitations / SSO](https://docs.maiagent.ai/tech/en/identity-and-access/member-provisioning.md): Three ways to add your personnel as MaiAgent organization members—SCIM provisioning API (for customer IT teams and ISV-managed organizations), admin console invitations, and automatic provisioning thr
- [Real-Time Synchronization: Call from User Events](https://docs.maiagent.ai/tech/en/identity-and-access/member-provisioning/member-event-sync.md): If your product is a web service, call SCIM in real time when users are created, updated, or deactivated to keep MaiAgent organization members synchronized with your system at all times. Includes a re
- [Roster Synchronization Tools: CSV / JSON / Database](https://docs.maiagent.ai/tech/en/identity-and-access/member-provisioning/member-roster-sync.md): Automatically provision members without an IdP: a ready-to-use roster sync tool that accepts CSV, JSON, or database exports to create, update, and deactivate organization members through SCIM, with su
- [SSO and Identity Integration Overview](https://docs.maiagent.ai/tech/en/identity-and-access/sso-overview.md): An overview of MaiAgent sign-in and identity integration options: built-in accounts, SAML, EIP, Keycloak, Cloudflare Access, LDAP password sign-in, and Google sign-in, including use cases, configurati
- [SAML SSO Integration](https://docs.maiagent.ai/tech/en/identity-and-access/sso-overview/saml-sso.md): SAML SSO integration: IdP and SP architecture, email normalization, automatic account creation and conflict handling, configuration steps, limitations, and troubleshooting.
- [MaiAgent as an OAuth Authorization Server](https://docs.maiagent.ai/tech/en/identity-and-access/maiagent-oauth-server.md): Connect MCP clients such as Claude to MaiAgent MCP with OAuth 2.1 (authorization code + PKCE): endpoints, application registration, Redirect URIs, token lifetime and rotation, and how scopes actually
- [Knowledge Management Permissions (Query Metadata) Overview](https://docs.maiagent.ai/tech/en/identity-and-access/zhi-shi-guan-li-quan-xian-query-metadata-cha-xun-yuan-zi-liao-zong-lan.md): Use Query Metadata to control the knowledge an Agent can retrieve. See the Getting Started subpage for detailed configuration.
- [Start Building—Use JSON Format](https://docs.maiagent.ai/tech/en/identity-and-access/zhi-shi-guan-li-quan-xian-query-metadata-cha-xun-yuan-zi-liao-zong-lan/json-interfaces.md): For more complex filtering conditions, use JSON to specify IDs directly at each level, such as knowledge bases and individual documents.


---

# 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/en/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.
