Workspaces: manage multiple projects as one team

Workspaces group related projects together so team members share access, visibility, and context across everything they are working on.

Browse all docs

What is a workspace?

A workspace is a container for multiple projects. When you add team members to a workspace, they automatically gain access to all projects within it. This simplifies onboarding, ensures consistent visibility, and avoids the need to manage invitations one project at a time.

  • Group related projects — e.g., all projects for a product line, department, or client
  • Add members once to the workspace instead of inviting them to each project individually
  • Workspace members appear in project member lists, allocation charts, and assignment menus
  • Switch between workspace projects quickly from the project navigation

When to use workspaces

Not every team needs workspaces. They are most valuable when your organization has multiple related projects with overlapping team members.

  • A product team with separate projects for Web App, Mobile App, and API — all share the same engineering and design members
  • An agency managing multiple client projects with a shared pool of developers and designers
  • A department with a 'Platform' project and several feature-specific projects that share infrastructure engineers
  • A cross-functional team that needs visibility into each other's boards without individual invitations

Example: A startup has three projects: Core Product, Admin Dashboard, and Marketing Site. All five engineers work across all three. Instead of managing 15 individual invitations, the team lead creates a workspace, adds the five engineers, and links all three projects. New hires only need one workspace invitation.

Creating a workspace

  • Navigate to the workspace section and create a new workspace with a name and description
  • Add existing projects to the workspace — projects can belong to one workspace
  • Invite members to the workspace with their role (member, admin, or read-only)
  • Workspace members automatically see all linked projects in their project list

Workspace membership vs. project membership

Team members can be added to projects directly or through a workspace. Both paths give access to the project, but workspace membership has unique characteristics:

  • Workspace members appear in all linked projects — they can be assigned to cards and tasks
  • Workspace members show up in the sprint allocation chart and project member list
  • Workspace-derived followers see an Unfollow button only if they have directly followed the project
  • Direct project membership and workspace membership can coexist
  • Removing a member from the workspace removes their access to all linked projects (unless they also have direct membership)

Best practices

  • Use workspaces for organizational grouping, not for permissions — control access with project roles
  • Keep workspace membership updated: remove team members who have moved to other teams
  • Name workspaces clearly: 'Frontend Team' or 'Client X Projects' rather than generic names
  • Review workspace projects periodically and archive completed projects to keep the navigation clean

Common questions

Can a project belong to multiple workspaces?+
A project is linked to one workspace at a time. If you need cross-workspace visibility, add members directly to the project.
Do workspace features require a paid plan?+
Yes. Workspaces are available on paid plans. The free plan supports individual project memberships.
Can I convert existing projects into a workspace?+
Yes. Create a workspace and add your existing projects to it. Existing project memberships are preserved alongside workspace membership.
What happens when I remove a project from a workspace?+
Workspace members lose access to that project unless they also have direct project membership. The project and all its data remain intact.

Simplify team management across projects

Workspaces make it easy to manage access, visibility, and collaboration when your team works on more than one project.

Browse all docs