Look up what a permission lets a person do

Every permission an organization role can hold, in words.

In short

A role is made of permissions. This list says in words what each permission lets a person do, and which are dangerous. Use it when you build a custom role or wonder why someone can or cannot do something.

Before you start

• Who: seeing the roles that hold each permission needs "See roles". Anyone can read this list.
• Plan: Organizations is part of every plan, Free included. Your plan sets how many members and teams an organization may hold (Plan & usage shows them).
• First: nothing.

Steps

1. Open the organization's "Access" › "Roles" to see which permissions each role holds.
2. Find the permission in the table below.
3. To give it, give the person a role that holds it, or create one. See /help/organizations/custom-roles.

What the permissions mean

Good to know

• Each module permission is a ceiling: a person holds at most that on any one board, project or notebook, and the thing decides who it is open to. See /help/organizations/sharing.
• A few permissions, such as See members, See reports, Use monitoring, Use Chat and See the Planner team view, are reserved. They sit in the built-in roles but nothing asks for them yet.
• The role newcomers get can never carry a dangerous permission.

If something goes wrong

• Someone has the permission but still cannot open a thing: the thing is not open to them. Share it, or file it under their team.
• You cannot add a permission to a role: you do not hold it yourself.

Related

• /help/organizations/roles-and-permissions
• /help/organizations/custom-roles