Project members and permissions
You add the people and minions you work with to a project as members. Each member gets a permission, which decides what they can change in that project.
Permissions are there to protect things that shouldn’t change without you knowing, such as the project’s description (its context) and who is on the project.
The three permissions
Section titled “The three permissions”| Permission | What it allows |
|---|---|
| Admin | Add and remove members, change permissions, archive or delete the project. Can also do everything an editor can. Only people can be admins |
| Editor | Edit the context, variables and project settings, and place and run workflows in the project. Can also do everything a member can |
| Member | Write and move tickets on the board, add memories, approve workflow reviews. Minions run workflow steps |
People who aren’t members of a project can still look at it if they’re in the same workspace. A notice at the top says they can only view it, and the edit buttons don’t appear.
Who is an admin from the start
Section titled “Who is an admin from the start”- Whoever created the project
- The workspace’s owners and admins (they are admins of every project, even ones they aren’t members of)
A project never ends up without an admin. Even if its creator leaves, the workspace’s owners and admins can still manage it.
Add a member
Section titled “Add a member”Only admins can add members.
- Open the project’s Members tab
- Under Add Member, choose the person or minion to add
- Choose a Permission. If you’re not sure, pick Member; you can change it later
- Press Add
You can change a permission at any time with the choice at the right of each row. To take someone off the project, press Remove. Tickets they were assigned keep showing them as the assignee.
Permissions for minions
Section titled “Permissions for minions”A minion can be an Editor or a Member, but not an admin. That way a minion can never change who is on the project or what they’re allowed to do.
- Member — does the work on tickets and workflow steps. This is usually enough
- Editor — can also rewrite the context and variables, and create and run workflows. Choose it when you want a minion to run the project’s process too
About the old “roles”
Section titled “About the old “roles””Members used to be added with a role: “PM”, “Engineer” or “Accountant”. Roles have been retired and are no longer chosen. What someone can do is set by their permission.
Members who were added earlier may still show a small label such as “DAG: PM” in the list. It only decides which minion runs the steps of older workflows, and will go away.
If something doesn’t work
Section titled “If something doesn’t work”- There’s no Edit button — you don’t have the permission that action needs. Ask a project admin to raise it
- There’s no form for adding members — only admins can add members
- A notice at the top says you can only view the project — you aren’t a member of it. Ask an admin to add you