Workspaces
A workspace is a container of written pages — specs, runbooks, decisions, and notes — scoped to you, a team, or a project so the context lives next to the work.
Release plan — v2
Engineering · shared doc
#Owner: @lena · target: 2026-06-25
Staging URL is ready for review — ping when green.
Pages are written block by block. Each block saves on its own, and the page shows a live save state so you always know whether your edit landed.
How a workspace is built
- Workspace: The container. Give it a name, a description, an icon, and a colour so it is recognisable in the list.
- Pages: Each workspace holds pages, and each page is made of blocks — text, headings, lists, and embeds.
- Links: Link a page to the tasks and projects it describes, so a spec and its board point at each other.
Visibility
You pick the scope when you create a workspace. It determines who can find it before any individual roles are granted.
Personal
Only you can open it, plus anyone you explicitly grant a role to. The default for a new workspace.
Team
Scoped to a team you belong to. Use it for handbooks, runbooks, and decisions the whole team needs.
Project
Attached to a specific project, so the spec sits next to the board that delivers it.
Roles inside a workspace
On top of visibility, the workspace owner can grant a specific person a role:
- Owner: Full control, including granting and revoking other people's access and deleting the workspace. The creator is the owner.
- Editor: Can create and edit pages, but cannot manage access.
- Viewer: Read-only.
Only the owner manages access
History and AI drafting
Change history
Every workspace keeps a history of what changed and who changed it, so you can see how a decision document got to its current wording.
AI-drafted pages
Generate a page from a prompt or a template — the result is a normal page you edit by hand, and it is marked as AI-generated so reviewers know where it came from.
When to create a new workspace
Do create one if:
- • A body of written context has its own audience — an on-call runbook, an architecture decision log, an onboarding handbook.
- • A project needs a spec that outlives any single task.
- • You want a private scratch space that is not visible to your team.
Do not create one if:
- • You want to separate people or billing — that is a team.
- • You want to separate deliverables and boards — that is a project.
- • You just need one note attached to one task — write it in the task description or a comment.
Deleting a workspace is permanent
Plan requirement