Roles & Permissions
Available to organisation administrators as part of the roles and permissions rollout.
The Roles & permissions page is the role catalogue for your organisation: what each role can do, and where you build your own when the built-in four don't fit. For what the built-in roles are and who they are meant for, see Roles and Permissions.
Where to find it
Account menu (your avatar, top of the sidebar) → Organisation → Roles & permissions.
Reading the catalogue, changing a role and deleting one are three separate permissions, all of which the Organisation Admin role carries. Because they are separate, an administrator can be given the catalogue to read without being able to change anything in it.
The catalogue
The left-hand list holds every role that can be given to someone on a team: the built-in roles Strise maintains, then your own, alphabetically within each group. Roles that are never assigned by hand — the Connect API's own role, for instance — are left out. Each entry shows the role's name, a Custom badge if your organisation owns it, and how many permissions it grants.
The list is relative to the team you are working in. A custom role scoped to one team only appears while you have that team selected, so switch teams if a role you created is missing.
Selecting a role shows what it grants on the right:
| Shown | Meaning |
|---|---|
| Available to | Who can be given the role: anyone in the organisation, or only members of the one team it is scoped to. Built-in roles can be given anywhere. |
| Description | What the role is for. |
| Permissions | The permissions it grants, with the total in brackets. |
Permissions are grouped by what they act on — Companies, Members, Reviews, Settings and so on — and each group expands to the individual permissions with a one-line description of each. Only granted permissions are listed here; the full catalogue appears when you edit a role.
Built-in roles are read-only. Their permissions are maintained by Strise, which is also what keeps them current: when a new feature ships, the built-in role that should cover it gets the new permission automatically.
Creating a custom role
Create custom role, at the bottom of the role list, opens a blank role. It appears in the list as a Draft until you save it.
| Field | What it does |
|---|---|
| Start from | Copies the permissions of an existing role as a starting point, or starts from Blank — no permissions. Only offered while creating; it is a starting point, not a link. |
| Role name | What members and administrators see. Required, and unique among your organisation's roles. |
| Description | One line explaining what the role is for. Worth writing — it is what the next administrator reads. |
| Available to | All teams, or one specific team. This decides who may be given the role, not where it takes effect — a role is always granted to a person on a particular team. |
Create saves it; the button stays disabled until the role has a name. Cancel discards the draft without asking. You cannot select another role while a draft or an edit is open.
Picking permissions
The permission picker lists every permission your organisation can grant, grouped by what it acts on. Each group header shows how many of its permissions the role grants, and expands to the individual permissions with a description of each; the counter above the list tracks the total.
The list is the whole of what a custom role can hold. Permissions that only Strise can grant — staff-level and organisation-level administration — are not offered, because custom roles are assigned to people on teams. If you need one of those, it comes from a built-in role instead.
Permissions are independent: granting the permission to change something does not imply the permission to see it, so give a role both halves where both are needed.
Editing and deleting
Edit on a custom role reopens the same form. The permission list you save replaces what the role had, so a saved role grants exactly what is ticked — an Unsaved marker shows while there are changes in flight. Changes apply immediately to everyone holding the role; nobody has to sign out and back in.
Delete removes a custom role for good. It is blocked while anyone still holds the role: the dialog names who they are and asks you to move them to a different role first. Once no one holds it, deleting asks for a confirmation and cannot be undone.
Every create, edit and delete is recorded in the Activity log.
What custom roles don't do
A custom role is a snapshot of the permissions you picked. It does not pick up new permissions when Strise ships a feature — the page says as much on every custom role. A team relying on custom roles should review them when a feature they care about launches, or the people holding them quietly lack access to it. Built-in roles do not have this problem.
Questions?
Reach out to your customer success manager or support@strise.ai.
Last updated on