> ## Documentation Index
> Fetch the complete documentation index at: https://docs.groupflow.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Admin Permissions

> The permissions you can give a member, what each one opens up, and how GroupFlow enforces them

Everything an admin can do in GroupFlow comes from a permission on their member record. There is no separate admin account: you give an existing member a permission, and the **Admin Dashboard** appears for them.

To set them, go to **Members & Users** in the admin menu, open the member, and choose the **Edit details** tab. The **Admin Permissions** section lists the permissions as toggles:

> These permissions (roles) give active members access to GroupFlow's administrative functions.

Turn on the ones the member needs and save.

<Note>
  The **Admin Permissions** section only appears for members. A non-member account can't be given permissions, so set their status to **Active Member** on the **Dues** tab first. See [Membership Lifecycle](/concepts/membership-lifecycle).
</Note>

## What each permission grants

Most permissions open one part of the **Admin Dashboard** menu. A member who has none of them has no Admin Dashboard at all.

| Permission | What it opens |
| - | - |
| **Content Management** | The **Design & Web** section — **Web Pages**, **Design Settings**, **SEO**, **Design Templates**, **Hostnames**, and **QR Code** — and editing the website in [Edit Mode](/website/edit-mode) |
| **Elections** | The **Elections** section |
| **Events** | The **Events** section — the event list, **Reports**, **Venues**, and **Settings** |
| **Finances** | The **Finances** section — **Transactions** and **Settings** — and **Subscription Plans** |
| **Forum Moderation** | The **Topic Moderation Queue**, moderating forum topics and posts, and adding chat channels and managing who is in them. Nothing in the Admin Dashboard: these tools are in the members area. |
| **Group Announcements** | The **Announcements** section |
| **Members Management** | The **Dashboard**, **Member Applications** and its **Applications Reports**, **Application Form** and **Settings**, and **Members & Users** with its **Member Counts**, **Admin Emails**, **Profile Form** and **Settings** (Membership Settings) — and **Reports** |
| **Superuser** | **Settings › Group Settings**, plus everything above |

Some sections depend on the group as well as the permission: **Elections** appears only when elections are turned on for your group, **Reports** only when reports are, and **Subscription Plans** only for groups on a trial plan.

<Note>
  **Superuser** has the access of all the other permissions combined, so a Superuser doesn't need any of the others turned on. Give it only to the people who run the group.
</Note>

## How GroupFlow enforces them

* **Permissions only work while the member is active.** If a member's account status stops being **Active** — their membership lapses, or you make them a past member — their permissions stop working until they're active again. The permissions stay on the record; nothing is lost.
* **The check happens in the backend, not the menu.** Hiding a menu item isn't what protects your group's data. GroupFlow checks permissions again on every request, so data a member has no permission for stays out of reach however they get to the page.
* **Any one permission grants the Admin Dashboard.** A member with only **Events** sees the Admin Dashboard, with only the **Events** section in it.

## Related: who sees a menu link

A navigation link can be limited to members with a particular permission, using its **Access by permission role** setting. That controls who sees the link, not who can open the page. See [Navigation Menus](/website/navigation).

## Related: event staff permissions

Event staff permissions are separate from the permissions above, and are granted on one event at a time. On an event's staff list, each staff member has their own toggles:

* **Take attendance**
* **Edit event details**
* **Send announcements**
* **Moderate event forum**
* **Manage staff permissions**

Use these to let a volunteer run one event without giving them the **Events** permission, which applies to every event in the group. A member with **Events** already has all five on every event, and so does the member who created the event.

<CardGroup cols={2}>
  <Card title="Members & Profiles" icon="users" href="/guides/members">
    What members and admins each see of a member record
  </Card>

  <Card title="Your Website" icon="browser" href="/website/overview">
    What the Content Management permission lets you edit
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.