> 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.md).

# Admin panel access

Grant colleagues access to the Admin Panel by adding them as organisers. Each organiser receives their own login, making it easy to collaborate securely on your event.

If different team members require different levels of access, we recommend creating **Admin roles** before adding new organisers. For example, you could create a role for your marketing team that allows access to branding and emails without giving access to users, registrations, the programme, or other areas of the Admin Panel.

Learn more in [**Admin roles**](/getting-started/admin-panel-access/admin-roles.md).

#### Add a new organiser

Follow these steps to add a colleague as an organiser:

1. Log in to the **Admin Panel**.
2. Go to **Users → Organisers**.
3. Click **+ New organiser**.
4. Enter the organiser's:
   * First name
   * Last name
   * Email address
5. Click **Save changes**.
6. *(Optional)* If you have created **Admin roles**, open the organiser's profile, go to the **Settings** tab, select the appropriate [**Admin role**](/getting-started/admin-panel-access/admin-roles.md), and click **Save changes** again.

The organiser will automatically receive an email containing a link to log in to the Admin Panel.

{% hint style="info" %}
**Tip:** If you're using [Admin roles](/getting-started/admin-panel-access/admin-roles.md), we recommend creating them before adding new organisers so you can assign the correct permissions as soon as the organiser has been created.
{% endhint %}


---

# 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.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.