Value Proposition Statement
Ensure Workspaces in Camunda Hub represent intentional collaboration boundaries by introducing a governed creation and access model.
This:
- Prevents accidental private or siloed spaces
- Reduces workspace sprawl
- Enables enterprise-ready onboarding and governance
- Keeps modelling accessible without compromising structure
User Problem
With the introduction of Workspaces as top-level collaboration boundaries, allowing any user to create them would:
- Enable accidental private or siloed collaboration spaces
- Fragment teams and ownership
- Undermine governance and scalability for enterprise customers
The current Web Modeler behaviour (where any user can create a project) does not scale once projects are transformed into Workspaces.
At the same time, removing unrestricted creation means users no longer get implicit private projects — which must be addressed intentionally.
Release Notes
(To be defined)
User Stories
Workspace Creation & Organisation Admins
US-1 — As an Org Owner or Org Admin, I want to create and manage workspaces, so that collaboration boundaries are intentional, owned, and governed.
Capabilities:
- Create new workspaces
- Assign users to workspaces
- Manage workspace roles
- Rename or delete workspaces
Regular Users / Contributors
US-2 — As a regular user (non-admin), I want access only to workspaces I am assigned to, so that I can collaborate on projects without accidentally creating new collaboration boundaries.
Capabilities:
- See and access assigned workspaces according to workspace roles
- Access projects inside those workspaces
- Cannot create, rename, or delete workspaces
- Cannot manage workspace membership
Workspace-Level Administration
US-3 — As a Workspace Admin, I want to manage membership for my workspace, so that I can control who can access and collaborate on the projects within it.
Capabilities:
- Add users to the workspace
- Remove users from the workspace
- View all workspace members and their roles
- Assign or change workspace-level roles
SaaS Trial Users
US-5 — As a SaaS trial user, I want to create and manage workspaces, so that I can explore the product fully without requiring Camunda support.
Capabilities:
- Automatically assigned Org Admin role in the trial organisation
- Can create, rename, and delete workspaces
- Can assign users
Workspace Access State
US-6 — As a user without workspace access, I want to see a clear explanation of my state, so that I understand why I cannot create or see workspaces and what steps to take next.
Capabilities:
- Clear “no access” or empty-state messaging
- Guidance on how to request access
Target State
Workspace Creation
- Only Org Owners / Org Admins can create workspaces
- Regular users cannot create workspaces by default
- No workspace is created implicitly through user actions
User Access
- Every user is either:
- A member of one or more workspaces, or
- In a clearly defined “no workspace access” state
- The system does not require a mandatory default workspace
SaaS Trial Behaviour
In SaaS trial organisations:
- The trial user is assigned the Org Admin role by default
- Trial users can create and manage workspaces
This ensures:
- Zero onboarding friction
- Full product exploration
- Consistency with the governed workspace model