> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/setting-up-a-new-environment/environment-and-access/administrators-and-permissions.md).

# Administrators and permissions

Adding administrators, access levels, and the permissions needed to complete setup.

**Home → Settings (gear) → Admins → Add admin**

## Access levels

| Level        | Scope                                         | Typical holder                                           |
| ------------ | --------------------------------------------- | -------------------------------------------------------- |
| Organisation | Every site in the organisation                | Owns organisation-wide settings and manages other admins |
| Site         | One site and every location beneath it        | Responsible for a whole site                             |
| Location     | One location, or a defined group of locations | Responsible for a single site of operation               |

Permissions granted at site level inherit to every location beneath it, and show at each location as inherited. Grant at location level only where the permissions genuinely differ.

The client is usually one of the superadministrators, and grants temporary access to a channel partner or a Gallagher or Kenai representative to help configure.

## Permissions required for setup

### Configuration (required)

* `Administrate configuration`
* `Manage configuration`
* `View configuration`

Manage and View are the minimum. Granting Administrate grants the other two. This covers kiosk setup, branding, location details, visitor flows and module settings.

### Also grant for a Gallagher integration

* `API tokens`
* `Connectors`
* `Integration ops`
* `Number ranges`

Nothing beyond this is needed to complete the setup.

{% hint style="info" %}
Administration permission is normally withheld from external parties. The client grants admin rights, not the partner.
{% endhint %}

{% hint style="warning" %}
The Visitors module carries personal data. Prefer testing alongside the client over granting access to visitor logs.
{% 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://help.security.gallagher.com/knowledge-hub/kenai-user-guide/setting-up-a-new-environment/environment-and-access/administrators-and-permissions.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.