Skip to main content
A workspace owns canvases, blocks, assets, and API keys. Sign-up creates a personal workspace. Existing membership rows continue to control access to private resources. The workspace owner can author blocks and canvases through the web UI. Workspace-scoped MCP keys act on that workspace’s resources; key creation requires an admin membership. The app remembers the previously selected workspace. Existing workspace cookies remain readable; when no valid cookie is available, the latest persisted viewer context is used before the first-membership fallback. See MCP limits for resource caps and Canvas and blocks for public sharing.