> For the complete documentation index, see [llms.txt](https://docs.sesamelabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sesamelabs.xyz/product-guides/admin-and-moderation/roles.md).

# Roles

Community Hubs are managed by two types of users: admins and moderators.&#x20;

### Admins&#x20;

All Admins are granted superuser permissions and have the ability to modify the Community Hub itself, create/publish/pause/delete Quests, and moderate users and content. As you might expect, the Admin role can interact with every feature and editable component of a Community Hub.&#x20;

At minimum, there must always be at least 1 Admin role assigned at all times.&#x20;

The Admin role is necessary and sufficient. You can manage an entire Community Hub with just a single Admin.&#x20;

### Moderators

The Moderator role is intended to assist the Admin with moderation duties. This role is restricted from making Community Hub-wide changes, creating or modifying Quests.&#x20;

The Moderator is granted permissions to:

1\) Review submissions (meme contests, photo proof, etc.) for quality and eligibility. \
2\) View existing Quests and associated Quest details.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sesamelabs.xyz/product-guides/admin-and-moderation/roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
