Cyberlop locks its system roles, so nobody can delete them, and it reserves the SuperAdmin name. Deleting any role also needs the role:manage permission. Someone who holds that permission can delete the custom roles that you or your colleagues create.
Why this happens
The roles that ship with Cyberlop get extra care. The API reference marks system roles as undeletable and SuperAdmin as reserved and unchangeable. That keeps the core roles in place for every workspace, whatever else people change around them.
Changing a role takes role:manage, while listing roles takes only role:read. People forget the first.
How to fix it
- Check the role name. Built-in roles such as SuperAdmin and Developer are system roles, so leave them alone.
- Open Administration. Only admins see it. Check that you hold
role:manage. - Without it, ask an administrator who holds it to delete the role for you.
- When you want a different set of rights, create a custom role with the keys you need instead.
Still not working?
The role screen sits in Administration, which our capture did not cover. The steps there may differ from what we describe, so rely on the screen itself. When the app refuses to delete a custom role you made, send us the role name and the exact message.
Before you retire a role, move its people to another role, so nobody loses the access they need for their daily work in the app. Read why you cannot edit the SuperAdmin role and built-in roles. The glossary entry on RBAC gives the background. For help, write to us.
Related questions
- Why can't I edit or delete the SuperAdmin role?
- Which roles come built in?
- How do I create a custom role with specific permissions?
- How are permissions named?
- Why can't I delete the base admin account?
Cyberlop API tokens and permissions: how to issue and limit them
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Still stuck?
Tell us what you see on screen and an engineer will help you sort it out.