Workspace Canvas basics
What Workspace Canvas is, the building blocks that make it up, and what makes it different from every other tool your team already has open.
Workspace Canvas is a single surface for docs, databases, teamspaces, and AI. Instead of juggling a wiki here, a task tracker there, and a set of AI tools in a fourth tab, everything you write, plan, and automate lives on the same connected canvas — and every piece can talk to every other.
This article covers the four building blocks you'll use every day, how they combine, and the mental model that makes advanced setups feel obvious rather than intimidating.
The four building blocks
Everything in Workspace Canvas is built out of just four primitives. Learn these and the rest of the product stops feeling like a menu of features and starts feeling like a language you already speak.
Pages
A page is a blank canvas. It can hold plain text like a doc, structured content like a wiki article, or embedded views of a database. Pages nest inside each other, so you can build anything from a single meeting note to a hundred-page product handbook without ever leaving the same surface.
Blocks
Every element inside a page is a block: a paragraph, a heading, a to-do, an image, a table, an embed, a database view. Blocks can be dragged, nested, and converted into each other. Type / anywhere on a page to insert one.
Databases
A database is a page whose content is a structured collection of items — tasks, contacts, meetings, bugs, anything you'd otherwise track in a spreadsheet. The same database can be shown as a table, board, calendar, timeline, or gallery just by switching views.
Teamspaces
A teamspace is a shared home for a group inside your workspace — a team, a squad, a project. It has its own sidebar section, its own permissions, and its own set of pages and databases. Use teamspaces to keep engineering, marketing, and ops from stepping on each other's toes while still living in one workspace.
What makes it different
Three things separate Workspace Canvas from a stack of single-purpose apps stitched together with integrations:
- Everything shares the same content model, so a task in a database is the same object whether you look at it on a board, in a doc, or from an AI query.
- Workspace AI has native access to your content and can search across every page and database you can see (and nothing you can't).
- Permissions cascade sensibly from workspace to teamspace to page, so a new hire lands somewhere useful on day one without an admin building them a bespoke setup.
A worked example
Say you run a weekly product review. In most tools that's a Google Doc for the agenda, a Jira board for the tickets, a Slack thread for the follow-ups, and a Loom for the recording — four places, none of them talking to each other. In Workspace Canvas it's one page that embeds a filtered view of your projects database, a linked view of blockers, an AI-generated summary at the top, and a to-do list at the bottom. Next week, duplicate the page and everything refreshes.
Everything you can reach from the left sidebar — how it's organised, how to move around, and the shortcuts that make it feel instant.
