Roles and permissions

Roles decide what each person can see and change. Every member of a workspace has exactly one role, and buttons and menus appear only for actions you are allowed to take.

The four starter roles

Every workspace starts with these roles.

• Owner. Everything, including billing, roles, settings and deleting the workspace. The Owner role is locked: it cannot be renamed, edited, deleted or given through an invitation.
• Admin. Manages the team, billing and integrations, can view and update company revenue, connect AI agents, and do everything a Member does.
• Member. Captures and reads feedback, reviews AI suggestions, manages opportunities and solutions, records decisions, uses the Analyst and connects AI agents. Cannot see revenue.
• Viewer. Reads the workspace and its feedback. Cannot change anything, use the Analyst or see revenue.

Permissions behind the roles

Roles are bundles of permissions. The product group covers capturing, reading and reviewing feedback, managing opportunities and solutions, recording decisions, using the Analyst, viewing and updating revenue, and connecting AI agents. The settings group covers workspace details, roles, team, billing, integrations, broadcast templates, product context, product areas, custom fields, priority weights and AI linking. Each Settings section opens for people with its permission.

Create or edit a custom role

Who can do this: people with the roles permission (Owner by default).

1. Open Settings › Roles.
2. Choose New role.
3. Give it a name and description.
4. Tick the permissions it should have. A new role starts with Member's permissions and no revenue access.
5. Save. Changes apply to everyone with that role right away.

Assign a role

In Settings › Team, choose a role when you invite someone, or change it later on their row. The list shows every role except Owner.

Delete a role

A role can be deleted only when nobody uses it, and no pending invitation uses it. Move people to another role first.

Good to know

• Removing a member suspends their access immediately. Their work stays.
• The public demo behaves like a Viewer.
• Actions are checked on the server too, so hiding a button is never the only protection.
• There is no ownership transfer yet.

Tips

• Give most people Member. Keep Admin and Owner to a few people.
• Create a "Support" or "Sales" role without settings access if you want people to capture and review but not configure.
• Grant revenue access deliberately; see Revenue visibility.