Docs
Home

Canvas databases overview

Workspace Canvas databases with typed records and reusable views.

A Canvas database is a workspace-root structured table of records. Open it from the Canvas section at the bottom of the sidebar, below Direct messages, or via a mention, search, or a direct link. Each row is a record with typed cells, and the same data can be saved through multiple views — table, board, list, gallery, or feed — without copying anything.

When to use a database

Use a database for anything you'd otherwise track in a spreadsheet where the rows are things you'll want to talk about, assign, filter, or cross-link with the rest of the workspace:

  • Projects, tasks, OKRs, sprints
  • Customer accounts, leads, support tickets
  • Bug reports, feature requests
  • Content pipelines, editorial calendars
  • Inventory, expenses, hiring pipelines

If your data is mostly free-form prose, you want a document instead.

What's covered in this section

  • Creating a database — column types, rows, filters and sorts, page comments, version history and revert, real-time collaboration, and what agents can do with the data.
  • Database views — the five view kinds (table, board, list, gallery, feed) and how each saves its own filter, sort, visible columns, and column widths.

Mentioning a database in a message

You can #mention any canvas database from a message or a document. The mention turns into a chip anyone with access can click to jump to the database, with a Circle Stack icon and a "Database" badge so it's distinguishable from a document mention. The chip's label stays in sync as the database is renamed.

Comments

Every database has a page comments stream — the same page-level discussion a canvas document has, sitting just below the title and above the views. Drop a comment about the database as a whole, @mention a teammate, react, resolve, or archive — and cross-post it into a space to start the conversation in the channel. See Comments for the full flow.

Permissions

Databases have Canvas access independent from Spaces. An audience can be the workspace, a person, a Group, or readers of a Space. Viewers can read, editors can edit/comment, and managers can change access or archive the Canvas. There are no per-row permissions.