# Roles and permissions

> Make your server's own Jellyn roles, each opening exactly the parts of the dashboard and moderator panel a team needs.

Your staff and management Discord roles (from `/setup`) are a good start, but most teams need more in between: a moderator who can run in-game commands but not change settings, an applications team, an activity manager. That is what **Jellyn roles** are for.

## What a role is

A role is made on the **Roles** page of the dashboard. It has:

- a **name** and a **colour**,
- a **place in the order** (1 is the highest),
- the **permissions** it gives,
- and, if you like, the **Discord role** it is linked to.

A server can have up to 15 roles; with <Badge color="grape">Jellyn+</Badge> there is no limit. Change the order with the arrows on a role, or hold it and slide it into place.

## Who holds a role

- **Given by hand**: in the role's window, by Discord ID.
- **Through Discord**: everyone with its linked Discord role holds it. This is decided from the Discord roles someone has right now, so it is immediate on the website, and Jellyn keeps its list of holders in step within a couple of minutes.

Holding any role makes someone staff on Jellyn, in Discord commands too.

## The permissions

<Tabs>
  <Tab title="Moderator panel">
    | Permission | Lets them |
    | --- | --- |
    | Log bans | Log bans, not only lesser punishments |
    | Void punishments | Void a punishment log |
    | Run in-game commands | Use the command box and the player card's in-game actions |
    | Bans and ranks in game | Run bans and other restricted commands in game, like raid rollback |
    | Message players | Message players on Discord from their card |
  </Tab>
  <Tab title="Dashboard">
    Each opens one page or part of the dashboard: **Members**, **Infractions**, **Types and rules**, **Applications**, **Activity**, **Leave of absence**, **Documents** (the Resources permission), **Audit log**, **Discord**, **ER:LC overview**, **Session settings**, **Automations**, **Vehicles**, and **Reminders & actions**.
  </Tab>
  <Tab title="The server">
    | Permission | Lets them |
    | --- | --- |
    | Roles | Make, change and give Jellyn roles (below their own) |
    | Server settings | Change the server's settings and log channels |
    | ER:LC connection | Link and change the ER:LC servers |
    | Administrator | Everything, except what only the owner can do |
  </Tab>
</Tabs>

These sit on top of the Discord roles from `/setup`:

- A **management** Discord role has every permission of the first two groups.
- The **owner** and Discord **admins** (Administrator or Manage Server) have all of them.
- A **staff** Discord role alone has none: staff get shifts, punishment logs and the moderator panel.

## Who can manage roles

Whoever has the **Roles** permission; the owner and Discord admins always can. Someone who isn't the owner or a Discord admin works **below their own highest role**: they change, order, remove and give only roles under it, and only put permissions on a role that they hold themselves. A new role goes to the bottom of the order.

<Note>
  Discord slash commands that need management, like `/infraction` and `/promotion`, still go by the management Discord roles from `/setup`.
</Note>

Every change to a role is in the [audit log](/moderation/audit-log).