Databases make recurring work structured, filterable, and reviewable. Typical examples include content calendars, campaign trackers, research libraries, CRM-style lists, competitor trackers, and task boards.
Create a database
- In Workspace, choose the add control and select Database.
- Choose whether to create a full-page database or insert one inside a page.
- Name the database for the operating job, not the tool - for example,
Q3 Content Pipelinerather thanContent table. - Create the first properties and views before importing a large amount of data.
Build a useful schema
Every database has rows, which open as full pages, plus properties that describe each row.
Start small. For a content pipeline, use:
| Property | Recommended type | Example |
|---|---|---|
| Name | Title | AEO: stop optimizing only for rankings |
| Status | Status or select | Idea, Draft, In review, Scheduled, Published |
| Channel | Multi-select | LinkedIn, Blog, Newsletter |
| Owner | Person | Content lead |
| Publish date | Date | 2026-08-13 |
| Strategic theme | Relation or select | Category education |
| Source / evidence | URL, relation, or text | Research report link |
Available property types can include text, number, select and status, date, person, relation, URL, phone, email, formula, and system fields such as created time, last edited time, created by, last edited by, and ID.
Choose the right view
| View | Best for |
|---|---|
| Table | Data entry, audits, research inventories, and detailed comparison. |
| Board | Workflows grouped by status or another select property. Drag cards between groups to update progress where supported. |
| Calendar | Publishing schedules, launches, events, and deadline-driven work. |
| Gallery | Visual assets, creative concepts, and card-based libraries. |
Use filters to hide irrelevant rows, sorting to create a decision-ready order, and group-by to make workflow states visible. A database’s shared link respects its saved view configuration, including filtering and order.
Linked and inline databases
- Use an inline database to keep a small working table inside a planning page.
- Use a full-page database for a team operating system that needs many views.
- Use a linked database view to show the same source database in a different page and context. For example, show only LinkedIn drafts on a channel plan page without duplicating the underlying items.