> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/moderators.md).

# Event Moderators

People with access to the backend of your event.

Moderators have permissions. Based on those permissions these people can do certain things in your event.

{% hint style="danger" %}
**Keep permissions minimal.** Only give people the access they need to do their work.
{% endhint %}

<details>

<summary><strong>3 types of moderators</strong></summary>

* [Supermoderator](https://app.gitbook.com/s/MoqjcHMq42F8FFp86l8S/features/company-moderators)
* [Platform moderator](/event/general/moderators/platform-moderators.md)
* [Hardware moderator](/event/general/moderators/hardware-moderators.md)

</details>

{% hint style="warning" %}
**Blocked users can't be moderators.** If a user is [blocked](https://app.gitbook.com/s/MoqjcHMq42F8FFp86l8S/features/blocked-users) from your company or event, they can't be searched for or added as a moderator. If they get blocked while already a moderator, they automatically lose that access.
{% endhint %}

### Permissions

Permissions **determine which parts** of the backend a moderator **can acces, view and/or edit**.

<details>

<summary>Examples of permissions</summary>

* *View a substation*
* *Edit accreditation*
* *Get information based on QR codes*
* *Check people in & out of event*

</details>

### Limit when enabled

You can **add a start and end date to each moderator**. Outside of those dates, their permissions are automatically inactive.

{% hint style="info" %}
**Best practice:** Set an active date range so access expires automatically when it's no longer needed.
{% 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://docs.eventication.com/event/general/moderators.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.