> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/managing-teams/access-control/roles.md).

# Roles

### Types of Roles

A team member can have one of five roles:

* Admin: can manage the team, its members, and deployments
* Manager: can perform non-destructive admin actions
* Developer: can create/edit/delete bricks and mods in the team's private scope
* Member: a full member can use mods and integration configurations within the team scope
* Restricted (default): must be added to a permissions group to access team mods and other resources

For enterprise teams, most team members should be "Restricted".

#### Role Permissions Matrix <a href="#block-969a814b8acd4643b98db308047298e1" id="block-969a814b8acd4643b98db308047298e1"></a>

The following table lists the base permissions for each role.

<table><thead><tr><th width="176">Resource/Role</th><th width="100">Admin</th><th width="131">Manager</th><th>Developer</th><th>Member</th><th>Restricted</th></tr></thead><tbody><tr><td>Team Members</td><td><p>View, Invite,</p><p>Edit, Delete</p></td><td>View, Invite</td><td>No</td><td>No</td><td>No</td></tr><tr><td>Groups</td><td>View, Edit, Delete</td><td>View, Edit</td><td>No</td><td>No</td><td>No</td></tr><tr><td>Mods/Packages</td><td>View, Edit, Delete</td><td>View, Edit, Delete</td><td>View, Edit, Delete</td><td>View</td><td>No</td></tr><tr><td>Integration Configurations</td><td>View, Edit, Delete</td><td>View, Call<br><em>No Access to Secrets</em></td><td>View, Call<br><em>No Access to Secrets</em></td><td>View, Call<br><em>No Access to Secrets</em></td><td>No</td></tr><tr><td>Mod Deployments</td><td>View, Edit, Delete</td><td>View, Edit, Pause/Unpause</td><td>No</td><td>No</td><td>No</td></tr><tr><td>Campaigns</td><td>View, Edit</td><td>View, Edit</td><td>No</td><td>No</td><td>No</td></tr><tr><td>Databases</td><td>View, Edit, Delete</td><td>View, Edit</td><td>No</td><td>No</td><td>No</td></tr></tbody></table>

#### Granting Additional Permissions <a href="#block-969a814b8acd4643b98db308047298e1" id="block-969a814b8acd4643b98db308047298e1"></a>

* Use permission groups to authorize read/edit access to specific resources (see [Groups](/managing-teams/access-control/groups.md)). When deploying a mod to a Group, PixieBrix will automatically prompt you to grant the required authorization for the mod.
* Admins/Managers can assign Deployment Manager groups to receive manager access to a Deployment and its related resources (see [Deploying Mods](/deploying-mods.md))

### Changing a Team Member's Role <a href="#block-969a814b8acd4643b98db308047298e1" id="block-969a814b8acd4643b98db308047298e1"></a>

If you decide to change a current team member’s role, you can do so by clicking on their name in the team list on the ***Members*** screen.

On the Member Detail screen, you can edit the member's role by clicking on the Role row. PixieBrix will show a dropdown allowing you to select a new role for the member. PixieBrix will automatically save and apply the new role.

### Applying User Interface Restrictions for Restricted Team Members

{% hint style="info" %}
User interface restrictions for restricted users are only available on Enterprise plans
{% endhint %}

To enable interface restrictions for Restricted team members, you can just contact <support@pixiebrix.com>. Interface restrictions include:

* Hiding references to the PixieBrix Marketplace
* Disabling the ability to deactivate deployments
* Disabling the Page Editor


---

# 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.pixiebrix.com/managing-teams/access-control/roles.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.