How do I create a custom role with specific permissions?

Steps

1. Use an account with role:manage, such as a SuperAdmin.
2. Open Administration and go to the roles section, then start a new role with the add control.
3. Give it a name that says what the role is for, such as the Pro Dev example visible in the Activity feed.
4. Choose the permissions. Start with the smallest set that lets the person do the job, and add more only when a real task fails for lack of one.
5. Save.
6. Assign the role to a user. Then open Activity, where a Create · Role entry lists every permission you chose, so you can check your work.

The Administration screens were not part of the pages we reviewed, so button names may differ. Treat the steps as a guide to the order of work, and trust what your screen shows over our wording.

Good to know

A role is a list of permission keys, and each key reads area:action. For developers who run scans and triage findings, a role might hold these:

• The API has the same job. POST /api/roles creates a role, and PUT /api/roles/:id updates one.
• The SuperAdmin name is reserved, you cannot edit that role, and you cannot delete the system roles.
• Roles describe what a person may do. Teams and groups help set what they may reach.

See how permissions are named and which permissions a custom role can hold. This is role-based access control, so keep each role narrow.

Related questions

• How are permissions named?
• Which permissions can I give a custom role?
• Which roles come built in?
• How do I add a new user to my workspace?
• Why can't I edit or delete the SuperAdmin role?

Full tutorial

Cyberlop API tokens and permissions: how to issue and limit them

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre