User guide
Organizations and people
The organization is the boundary of everything: projects, work items, workflow settings, channels and API tokens all live inside exactly one of them, and every URL carries its slug. This page covers how to build that structure - and how access flows through it.
Organizations and sub-organizations
Anyone can create a root organization: Account → Organizations → Create
Organization. The creator becomes its Owner, and the URL slug you
pick (/o/acme/…) cannot be changed later. Large teams nest: an admin of an
organization can create sub-organizations under it - a department, a product
line, a client team - each with its own members, projects and settings. The
Chart page of any organization draws the whole tree with its people, and
every member can open it, not just admins.
Access flows down, never up or sideways
A membership on an organization grants access to that organization and everything nested
under it. It never leaks up to a parent or sideways to a sibling: someone
invited only to acme / product-b cannot see product-a's projects.
Admins work the same way - an admin of the parent manages every descendant, but an admin of
the child does not manage the parent.
The roles
| Role | What it means |
|---|---|
| Owner | Whoever created the organization. Full control of the subtree; the owner's membership cannot be removed like other members'. |
| Admin | Manages members, settings, workflow, automation and sub-organizations for the organization and every descendant. |
| Member | The everyday working role: read and edit work across the subtree, join channels, be assigned items. |
| Viewer | Read-only across the subtree - useful for stakeholders who should watch but not touch. |
| Guest | A legacy read-only role kept for older memberships; invite Viewers instead. |
| External collaborator | An identity membership only: it proves who they are and puts them in the audit trail, but their data access comes only from explicit project grants. See below. |
Inviting someone by email
On the organization's Members page, Invite User takes an email address, a role (Viewer, Member, External collaborator or Admin) and an optional job title. If the address already belongs to an account, the invitation attaches to it immediately and the person gets a link to accept; if not, a pending membership is held for that address - registering with it claims the invitation automatically, or they can accept or decline later from the Review invitations banner on their dashboard. Until they accept, nothing is active, and the same address cannot be invited twice.
Assigning an existing person
Assign User adds someone who already has a backendup account directly - pick them by name, choose the role, done. There is no acceptance step: use it for colleagues moving between teams, where the invitation dance is ceremony.
Allowed email domains
An organization's Settings page can restrict membership to company addresses: one domain per line, blank means any address is allowed. The list is enforced where people join - inviting, assigning, and moving a member into a team all refuse addresses outside it ("This organization only allows members with email addresses at: acme.com.") - and it also protects the back door: a member cannot change their own email to a domain that would violate a rule at one of their organizations.
Quiet-hours default
Managers and owners can set a default quiet window (weekday and weekend, like the personal setting) in the same Settings page. It is a default, never an enforcement: it holds only for members who never chose their own windows - and any personal choice, including "never quiet", always wins and survives later admin changes. Child organizations inherit the nearest ancestor's default until they set their own, which lets one team diverge without touching the parent; clearing a branch's own row returns it to inheriting. Windows are read in each member's own timezone, and quieting still only ever holds delivery: the messages arrive, count unread, and the merged mail lands in the next digest.
External collaborators: access by project, not by org
Consultants and vendors get the External collaborator role plus one grant per project, chosen from the inviting organization's own subtree (never a parent's or a sibling's projects). Each grant is Viewer - can read work and discussions - or Collaborator - can also comment and update normal work. Grants hang off the membership, not the person: when the membership ends, every related grant stops working at once while its audit history survives. Admins can also grant, change or revoke project access from the project's own Collaborators page.
Moving people, teams and work
Restructuring is supported rather than tolerated. A member can be reassigned to another team in the chart; a sub-organization can be re-parented under a different team, with an option to rewrite its URL slugs to the new company prefix. Work that changes organization - moving a project, or a work item to another project - is preflighted against the target's workflow: statuses are remapped by their shared category (a source "In Progress" lands on the target's active in-progress status), and the move is blocked with a precise reason if the target has no compatible status or if a relation would end up pointing across organizations. When you are an admin of the target, the error even links to the workflow settings where the missing status would be added.
Removing a member
Remove on the members page ends a membership; their work-item assignments, comments and history stay as the record of what happened. The organization's Owner cannot be removed this way.