Collaboration depth
How this is scored
How much real multi-person project work the tool carries: shared planning, assignments, dependencies, workload, comments, guest access.
0 — A personal task list; a second user has no defined place in it.
3 — Tasks can be shared and assigned, but planning stays per-person — no shared timeline, workload or dependency view.
5 — Solid shared projects with assignments, comments and at least one team-level planning view; gaps appear in cross-project or capacity planning.
8 — Team-level planning is first-class: cross-project views, workload/capacity, dependencies, guest or client access with sane permissions.
10 — Handles the full span from two freelancers to a structured department in one model — planning, capacity, permissions and client involvement all without workarounds.
The UX Purist
Team-level planning is documented as the core of the product: a company-wide timeline spanning every workspace in the GitHub organization, cross-level dependencies drawn as directional lines, capacity planning and sprint automation on the enterprise tier, plus custom roles, audit logs and multi-project workspaces. Assignments, story points, bulk multi-select edits and saved shareable views are all in the board docs, and Slack teammates can comment into issues without a Zenhub account. We found no public information on a guest or client seat with its own permissions inside a workspace, which is what separates this from the very top. 1 2 3 4 7