---
title: Understand how permissions work
description: >-
  How permissions work in depth: switches, levels, reach, dependencies, critical
  permissions and how several roles add up.
icon: list-checks
sidebar:
  order: 16
  label: Permissions explained
  icon: list-checks
---

**A permission is one single ability, such as seeing users, editing a module or sending an email, and a role is the list of permissions that are switched on.** This page explains how the switches behave, so that you can read the permission reference pages and build roles with confidence.

## Where permissions live

Open a role in **Settings → Roles & Permissions** and stay on the **Permissions** tab. The permissions are grouped into **areas**. Use the **Permission areas** navigation on the side to jump between them, and the **Category** and **Status** filters (**Enabled** or **Disabled**) to narrow the list.

Every area has a master switch, **All permissions in …**, which turns the whole area on or off and shows progress such as "3 of 8".

## The kinds of controls

| Control | What it looks like | What it does |
|---|---|---|
| **Switch** | On or off | Gives the ability or not. |
| **Level** | A choice such as **Read** or **Read & Write** | Gives a stronger or weaker version of an ability. **Read & Write** includes **Read**. |
| **Chat contact restrictions** | A list of roles to pick | Limits which roles people with this role may start a new chat with. If nothing is picked, they can contact everyone. Existing chats aren't affected. |

Levels are named for what they do, for example **Read course grades** and **Read & write course grades**. Pick the weakest level that is enough for the job.

## Permissions only add

Access is the sum of everything a person is given. Switching a permission on never takes anything away, and there is no "deny" setting. If someone has too much, remove the permission from the role or take the role away from the person.

A Superadmin passes every check without any switch. See [Understand the Superadmin role](/docs/fuxam-web/settings/super-admin-role).

## Permissions that need other permissions

Many abilities only make sense together. For example, the permission to take part in a course needs the permission to see the course on the dashboard first. When you switch on a permission that needs others, a dialog **Activate Required Permissions?** opens. Click **Activate Required Permissions** to switch them all on, or cancel.

In the reference pages this shows in the **Notes** column as **Needs**.

## Critical permissions

A permission marked **Critical** can change or delete data, not just view it. The legend on the page says: "Critical = can change or delete data, not just view it." When you switch one on, the dialog **Enable this permission?** asks you to confirm. Give critical permissions only to people you trust with that data.

## Course-based permissions

Permissions marked with a tree icon, and **Course-based** in the reference, apply only in the courses a person is assigned to. They don't apply in all courses. To give a person a course-based permission, make sure they have the role in the right courses. See [Assign roles and access to users](/docs/fuxam-web/settings/assign-roles-to-users).

All other permissions apply across the organisation, or across the places where you gave the role.

## Organisation-wide or only for assigned records

Many view, edit and delete permissions come with a choice of reach, for example **Organization-wide** or **For assigned modules**. The first lets the person act on every record of that kind. The second lets them act only on the records they are assigned to, for example the modules they were given access to with a scope. This is how one role can be "all courses" for an administrator and "my courses" for a lecturer.

## Where a permission applies

A role says what is possible. The access scope says where. When you give a role in **Add access**, the sheet shows **What *role name* can do here**. Permissions that don't apply in the places you chose appear separately under **Not used in the selected places**, so nothing is granted by surprise. See [Understand roles, scopes and permissions](/docs/fuxam-web/settings/what-is-a-role).

## Areas that only appear with a feature or setting

Some areas and permissions only appear when your institution uses the feature behind them, for example room management, tuition fees or the learning journey. A few also need an institution setting to be on. The reference pages name the feature or setting in the **Notes** column. If an area is missing in your role, the feature isn't active for your institution.

## Edit modules and fine-grained permissions

Where one permission includes the others, the smaller ones are locked while the big one is on. For example, **Edit modules** already grants everything about modules, so the field-level module permissions are locked until you switch it off.

## Who can switch what

You can only save a role whose permissions you hold yourself, unless you are a Superadmin. See [Know what you can't set up in a role](/docs/fuxam-web/settings/role-limits).

## Permission reference

The reference pages list every permission in plain words, by area:

| Reference page | Areas |
|---|---|
| [Courses, chat, calendar and rooms](/docs/fuxam-web/settings/permissions-courses-chat-calendar) | Courses, Chat, Calendar, Rooms |
| [Campus Management, planning and exams](/docs/fuxam-web/settings/permissions-campus-management) | Management, Planning, Exam Center, Tuition Fees |
| [Users, documents and ratings](/docs/fuxam-web/settings/permissions-people-and-documents) | Users, User Profile, Documents, User Ratings |
| [Statistics, announcements, emails and MCP](/docs/fuxam-web/settings/permissions-insights-and-communication) | Statistics, Statistics Center, Info Hub, Emails, MCP |
| [Settings pages](/docs/fuxam-web/settings/permissions-settings-pages) | Settings |

## Common pitfalls

| Pitfall | Why it happens | How to avoid it |
|---|---|---|
| A person can see a course but not take part | They have **Can see course on dashboard** but not **Participate in course (student)**. | Give the participation permission to students, not to educators. |
| A permission doesn't work in one course | It is course-based and the role wasn't given in that course. | Add the role for that course in the person's **Access** tab. |
| You switched something on and it was already on | A switch only adds. Another role of the person may already give it. | Open the person's **Access** tab to see all their roles. See [Preview what a role can access](/docs/fuxam-web/settings/preview-role-access). |
| You want to take one thing away from a role you use for many people | Removing it changes everyone with the role. | Copy the role, change the copy and move people over. |

## FAQ

**Is there a permission that means 'everything'?**

No single switch, apart from the Superadmin role, which passes every check. The master switch of an area turns on every permission in that area.

**What is the difference between Read and Read & Write?**

**Read** lets people see the data. **Read & Write** also lets them create and change it.

**Why can't I find a permission?**

Its feature may not be active for your institution, or you filtered it out with **Category** or **Status**. Clear the filters.

**How do I check what a role really allows?**

Open the role and click the **Preview** button. See [Preview what a role can access](/docs/fuxam-web/settings/preview-role-access).

## Related topics

**[Create, edit, copy and delete a role](/docs/fuxam-web/settings/set-up-a-role)**

Switch permissions on and off.

**[Preview what a role can access](/docs/fuxam-web/settings/preview-role-access)**

See the result before you save.

**[Know what you can't set up in a role](/docs/fuxam-web/settings/role-limits)**

Locked permissions and limits.

**[Understand roles, scopes and permissions](/docs/fuxam-web/settings/what-is-a-role)**

How permissions, roles and scopes fit together.

