> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/team.md).

# Team and Permissions

## Permissions on AirOps

AirOps offers five roles, each scoped to what a teammate needs to do:

* **Admin:** Full, unrestricted workspace control, including members, billing, and workspace settings.
* **Developer:** Build and run Actions, manage integrations and secrets. Views Brand Kits.
* **Brand Manager:** Manage Brand Kits and Knowledge Bases. Can run and view Workflows and Playbooks, but cannot edit them.
* **Member:** Build and run Actions, edit Grids and Knowledge Bases. Views Brand Kits.
* **Guest:** Grid-only access for contractors and reviewers, with no other workspace access.

### What each role can do

The table below summarizes access by area. **Full** means view and edit, **View only** means read access without editing, and a dash means no access.

| Capability                | Admin | Developer | Brand Manager | Member    | Guest |
| ------------------------- | ----- | --------- | ------------- | --------- | ----- |
| **Content & building**    |       |           |               |           |       |
| Workflows                 | Full  | Full      | View only     | Full      | -     |
| Playbooks                 | Full  | Full      | View only     | Full      | -     |
| Grids                     | Full  | Full      | Full          | Full      | Full  |
| Run Actions               | Full  | Full      | Full          | Full      | -     |
| Prompts & Analytics       | Full  | Full      | Full          | View only | -     |
| **Brand context**         |       |           |               |           |       |
| Brand Kits                | Full  | View only | Full          | View only | -     |
| Knowledge Bases           | Full  | Full      | Full          | Full      | -     |
| **Integrations**          |       |           |               |           |       |
| Integration configuration | Full  | Full      | View only     | View only | -     |
| Secrets & API keys        | Full  | Full      | -             | -         | -     |
| **Workspace management**  |       |           |               |           |       |
| Team management           | Full  | View only | View only     | View only | -     |
| Usage & billing           | Full  | View only | View only     | View only | -     |
| SSO configuration         | Full  | -         | -             | -         | -     |

{% hint style="info" %}
These permissions are enforced everywhere, not just in the web app. The same role-based access applies through Quill and MCP.
{% endhint %}

### Which roles are available on my plan?

The roles you can assign depend on your workspace plan. Higher plans unlock more granular roles.

| Plan       | Available roles                                |
| ---------- | ---------------------------------------------- |
| Solo       | Admin                                          |
| Pro        | Admin, Member                                  |
| Enterprise | Admin, Developer, Brand Manager, Member, Guest |

## How do I invite new team members?

Navigate to :gear: **Settings → Team** to manage existing and invited users within your Workspace. When inviting a teammate, choose the role that matches what they need to do. The invite dialog shows a summary of each role's access as you select it.

<figure><img src="/files/V4zM3Etcyrs8R13Gnbpb" alt=""><figcaption></figcaption></figure>

###


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.airops.com/your-workspace/team.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.