> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/system-settings/system-managers.md).

# System Managers

Add admin users and control what each of them can do.

**System Settings → System Managers** lists the people who can use the admin console, with **ID**, **Name** and **Email**. For each manager you can open **Account settings** and **Action logs** (a log of what they did).

## Add a manager

Click **Add new manager**.

| Section                                         | What you set                                                                                                                                                                                                              |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Account info**                                | **First name**, **Last name**, **Email** and **Password**. Tick **Email new password to user** to send them their password.                                                                                               |
| **Edit affiliate fees** / **Edit partner fees** | Whether the manager may change affiliate and partner commissions.                                                                                                                                                         |
| **Full admin acess**                            | Gives the manager every permission.                                                                                                                                                                                       |
| **Admin notification settings**                 | Which emails the manager receives: new booking, payment received, booking update, trip finished, cancellation, rejection, trip reminder, new review, review reply, invoice sent, refund request, new partner application. |
| **Permissions**                                 | Fine-grained rights per area.                                                                                                                                                                                             |

The permission areas include **Bookings** (view, create, update, delete, cancel, change company), **Orders** (payment orders, including complete and refund), **Drivers**, **Users**, **Companies**, **Vehicles**, **Airports** and **Vehicle types**.

{% hint style="info" %}
Give each person their own account with only the rights they need. **Action logs** then show who did what.
{% 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://codico-dispatch.gitbook.io/documentation/system-settings/system-managers.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.