Last updated April 21, 2026
Workspaces & Organizations
Every piece of architectural knowledge in ContextDX lives inside a clear hierarchy: Organization → Workspace → Boards. This structure keeps your teams organized and your architecture isolated where it needs to be.
Organizations
An organization is your top-level container — typically your company or team. It has a unique handle that forms the URL for your organization's space. Every user, workspace, and resource belongs to exactly one organization.
Organizations control:
- Team membership and roles
- Integration credentials (GitHub OAuth apps, Confluence tokens, etc.)
- Shared config like element archetypes and insight skills
Workspaces
A workspace represents a distinct architectural domain — think "Payments Platform", "Mobile App Backend", or "Cloud Migration 2025". Each workspace gets its own:
- Boards — visual canvases for different architectural views
- Sources — connected data feeds from repos, docs, and infrastructure
- System catalogue — the registry of known systems and components
- Folders — organize boards into logical groups
Every workspace is scoped to a single organization. You can create as many workspaces as you need — one per product, per migration, per team — and they stay isolated from each other.
Workspace categories
When you create a workspace, you pick a category that describes the kind of system it represents:
| Category | Description |
|---|---|
| Self-Hosted | On-premise or self-hosted infrastructure |
Best for teams mapping internal data centres, private cloud deployments, or air-gapped environments. Sources like Terraform configs and GitHub repos shine here.
The org → workspace → board hierarchy
Rendering diagram...
The Master Board
When you create a workspace, ContextDX automatically generates a Master Board — the primary dashboard that aggregates everything in the workspace into a single overview. It's the anchor for your workspace, the starting point where everything rolls up.
You can't delete the Master Board, but you can customize it like any other board.
The Master Board is like the lobby of a building — everyone passes through it, and it gives you the lay of the land before you dive into specific rooms.
Folders
Folders help you organize boards within a workspace. They support nesting — put folders inside folders — and come in several flavors depending on what they hold:
Folder flavors in detail
| Folder | Purpose | Typical contents |
|---|---|---|
| Boards | Groups boards in the main listing | System diagrams, context maps, sequence flows |
| Artifacts | Groups architectural artifacts | ADRs, tech radar entries, capability maps |
| System | System-level grouping | Auto-generated folders for system catalogue items |
| Automation | Groups automation-related boards | Insight results, generated reports, CI/CD views |
Nest folders as deep as you need — each one can live inside another, giving you as much hierarchy as your architecture deserves.
Think of workspaces like project rooms — each one has its own walls, whiteboards, and reference materials. The Master Board is the big whiteboard by the door that shows the full picture.
Verify your workspace setup
- Organization created with a unique handle
- At least one workspace created under the org
- Master Board is visible in the workspace
- Workspace category is set correctly
- Folders created for logical board grouping
- Team members invited to the organization