Workspaces & Organizations

Every piece of architectural knowledge 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". 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:

The org → workspace → board hierarchy

The Root Board

When you create a workspace, you automatically get a Root 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 Root Board, but you can customize it like any other board.

Think of workspaces as project rooms — each with its own walls, whiteboards, and reference material. The Root Board is the big whiteboard by the door: everyone passes it, and it gives you the lay of the land before you head into a specific room.

Folders

Folders organize boards within a workspace. They nest — folders inside folders — and come in four flavors depending on what they hold. Create them from the sidebar, then drag boards in.

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.

Verify your workspace setup

• Organization created with a unique handle
• At least one workspace created under the org
• Root Board is visible in the workspace
• Workspace category is set correctly
• Folders created for logical board grouping
• Team members invited to the organization

What's next