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

# Roles & Permissions

> Understand Signal's role system and how it controls what each staff member can see and do.

Signal uses a hierarchical role system to control access. Each staff member is assigned one role per school, and that role determines what they can see, create, and manage throughout the platform.

## Role overview

| Role             | Access level                                                                                                                   |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Owner**        | Full access to everything — incidents, staff incidents, all settings, and staff management. Manages the Signal account itself. |
| **DSL**          | Full safeguarding access — student and staff incidents, all settings, and staff management.                                    |
| **Deputy DSL**   | Same access as DSL.                                                                                                            |
| **School Admin** | Can manage settings (categories, locations, groups, and more) but has limited incident access.                                 |
| **Contributor**  | View students and all incidents, receive alerts, and create new incidents. Cannot access settings.                             |
| **Member**       | A placeholder role with no login access. Used for staff who should appear in the system but do not need to use it.             |

<Info>
  Roles are hierarchical — each role includes all the permissions of the roles below it. For example, a School Admin can do everything a Contributor can, plus manage settings.
</Info>

## How roles affect what you see

Your role determines which items appear in the sidebar, which dashboard sections are visible, and what actions you can take.

<Accordion title="Owner, DSL, and Deputy DSL">
  You see the full sidebar, including staff incidents, all settings pages, and staff management. Your dashboard shows both student and staff mentions, alerts, drafts, upcoming reviews, and pending monitors.
</Accordion>

<Accordion title="School Admin">
  You can access settings pages to manage transfers, students, groups, and other configuration. You cannot view incidents and cannot view staff incidents.
</Accordion>

<Accordion title="Contributor">
  You can view and create student incidents, add comments, and receive alerts. You cannot manage settings or access staff incidents.
</Accordion>

<Accordion title="Member">
  You cannot log in to Signal. This role is used for staff members who need to appear in lists (for example, as a contact or witness on an incident) but do not need their own access.
</Accordion>

## Staff incidents require a privileged role

<Warning>
  Staff incidents are only accessible to staff with the Owner, DSL, or Deputy DSL role. If you have the School Admin or Contributor role, you will not see the Staff Incidents section at all. This restriction protects the sensitivity of concerns involving staff members.
</Warning>

Additionally, Signal enforces **self-exclusion** on staff incidents. If you are named in a staff incident, you are automatically prevented from viewing it — even if you hold the DSL role.

## Next steps

<CardGroup cols={2}>
  <Card title="Managing Staff Members" icon="users" href="/docs/staff/managing-staff">
    Learn how to add, invite, edit, and remove staff.
  </Card>

  <Card title="Staff Groups" icon="users" href="/docs/staff/staff-groups">
    Organise staff into groups for access control and alert routing.
  </Card>
</CardGroup>