> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/identity-access-and-administration.md).

# Identity, Access, and Administration

Understand how roles, resource permissions, credentials, and membership affect access to StackAI.

* [Organization Roles and Permissions](/technical-reference/identity-access-and-administration/organization-roles-and-permissions.md)
* [Folder and Project Access](/technical-reference/identity-access-and-administration/folder-and-project-access.md)
* [Connection Access and Execution Identity](/technical-reference/identity-access-and-administration/connection-access-and-execution-identity.md)
* [SSO, Social Sign-In, and Account Identity](/technical-reference/identity-access-and-administration/sso-social-sign-in-and-account-identity.md)
* [Invitations, Membership, and Access Removal](/technical-reference/identity-access-and-administration/invitations-membership-and-access-removal.md)
* [Personal API Keys: Scopes, Expiration, and Revocation](/technical-reference/identity-access-and-administration/personal-api-keys-scopes-expiration-and-revocation.md)
* [Audit Events and API Key Activity](/technical-reference/identity-access-and-administration/audit-events-and-api-key-activity.md)
* [Resource Deletion and Its Effects](/technical-reference/identity-access-and-administration/resource-deletion-and-its-effects.md)


---

# 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.stackai.com/technical-reference/identity-access-and-administration.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.
