Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Understand roles, scopes and permissions

What a role is, how roles differ from permissions, built-in and custom roles, and where a role applies, in plain language for administrators.

A role is a named set of permissions that you give to people, so that everyone sees and does exactly what their job needs. A permission is one single ability, such as "see users" or "edit a module". The access scope decides where a role applies: everywhere, or only on a specific course, cohort or study program.

This page explains the three building blocks and how they combine. When you know them, every other page in this group (setting up roles, assigning them, the permission reference) will make sense.

The three building blocks

Building block What it answers Example
Permission One single ability. Many permissions have levels, for example Read or Read & Write. Edit course settings
Role A named bundle of permissions with a name, a code and a colour. "Lecturer"
Access scope Where a role applies. The entire organisation, or one course

A person's effective access is the role plus the access scope it was given with. The same role can be given to different people in different places. For example, a lecturer role can be held organisation-wide by one person and only on two courses by another.

Where you manage roles

Go to Settings → Roles & Permissions. The page has up to three sections:

You need the Roles & Permissions permission (area Settings → Organization & Access Rights) to open the page at all. See Settings permissions.

Types of roles

Type What it is Can you change it?
Superadmin The system role with unrestricted access. Every institution has one. Only a Superadmin can open it. Its name, colour and permissions are locked. It can't be deleted or made the default.
Starter roles Ready-made roles that every new institution starts with, for example a student role, a lecturer or teacher role, an administrator role, Planner, Examiner, Statistics, User Management, Management and Information Management. The exact names depend on your type of institution and language. Yes. Edit, copy or delete them like your own roles.
Alumni role A special role for former students, available when the alumni feature is on. Partly. It can never receive permissions that change roles or users. See Know what you can't set up in a role.
Custom roles Roles you create, from a template, from another role or from scratch. Yes.

Exactly one role is the Default role. It is the fallback: if you delete a role, or remove someone's Superadmin status, those people move to the default role.

Roles belong to your institution

Roles are set up per institution. A role named "Lecturer" in one institution is not connected to a role with the same name anywhere else, and changing it affects only the people of your institution who hold it.

What a role contains

Opening a role shows up to six tabs:

Tab What it controls
Permissions What people with this role may see and do. Hidden for the Superadmin role, because it needs no permission list.
Profile Information Which tabs people see on their home dashboard and in user profiles, plus which data the role is asked to fill in. See Set the profile tabs and dashboard for a role.
Dashboard The default dashboard layout for people with this role.
eID Whether people with this role get an eID card and what is on it. See Set eID, onboarding and two-factor for a role.
Onboarding A role-specific invite email.
Security Whether people with this role must use two-factor authentication.

One person, several roles

A person can hold more than one role at the same time. You can give several organisation-wide roles in the Users table, and you can add roles on specific courses, cohorts and so on in the Access tab of the user. Fuxam adds all of them together: the person can do everything that any of their roles allows. There is no "deny": a role can only add abilities, never take them away.

A person must always have at least one role. See Assign roles and access to users.

Common pitfalls

Pitfall Why it happens How to avoid it
"I removed the permission from one role but the person can still do it" Another role of the same person still grants it. Roles add up. Open the Access tab of the person and check all roles and scopes.
Using a role to limit where someone works A role defines what, not where. Give the role with an access scope, such as one cohort.
Giving everyone the Superadmin role It is faster than designing roles. Keep Superadmins to a few people and build roles for everyone else.
Editing a starter role that many people hold Every holder is affected right away. Duplicate the role first, test on the copy, then switch people over.

FAQ

What is the difference between a role and a permission?

A permission is one ability. A role is a named collection of permissions that you can give to many people in one step.

What is the difference between a role and an access scope?

The role says what a person may do. The access scope says where: the entire organisation, or specific courses, cohorts, study programs, modules, rooms, curricula, exams, groups of users, individual users, user fields or management tabs.

Can a role take permissions away from a person?

No. Access is the sum of all roles. To remove an ability, take it out of every role that grants it, or remove the role from the person.

Which role do new people get?

The role you picked when you invited or created them. If a role is removed or deleted, the person falls back to the Default role.

Who can see and change roles?

People whose role has the Roles & Permissions switch turned on in the Settings permissions (area Organization & Access Rights). Only Superadmins can see or edit the Superadmin role.

Last updated on

Was this page helpful?