Custom roles

Admin → Custom roles lets you carve out a role that grants a narrow slice of admin power instead of full org-admin. A Billing manager who can touch billing but nothing else, a Templates editor who can edit the house templates and nothing else — that kind of thing.

Creating a role

Give the role a key (billing_manager) and a label ("Billing manager"), then create it and edit its permission keys. A custom role is assigned in addition to a member's primary system role — it doesn't replace it. Members keep their system role and pick up the custom role's extra permissions on top.

System roles are read-only

Owner, Admin, and Member are built-in. They're listed with their permission bundles so you can see exactly what each one grants, but you can't edit them — their bundles are fixed and the same in every organisation. They're managed automatically as people join and change roles.

Disabling a role is not available yet. The page shows the control in a disabled state with a note to that effect; it's tracked for a later release. For now, to remove a custom role's reach you delete the role outright, which detaches it from everyone who held it.

Related: Users & invites · Groups.