Workspaces, guests & plans

Your dashboard groups projects by how you're connected to them, so someone else's work never reads as your own:

• Your workspace — projects in a workspace you own. Your account, your seats, your billing.
• Invited workspace — you're a member of someone else's workspace. You see its projects, but it's their account and their seats.
• Guest project — you were invited to one project only. You see that project and nothing else of that workspace.

On any project a person is a lead, editor, or viewer. The lead (PM) manages that project's members and its visibility — no need to route every change through the workspace owner. Public projects are visible to the whole workspace (Slack-channel style); private ones only to people explicitly added.

• Lead — manages the project's membership and visibility, edits the timeline, and can be assigned tasks. The workspace owner is always the lead on any project they own.
• Editor — edits the timeline (tasks, dates, dependencies, status, comments) and can be assigned tasks. Cannot change the project's membership or visibility.
• Viewer — read-only. Can see the project, follow links, and be @-mentioned in comments, but cannot edit anything or be assigned a task. Use for stakeholders who need visibility without ownership.

Yes — if their project role is lead or editor. A guest is just a project member whose access is scoped to that one project, so the same role rules apply. The assignee picker shows guests with a small amber dot on their avatar so you can tell contractors from teammates at a glance. Viewer-role guests (or viewer-role workspace members on a specific project) don't appear in the assignee dropdown — assigning someone who can't edit the task wouldn't be meaningful — but they still receive @-mention notifications and show up everywhere else in the project.

Every project member (workspace + guest) gets a row in the Workload view, with their assigned tasks. The capacity reference line counts anyone who can act on a task — leads and editors, workspace or guest — but not viewers. So a project with one workspace owner plus five guest editors all working flat out shows capacity = 6, matching reality. If a viewer happens to be assigned a task (legacy assignment from before this rule), their row still renders so you can see the assignment and unassign them.

Editor seats and guest seats are separate pools. Workspace members count against your editor seat count — Team includes 3, +$5 per extra seat. Guests scale with your editor seats: 5 guests per editor seat. So a 3-seat Team workspace allows 15 unique guests across all projects combined; if the same person is a guest on three of your projects, they still count as 1.

Guests are tightly scoped to the projects they're invited to. Inside that project they can edit tasks (if editor role), be @-mentioned, capture baselines, and receive email or Slack notifications. They cannot:

• See any other project in your workspace — even ones marked Public. Public means "visible to workspace members," and a guest isn't one.
• Be a project lead — guests are capped at editor or viewer, so they can't invite other guests or manage the project's roster.
• Edit the project's status set (the colored columns). That's a settings-level change, owner / lead only — editors drag tasks across statuses but can't rename or recolor them.
• Save workspace templates, or follow a cross-project phase reference into a project they don't have access to (the linked phase still renders in their project; clicking through is what's blocked).
• Access workspace settings, the member roster, or the workspace's Slack roster. The /workspace page is owner-only.

• Basic — free, solo: a few projects, no invites, no cross-project references.
• Team — $29/month, 3 editor seats included, +$5 per extra seat. Unlimited projects + tasks, cross-project references, template authoring, and 5 guests per editor seat. New workspaces start here free during beta.
• Academic — Team at ~⅓ off ($19/month, +$3 per extra seat) for verified university research labs and academic teams. Same feature set as Team.
• Enterprise — no numeric ceilings, plus organization features.