.png)
Common scenarios
Roles make sense fastest through examples. Here's which role to reach for in common situations.
"Someone should do the work, but not run the company"
Use Member. They can create and update tasks, documents, and comments on the projects they're added to — but can't delete projects or invite people. This is the right role for most of your team.
"An external contractor needs to see progress, not change things"
Use Contractor (or Viewer). Both are read-only: they can see the work they're given access to, but can't edit it. Add them only to the specific workspaces and projects they need.
"A client wants visibility without touching anything"
Use Viewer, added only to the relevant workspace. They get a clean, look-but-don't-touch window into progress — and the Associate stays read-only for them too.
"Our finance person handles billing but shouldn't see projects"
Use Billing. It's walled off from all project work, tasks, documents, and AI — purely for the account and finance side.
"A lead needs to manage projects across the whole company"
Use Manager (or Admin). They have company-wide authority — they can act on any project without being added to it, create and complete projects, and invite people. Owner is the top of this tier and anchors billing and ownership.
"A teammate changed teams and shouldn't see their old projects"
Just remove them from the workspace or project. Because membership is the source of truth, access updates immediately — there's nothing stale to clean up.
Start narrow, widen later
When in doubt, give the lower access. It's quick to add someone to another workspace or bump their role up — and much safer than handing out broad access and hoping to claw it back.
Next
Last updated: 2026-05-31