---
title: Know what you can't set up in a role
description: >-
  What cannot be set up or changed in roles: locked Superadmin settings,
  protected default and last roles, permission ceilings and other edge cases.
icon: lock
sidebar:
  order: 15
  label: Role limits
  icon: lock
---

**Some things can't be set up in a role, and some are locked on purpose so that nobody can lock themselves out or give away more than they hold.** This page lists every limit, so you know in advance why a switch is greyed out or a save is refused.

## Limits that protect the Superadmin role

The Superadmin role is a built-in role with special rules. For the full story see [Understand the Superadmin role](/docs/fuxam-web/settings/super-admin-role).

| You can't … | Why |
|---|---|
| Rename it, change its colour or its code | The name, colour picker and code are locked on the Superadmin role. |
| Edit its permissions | It has no **Permissions** tab. A Superadmin passes every check, so there is nothing to switch on or off. |
| Delete it or make it the default role | **Delete** and **Set Default** are disabled. A default role must carry permissions for people who are moved to it. |
| See or open it as a non-Superadmin | The message says: "Only Superadmins can view or edit the Superadmin role." |
| Give it through an access scope or in a template | The Superadmin role can't be assigned in **Add access**, via **Everyone holding a role**, or inside an access template. Use the **Superadmins** section instead. |
| Remove the last Superadmin | "At least one Superadmin must remain." |
| Remove your own Superadmin access | "You cannot remove your own Superadmin access." Ask another Superadmin. |
| Remove another Superadmin as a non-Superadmin | "Only Superadmins can remove other Superadmins." |
| Delete a Superadmin from the institution | "Superadmins cannot be deleted." Remove the Superadmin status first. |

## Limits on who can change a role

| You can't … | Why | What to do |
|---|---|---|
| Edit your own role | If you are not a Superadmin, your own role opens as read-only with the message "You cannot edit your own role. Ask another administrator to change it for you." | Ask another administrator. |
| Give permissions you don't have yourself | A non-Superadmin can only save a role whose permissions they hold themselves. In the access sheet you see "You cannot grant: …" for roles you can't hand out. | Ask someone who holds those permissions, or a Superadmin. |
| Open the roles page without the **Roles & Permissions** permission | The page needs the permission **Roles & Permissions** in the area **Organization & Access Rights**. | Ask an administrator to turn it on in your role. |
| Edit roles while holding the alumni role | A person with the alumni role can't edit roles, even if another role of theirs would allow it. | Use a different account for administration. |

## Limits inside a role

| You can't … | Why |
|---|---|
| Leave the role name empty or longer than 100 characters | The **Role Name** field needs 1 to 100 characters. |
| Use a role code that already exists | Codes are unique in your institution. The save fails with a message about a duplicate code. Leave the field empty and one is generated for you. |
| Switch on a permission without the permissions it needs | Some permissions depend on others. Switching one on opens **Activate Required Permissions?** and offers to switch on the permissions it requires. |
| Set fine-grained module fields while **Edit modules** is on | **Edit modules** already grants everything, so the field-level module permissions are locked until you switch it off. |
| Deny something | Permissions only add. There is no "deny". To take something away, remove it from the role or take the role away from the person. |
| Make a permission apply on one course only inside the role | A role holds permissions only. Where it applies is decided when you give the role to someone. See [Assign roles and access to users](/docs/fuxam-web/settings/assign-roles-to-users). |
| Give the alumni staff permissions to the alumni role | The alumni role can't hold the staff permissions for managing alumni. Only the self-service permissions of alumni are allowed on it. |

## Limits when you give a role to someone

| You can't … | Why |
|---|---|
| Remove a person's last role | A person always keeps at least one role. |
| Give a place that the role has no permission for | A place that the role has no permission for is greyed out. Add a permission for that kind of record to the role first, or pick another role. |
| Select **All** records inside a place | Where the sheet says "Granting All is not available yet", select the specific records. Selecting specific records is not the same as **The entire organisation**. |
| Give the same role twice as the organisation-wide role | The sheet says the role is already the person's entire-organisation assignment. Pick other places. |

## Limits when you delete a role

| You can't … | Why |
|---|---|
| Delete the default role | People who lose their role must land somewhere. Make another role the default first. |
| Delete the last remaining role | There must always be at least one role. |
| Delete a role and keep its people on it | When you delete a role, everyone who had it moves to the default role. |

## Limits of the role tabs

| Where | Limit |
|---|---|
| **Security** | **Require two-factor authentication** works with authenticator apps only, and is blocked while a single sign-on alias is turned on for the role. |
| **Preview** | The dialog shows permissions, profile information and dashboard. It doesn't show eID, onboarding or security settings. |

## Limits of saving

| Message | What it means |
|---|---|
| **Unsaved role changes** | You tried to leave the role page with open changes. Choose **Stay**, save everything or discard everything. |
| A message that the role changed before the save completed | Someone else saved the same role while you worked. Reload and apply your change again. |

## Common pitfalls

| Pitfall | Why it happens | How to avoid it |
|---|---|---|
| You can't find the Superadmin role in the list | You are not a Superadmin. | Ask a Superadmin. |
| You can't open your own role | Your own role is read-only for you. | Ask another administrator. |
| A permission is greyed out | It is locked by a dependency, or you don't hold it yourself. | Read the hint next to the switch. |
| You deleted a role and people changed their access | They moved to the default role. | Check the default role before you delete another one. |

## FAQ

**Can I make a role that denies one thing?**

No. Access is the sum of everything a person is given. If someone has too much, remove the role or permission that gives it.

**Can I give a role more permissions than I have?**

Not as a non-Superadmin. A Superadmin can give any permission.

**What if I locked myself out?**

Ask another Superadmin or administrator. There is always at least one Superadmin, and nobody can remove the last one.

## Related topics

**[Understand the Superadmin role](/docs/fuxam-web/settings/super-admin-role)**

The one role that can't be changed or removed.

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

The steps for everything that is allowed.

**[Understand how permissions work](/docs/fuxam-web/settings/permissions-explained)**

Dependencies, critical permissions and levels.

**[Bundle roles into access templates](/docs/fuxam-web/settings/access-templates)**

What a template can contain.

