Inviting your team and setting access levels
Invitation links, six-character join codes, the three member roles, invite expiry, and restricting a member to specific views.
Two ways to invite
You can share an invitation link, or a six-character join code that someone enters at the join page. Both carry the same information: which project, which role, when the invitation expires, and how many times it can be used.
Someone who is signed out can still accept. The code is remembered through sign-up and redeemed once their account exists, so you do not have to coordinate the order.
The three roles
Editor gives full task management. Contributor can update progress and effort but not restructure the project. Viewer is read-only.
These are enforced in the database through row-level security, not just hidden in the interface. A Contributor cannot change a task name by any route, including a direct API call.
The Project Owner is separate from these three. It is the person responsible for running the project: whoever created it, until it is handed on. The current Project Owner, or an owner or admin of the organization, can make anyone else in the organization the Project Owner under Project settings → Access → Change owner: including a guest.
Who a project belongs to
A project belongs to its organization, not to its Project Owner. The organization’s owners and admins can always find it under Organization → Projects, manage who has access, change the Project Owner, and move it to the trash or restore it, even when it is Private and they are not on it. To work inside it they add themselves, which the project’s activity records.
Private means only the people on the project, plus the organization’s owners and admins. It never means the Project Owner alone. Whoever makes a project Private while they reach it only through the workspace stays on it as a member.
A guest who is the Project Owner runs the project and manages its people, but cannot delete it or take it out of the organization. Before someone who owns projects is removed from the organization, a new Project Owner is chosen for each of them.
Expiry
Invitations expire after 3, 7, or 14 days, with 7 as the default. There is deliberately no never-expires option: an invitation link that works forever is a link that ends up in a document somebody forwards two years later.
Expired invitations are shown as expired in the directory rather than disappearing, so you can see what was sent.
Restricting a member to specific views
A member can be restricted to a named set of views. A restricted member sees only those views in the sidebar, and reaching one of the others by typing its URL directly gets them a blocked screen rather than the content.
Their own private views always remain visible to them regardless of the restriction.
Seats
Starter supports 2 seats per project. Basic, Standard, and Professional have no per-project seat cap.
On a Team plan, seats belong to the organization. Every paid member uses one seat, however many workspaces they work in; guests never use one. Adding seats is charged straight away, prorated; removing seats takes effect at your next renewal, and never below the seats in use or the Team minimum of 3.