> 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/organization-roles-and-permissions.md).

# Organization Roles and Permissions

Organization roles determine which actions a member can perform. Resource sharing can further control access to folders, projects, and connections.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F7Y5zucn83VOu5NVPvk5C%2FG090.mp4?alt=media&token=e6477554-d62e-4b4a-830f-93a4e7aacaf7>" %}

## Before you begin

Permission to manage organization members or roles.

## Roles and access

| Term          | Definition                                                                                                                                                               |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Organization  | The team-level container for members, roles, projects, connections, and settings. Select the correct organization before looking for a resource or calling an operation. |
| Role          | A set of permissions assigned to a member or supported account. Inspect the permission matrix rather than inferring access from the role name.                           |
| Authorization | The decision whether a caller can perform an operation on a resource. Check roles, scopes, organization context, and sharing when access is denied.                      |
| Scope         | A permission category requested by an application or assigned to a key. A scope permits an operation class; resource-level restrictions can still apply.                 |
| Membership    | The account’s association with an organization and assigned access. An invitation alone is not proof of accepted membership.                                             |

## Standard roles and their defaults

StackAI provides four standard organization roles: **Admin, Editor, Viewer, and User**. The tables below describe their default permissions. An organization can customize non-admin role permissions, so check the role settings for the permissions that apply to your organization. Access to a specific project, knowledge base, or connection can impose additional restrictions.

| Role   | What it provides by default                                                                                                                                            | Main restrictions                                                                                                                                                                                                                     |
| ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Admin  | Full organization permissions, including member and role management, security settings, billing, and resource administration.                                          | A StackAI role does not grant permissions in an external provider account.                                                                                                                                                            |
| Editor | Create, edit, run, publish, export, archive, and delete projects. Build knowledge bases, skills, and evaluations. Configure environments and view or manage analytics. | Cannot manage organization security, billing, memberships, or roles by default. Publishing permission does not include release approval permission.                                                                                   |
| Viewer | View and run accessible projects. Read and query accessible knowledge bases. Read evaluations and skills. View and export analytics.                                   | Cannot create or change projects, publish releases, edit skills, or run evaluations by default. Viewer is not strictly read-only: it includes project execution and connection permissions.                                           |
| User   | Read organization information, member lists, knowledge bases, prompts, skills, and evaluation resources. Query accessible knowledge bases and use connections.         | Does not include project read/run or analytics permissions in the standard organization-role defaults. Do not assume the role name grants these permissions; inspect the assigned permissions and the interface access configuration. |

### Permission comparison

**Yes** means the standard role includes the organization-level permission. It does not guarantee access to every resource. **No** means the permission is not included by default.

| Capability                                                    | Admin | Editor | Viewer | User |
| ------------------------------------------------------------- | ----- | ------ | ------ | ---- |
| View organization information and member list                 | Yes   | Yes    | Yes    | Yes  |
| View organization settings                                    | Yes   | Yes    | No     | No   |
| Change organization settings, SSO, billing, or roles          | Yes   | No     | No     | No   |
| Invite or remove members                                      | Yes   | No     | No     | No   |
| Read and run projects                                         | Yes   | Yes    | Yes    | No   |
| Create, update, delete, or archive projects                   | Yes   | Yes    | No     | No   |
| Publish, export, or manage projects                           | Yes   | Yes    | No     | No   |
| Approve release requests                                      | Yes   | No     | No     | No   |
| View environments                                             | Yes   | Yes    | Yes    | No   |
| Create or update environments; write environment variables    | Yes   | Yes    | No     | No   |
| Delete or manage environments                                 | Yes   | No     | No     | No   |
| Read and query knowledge bases                                | Yes   | Yes    | Yes    | Yes  |
| Create, update, delete, synchronize, or index knowledge bases | Yes   | Yes    | No     | No   |
| Manage knowledge-base access                                  | Yes   | No     | No     | No   |
| Read, create, update, delete, or use connections              | Yes   | Yes    | Yes    | Yes  |
| Manage connection access or the connector catalog             | Yes   | No     | No     | No   |
| Read prompts, skills, and evaluations                         | Yes   | Yes    | Yes    | Yes  |
| Edit prompts; create, update, or delete skills                | Yes   | Yes    | No     | No   |
| Create, update, delete, or run evaluations                    | Yes   | Yes    | No     | No   |
| View or export analytics                                      | Yes   | Yes    | Yes    | No   |
| Create or change analytics                                    | Yes   | Yes    | No     | No   |
| Read organization labels                                      | Yes   | Yes    | Yes    | Yes  |
| Create, update, or delete organization labels                 | Yes   | Yes    | No     | No   |
| View or export audit events                                   | Yes   | No     | No     | No   |

### How role permissions and resource access interact

A role defines the types of operations a member can perform. Resource access determines which projects, folders, knowledge bases, or connections they can use for those operations. Check both when a member cannot complete a task.

For example, the default Viewer role includes permission to run projects. This does not expose every private project to that member. Conversely, sharing a project does not automatically grant permission to edit or publish it.

Connection permissions are also separate from provider permissions. Permission to use a connection in StackAI does not let the connected account read a provider folder or record that the provider denies. Permission to create or update connections does not mean that a member can edit every other member's connection.

### Customized roles and personal API keys

A customized standard role can add or remove permissions from its defaults. A custom role uses its configured permission set. Standard roles cannot be renamed or deleted. Review the actual role matrix before assigning access, especially if the organization has changed the defaults.

Members can manage their own personal API keys without an organization-wide key-management permission. A personal key is still limited by its scopes and the owner's effective access. Managing another member's keys is a separate administrative capability. Giving a key a broader scope does not elevate its owner to Admin.

## Assign an organization role

1. Open the organization’s member and role settings.
2. Review the permissions for the role you intend to assign.

![Compare organization and project permissions in the role matrix.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/u0JWXlNbl1gpPnafBNPm/assets/g090-g090-01-matrix.png)

Compare organization and project permissions in the role matrix.

3. Assign the role and confirm the member can perform the required task.

The member has the access needed for their responsibility.

## Behavior and limitations

A role name alone does not describe every resource permission. Some settings require administrator access. Organization membership does not necessarily expose every private project or connection. Review both organization permissions and resource sharing when access is denied.

## Related resources

[Roles and permissions](https://docs.stackai.com/guides-and-quickstarts/organization-administration/roles-and-permissions.md)

[Folder and Project Access](https://docs.stackai.com/technical-reference/identity-access-and-administration/folder-and-project-access.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/organization-roles-and-permissions.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.
