Account
Teams and folders
Diagrams scattered across personal accounts disappear when their owner does, and inviting everyone to every project one by one does not scale past two people. A team is a shared workspace: its projects belong to the team, and members work in them without per-project invitations. The Team plan is flat-priced for up to 5 seats, one subscription covers everyone, and folders organize the workspace, optionally on a need-to-know basis.
How it works
- 1Set up the team: name the workspace and invite your people by email. Creating it and inviting are free; billing starts when you activate.
- 2Activate the plan. One subscription, held by the owner, covers up to 5 seats; no member needs their own.
- 3Switch to the team workspace from the sidebar. Its projects are open to every member, with no per-project invitations.
- 4Restrict a folder when its projects are need-to-know; only people added to the folder see inside.
The team workspace
- You switch between your personal workspace and the team workspace from the switcher at the top of the sidebar. Each shows its own projects and folders.
- One subscription, held by the team owner, covers every member: being a member of an actively billed team is what grants the Team plan. Members do not need their own subscription.
- 5 seats, enforced. Members plus pending invitations must fit in 5. When all seats are taken, revoke a pending invitation or remove a member to free one.
- Invitations expire after 14 days if not accepted.
Team roles
| Role | Can do |
|---|---|
| Owner | Billing, everything else, cannot be demoted. |
| Admin | Manage members, invitations, projects, and folder access. |
| Member | Work in the workspace: create and edit its projects. |
These are workspace roles. Per-project sharing with outside collaborators still works as described in Sharing and permissions.
Folders
Folders live in the sidebar under Home and hold projects. Personal folders are purely organizational. Team folders have one extra property: they can be restricted.
Restricted folders are need-to-know
In a restricted folder, being a team member is no longer enough to see the projects inside: only people added to the folder can. Org owners and admins always retain access, as do a project's own owner and anyone explicitly invited to a specific project. Restriction narrows the team-wide grant, nothing else.
Use a restricted folder for the diagrams that should not be workspace-wide: an acquisition's infrastructure, a security review, a client whose architecture is under NDA.