The Anatomy of a Workspace

A workspace is a permission and visibility boundary within a project. It allows different teams or user groups to see tailored views of the same project data.

  1. Core Properties
  2. What Workspaces Control
    1. 1. Dimension Visibility
    2. 2. Default Filters
    3. 3. Board Permissions
  3. Members
  4. Use Cases
  5. Key Relationships

anatomy-workspace.svg


Core Properties

Property Description
Name Human-readable workspace name
Code URL-friendly identifier
Description Optional explanation of the workspace's purpose
Members Users who belong to this workspace

What Workspaces Control

1. Dimension Visibility

Choose which dimensions workspace members can see:

Mode Effect
Show all All project dimensions are visible
Whitelist Only specified dimensions are shown
Blacklist All dimensions except specified ones are shown

Example: Marketing workspace only sees Status, Priority, and Due Date — not Story Points or Technical Debt.


2. Default Filters

Pre-filter cards for the workspace:

Engineering Workspace:
  └── Default filter: Team = "Engineering"

Marketing Workspace:
  └── Default filter: Team = "Marketing"

Members see only relevant cards without manual filtering.


3. Board Permissions

Each board defines access levels per workspace:

Workspace Board: Backlog Board: Roadmap Board: Reports
Engineering Manager Contributor Viewer
Marketing Viewer Contributor Manager
Support Viewer Viewer

Permission levels:

  • Viewer — Read-only access
  • Contributor — Can edit cards
  • Manager — Can change board settings

Members

Each workspace has its own member list:

Engineering Workspace
├── 👤 Alice (alice@company.com)
├── 👤 Bob (bob@company.com)
└── 👤 Charlie (charlie@company.com)

Users access the project through their workspace, seeing only what's configured for them.


Use Cases

Scenario How Workspaces Help
Multi-team project Each team sees their own cards and relevant dimensions
Client access External users get read-only view without internal details
Department views Finance sees budgets, Engineering sees story points
Role-based access Managers can edit, contributors can view

Key Relationships

Project
├── Dimensions (shared across all workspaces)
├── Cards (shared, filtered by workspace settings)
├── Boards (each defines per-workspace permissions)
└── Workspaces
    ├── Members (who can access)
    ├── Dimension visibility (what they see)
    ├── Default filters (which cards they see)
    └── Per-board permissions (what they can do)
Go back

Article status changed.

Article status changed.

Article status changed.