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

# Access and API grants

Katara checks organization membership, credential permissions, and the target resource’s current authority. Passing one check does not bypass the others. Organization administration does not automatically grant access to every private Brain or original document.

## Brain access is not document access

A **Personal Brain** has no audience grants. A **Team Brain** can grant users or groups **Viewer** or **Editor** access; without audience grants it is owner-only. Its owner manages sharing through **Settings → Sharing/Access**, when the current capabilities permit it. Review the audience, save changes, and reload before reapplying a draft if a revision conflict is reported. See [Brains](https://docs.katara.ai/about/brains/overview.md).

Original sources inherit Brain access, but the owner can also grant **Additional document viewers** through the source-sharing sheet. These recipients can read the shared original, not the Brain’s Wiki or facts. Uploader attribution is not ownership. Removing an additional document grant may leave inherited Brain access intact.

Check both paths when investigating access: the Brain’s audience and the original’s separate grants. A Content Management origin filter only narrows the listing; it grants no permissions. Manage group membership under [Members and groups](https://docs.katara.ai/about/organization-administration/members.md).

## Create an API access grant

1. Choose **API access grants** from the organization menu.
2. Open the creation form. Enter a name and, optionally, a description identifying the integration.
3. Select only the required **Permissions** presets; multiple selections are supported.
4. For browser use, optionally enter a domain in **Allowed browser origins**, using the form’s domain format, such as `example.com`. The current form has one domain field. Leaving it blank creates no origin restriction for server-side/API use.
5. Create the grant and copy the JWT from its one-time display into your integration’s secure configuration.

Available presets are:

| Preset                | Permission set                       |
| --------------------- | ------------------------------------ |
| Website widget answer | Create widget answers                |
| Document read         | Read and list documents              |
| Document write        | Create, update, and delete documents |
| Agent read            | Read and list agents                 |
| Agent run             | Run agents                           |
| Memory read           | Read memory                          |
| Memory write          | Write memory                         |
| Wiki page read        | Read pages                           |
| Wiki page write       | Write pages                          |

Write presets do not implicitly include their corresponding read preset. Memory and page permissions are distinct; document access is not a substitute for either. Grants are not limited to website widgets.

## Protect and maintain credentials

Treat the JWT as a secret. Do not put privileged grants in public repositories, screenshots, chat, or browser code. An origin restriction is not a substitute for secret storage or least privilege.

Use the grant table to review status, owner, permissions, and origins. **Reissue** provides a newly displayed credential; update the consuming integration and verify it works. Use **Revoke** when access is no longer required. Do not assume reissuing proves every previous credential has been invalidated; use explicit revocation for a compromised grant.

Grant-specific MCP default-source management is separate from selecting permissions. A default selects a Q\&A alias, not additional authority; see [MCP tools](https://docs.katara.ai/about/connect-ai-clients/tools.md). For the standard remote MCP connection, follow [browser OAuth setup](https://docs.katara.ai/about/connect-ai-clients/connect.md), rather than pasting an API grant into the client configuration.
