Custom Roles

The built-in project roles (Viewer, Editor, and Admin) cover most cases, but sometimes you need something in between: a contractor who can build and deploy apps but nothing else, or a reviewer who can approve deployments without editing. A custom role defines that combination.

Custom roles are created per project, under Settings → Roles, by anyone with the project Admin role.

A custom role has two parts:

1. Base access level: Viewer, Editor, or Admin. The role includes everything that level can do.
2. Additional permissions: individual abilities you add on top of the base level.

Pick the closest built-in level, then add the permissions you need.

Select New role and fill in:

• Role name: a label your team will recognize, such as Support lead or Release manager.
• Base access: the starting level (Viewer, Editor, or Admin).
• Additional permissions: the abilities to add on top.

Permissions that come with the base level are shown ticked and greyed out; they're part of the role and can't be removed. You choose everything else.

Two abilities stay with the built-in Admin role and can't be added to a custom role:

• Managing members (adding people and changing their roles)
• Managing roles (creating and editing roles)

Either one amounts to admin control. If someone needs it, give them the Admin role. Billing isn't part of project roles either; it comes from a person's organization role.

A custom role appears in the role dropdown wherever you assign project roles: when adding members and when changing an existing member's role. Each custom role shows its base level and how many permissions it adds.

From the Roles tab, edit a custom role to rename it or change its permissions. Built-in roles can't be edited and carry a Built-in badge.

To delete a custom role, first reassign any members using it to another role. Reflex won't delete a role while members are still assigned to it.

• Managing project access — assign a role to members.
• Roles & permissions — how the built-in roles are made up.