Last updated August 12, 2026
Workspaces & Organizations
Two containers hold everything you build: organizations and workspaces.
The hierarchy
An organization is the top-level container, usually your company. Its handle forms the URL. Org-level settings include members, roles, connectors, archetypes, and insight skills.
A workspace is one architectural domain, such as "Payments Platform", "Mobile Backend", or "Cloud Migration". Each workspace has its own boards, source catalog, and folders.
Boards live in folders inside a workspace, and folders nest as deep as you want.
If you are choosing between a workspace and a folder, ask whether the boards should share sources and audience. A folder organizes boards inside one domain. A workspace creates a separate domain.
Creating a workspace
Create Workspace opens a short dialog:
- Workspace Name: what people call it.
- Code: the short handle that appears in the URL of every board inside it. Pick something you are comfortable typing.
- Icon and Description: how it appears in the switcher, and what it is for.
- Default: makes this the workspace you land in when you sign in.
Finding your boards
The org-wide boards page is where boards are created, renamed, disabled, deleted, and found again. Deleting & Undoing explains what can be restored.
A folder tree runs down the side, and a searchable grid of board cards fills the rest. Filters narrow by owner, org sharing, published state, privacy, and disabled state. Sort by recent update or alphabetically.
Manage folders from the folder tree's context menu: add a folder, add a board inside it, rename, or remove. Drag boards in as the workspace grows. If nobody uses a folder, collapse its contents into the parent.
Who's in it
Settings → Access lists everyone in the organization and their role: Owner, Admin, Contributor, or Read only.
Role changes do not happen on this page. It is read-only in the portal. The Manage team in Portal button takes you to the place where invites and role changes are made.
Sharing one board
Org membership decides general permissions. A board's Share dialog decides access to that board.
General Access grants access by role. Admins, contributors, and read-only members can each have no access, view, or edit on this board. Specific Access invites named people individually as a viewer, editor, or owner.
The two layers combine, and publishing is a third decision. Permissions & Access explains all three.
The Root Board's place
A workspace's board tree has a Root Board at its top, and everything else you create sits below it. Boards explains what the Root Board is, where it comes from, and how its opening view changes once app boards appear beneath it.
Settings that live at org level
Archetypes, field templates, context tags, insight skills, and connectors are configured once for the whole organization rather than per workspace. Organization Settings covers the list.