Canvas databases overview

A canvas database is a structured table of records that lives inside a space, next to the channel and any document canvases. 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, comments anchored on rows or cells, 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 everyone in the space 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#

You can drop a comment thread on the database as a whole, on a single row, on a single cell, or on a specific substring inside a rich-text cell. Cross-post the root comment into a space to start a conversation in the channel while keeping the anchor on the data. See Comments for the full flow.

Permissions#

Databases inherit access from the space they live in. Anyone who can read the space can read and edit its databases. There are no per-database or per-row permissions to learn.