Roles and permissions

Roles let workspace administrators shape what each person in the team can see and do. Admins keep full control of the workspace; team members get a focused, simplified experience without the setup and organisation tools — which means less to explain, less to get wrong, and a much easier rollout.

Roles and permissions are available on team plans.

Setting up roles has three steps:

1. Define roles for the kinds of people in your team — for example Admin and Team member, or something more specific to your work.
2. Assign permissions to each role — what its members can see, create, edit and manage.
3. Assign each person a role. Non-admin users are locked down to exactly what their role allows.

Typical splits: admins create, edit and reorder tags while team members apply existing ones; tasks are fully visible to admins but hidden entirely for roles that don’t use them; and imports, duplicates and structural tools stay admin-only.

A team member in a restricted role sees a simpler app focused on the map and their pins. Sections their role doesn’t include — such as tasks or organisation areas — are hidden rather than greyed out, so there is less to navigate and nothing to misconfigure.

If someone on your team asks why a feature they’ve seen elsewhere is missing from their app, that is roles working as intended. If they do need it, an admin can adjust the permissions on their role at any time.