> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brew.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Team and Roles

> What organization admins and members can do in Brew, which brands each role reaches, and what an INSUFFICIENT_ROLE error means.

Everyone on your Brew team has one of two roles: **organization admin** or **member**. The role decides which brands a person can reach and which organization-level actions they can take. Your team list lives under **Settings → Team**.

## What Each Role Can Do

| | Organization admin | Member |
| - | - | - |
| Brands they can reach | Every brand in the organization | Only the brands an admin added them to |
| Work on emails, automations, and contacts in those brands | Yes | Yes |
| Comment on emails | Yes | Yes |
| Add a member to a brand, or make someone an admin | Yes | No |
| Create and revoke API keys | Yes | No |
| Delete a brand | Yes | No |
| Approve a send held for review | Yes | No |
| Extract a new brand over MCP (**All brands**, then `onboard_brand`) | Yes | No |
| Get the send-limit notification | Yes | No |

Anyone in the organization can comment, with no extra permission ([Comments](/create-emails/comments)).

**Delete brand** shows only for admins, at the bottom of the brand's **Details** ([Multiple Brands](/brand/multiple-brands)).

A send is held for review only if your organization requires send approval. Nothing goes out until an admin approves it, and a rejection cancels the run ([Send Options](/create-emails/send-options)).

## Roles and Connections

An MCP connection made with OAuth has the access of the person who connected it. An admin's connection reaches every brand, and a member's reaches only their brands ([MCP Authentication and Scoping](/api-reference/mcp/authentication-and-scoping)).

An API key works differently. Its reach is set when an admin creates it: one brand, or the whole organization.

A role and a key don't affect each other. An organization-wide key gives no one a role. Making someone an admin doesn't change what an existing key can reach ([Organization and Brand Credentials](/api-reference/api/organization-and-brand-scope)).

Key management needs a signed-in admin in the dashboard. An API key, an OAuth connection, the MCP server, and the CLI can't create or revoke keys.

## When You Don't Have Access

An action your role doesn't allow returns `403 INSUFFICIENT_ROLE`. Its `param` says what's missing:

| `param` | Meaning | Fix |
| - | - | - |
| `member` | You aren't a member of this brand. | Ask an organization admin to add you to the brand. |
| `org_admin` | The action needs the organization admin role. | Ask an admin to run it, or to make you an admin. |

A different error, `403 ORG_SCOPE_REQUIRED`, is about an API key's reach, not a person's role. [Organization and Brand Credentials](/api-reference/api/organization-and-brand-scope#403-org_scope_required) explains the difference.

## Related

* [Multiple Brands](/brand/multiple-brands): what is shared across brands and what each brand keeps
* [Settings](/settings/settings): API keys, MCP connections, and AI models
* [Organization and Brand Credentials](/api-reference/api/organization-and-brand-scope): key scope and the `403` codes

## Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:

**Self-Service Tools**

> **Search Documentation**
>
> Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages.

> **[Ask ChatGPT or Claude](#top)**
>
> Click here to open the **Copy page** menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.

**Talk to Our Team**

> **[Schedule a Call](https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ1iYoRUG1J792XQpbuQLjSRRDupr7MwraFK-HQRCtTYdBmrQi8nZu2qXfzKQigb8gbKJK3KN3-R)**
>
> Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions.

> **Call Us Directly**
>
> Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions.

> **Slack Channel**
>
> Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses.

> **[Email Support](mailto:support@brew.new)**
>
> Contact us at **[support@brew.new](mailto:support@brew.new)** for detailed inquiries or if you prefer not to use Slack.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.