> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/getting-started/admin-panel-access/admin-roles.md).

# Admin roles

Admin roles allow you to control which parts of the Admin Panel organisers can access. Instead of giving every organiser full access, you can create roles with specific permissions and assign them to the appropriate team members.

For example, you could create a **Marketing** role that allows access to branding and emails while preventing access to users, registrations, or the programme.

{% hint style="info" %}
**Tip:** We recommend creating your Admin roles before adding new organisers. Once an organiser has been created, you can assign the appropriate role from the **Settings** tab of their profile. See [**Admin Panel access**](/getting-started/admin-panel-access.md) for more information.
{% endhint %}

### Create an Admin role

Follow these steps to create a new Admin role:

1. Log in to the **Admin Panel**.
2. Go to **Settings → Admin roles**.
3. Click **+ New role**.
4. Enter a name for the role.
5. Open the **Permissions** tab.
6. Configure the required permissions.
7. Click **Save changes**.

Your new Admin role is now available to assign to organisers.

### Configure permissions

Permissions are organised into categories such as **Users**, **Content**, **Communication**, and **Settings**.

For each category, you can choose one of the following access levels:

* **Full access** – The organiser can view and make changes.
* **View only** – The organiser can view information but cannot make changes.
* **No access** – The organiser cannot access that section of the Admin Panel.

Some categories contain individual permissions. Expand a category to override the default access level for specific features where required.

You can also use **Set all to full access** or **Set all to no access** to quickly configure a role before making individual adjustments.

### Assign an Admin role

Once an Admin role has been created:

1. Go to **Users → Organisers**.
2. Open the organiser's profile.
3. Select the **Settings** tab.
4. Choose the appropriate **Admin role**.
5. Click **Save changes**.

The organiser's permissions are applied immediately.


---

# 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://knowledge-base.letsgetdigital.com/getting-started/admin-panel-access/admin-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.