← Help center

Create your own roles for groups

A role names what kinds of action someone may take: reply to customers, send broadcasts, change playbooks, manage the team, use the Consultant, and so on. Groups give roles to their members (see team-groups). Besides the built-in Admin and Member roles, you can create your own, for example a "Closers" role that replies to customers and runs reports but can't change configuration.

Finding your roles

Go to Settings → Team. The roles are listed under the groups, each with how many scopes it holds and the groups that use it. Admin and Member carry a Built in badge. Click a role to open it, or New role to create one.

Built-in roles

They open read-only: they can't be renamed, changed, or deleted. Create a custom role to choose its scopes.

Creating or changing a role

A role has a name, a description, and its scopes, grouped by area (workspace and team, configuration, secrets, customers and conversations, analytics, developer, Consultant) under their technical names. Tick each scope the role should give, then click Save.

To give the role to people, tick it on a group's Roles card (see team-groups). Everyone in a group holds every role of every group they are in, minus any scope a group withholds.

If someone else saves the same role while you are editing it, your save is refused and you are offered to reload it; reloading discards your unsaved changes.

Who can change a role

You can only give what you hold yourself: creating a role needs every scope it names, and adding a scope to a role needs that scope. Otherwise the save is refused and the message names each scope you lack, such as "the scope secrets.write". Renaming a role or removing a scope is always possible.

Giving anyone more than the Member role gives also needs teams.roles.assign: a role holding a scope Member doesn't, giving a group such a role, removing one of its scope denies, or adding someone to a group whose roles go beyond Member. The owner holds it; the Admin role does not. To let others do it, create a role holding teams.roles.assign (for example "Role managers") and give it to their group. Without it, the save is refused and the message names the owner and the team members who hold it, to ask.

Adding a scope to a role that a group uses gives more to everyone in that group, so Yapper asks you to confirm it is really you: type the role's name, and sign in again first if your last sign-in was more than 15 minutes ago (in a new tab, so your unsaved changes stay). A change that would take the Consultant away from a team member while they are using it is refused; try again once their session ends.

When a role's scopes change, everyone in the groups using it gets the new scopes straight away.

Deleting a role

Open the role and click Delete role. A role that a group still uses can't be deleted: the message names those groups. Untick the role on each group's Roles card first.

Roles and the Consultant

The Consultant can read your roles (each role's scopes and the groups using it) and propose creating a role, changing a custom role's name, description, or scopes, and deleting a role no group uses. It can't change the built-in roles. Nothing changes until someone who can approve proposals approves it; the approval card shows each change. A proposal adding a scope to a role a group uses asks for the same confirmation as the Roles editor: type the role's name, and sign in again if you haven't in the last 15 minutes. Approve it in the dashboard. Whoever approves must hold every scope the proposal gives, and teams.roles.assign when it gives more than Member; otherwise the approval is refused and names what they lack and whom to ask.