Create and manage planner databases
Create a planner database, set up columns and views, and recover rows you deleted by mistake.
A planner database is the unit you plan content inside. Each one has its own columns, views, and rows, and belongs to a single profile. This page walks through creating one and shaping it to match how you actually plan content.
Create a database
- Open Planner from the sidebar.
- Click the Database picker at the top of the page and select Create Database.
- The new database appears under the active profile with a starting set of columns. Rename it by opening the database picker and editing the name.
If your team has access to multiple profiles, the picker groups databases by profile. Pick the profile context first, then create the database in that group.
Choose column types
Click the + at the end of the column row in Table view to add a column. The planner supports the column types you would expect from a content database:
- Text — short titles, captions, notes.
- Long text — longer briefs or descriptions.
- Date — publish dates, deadlines.
- Status — a workflow state with a small set of named values (for example, Idea, Drafting, Ready, Published).
- Select and Multi-select — single or multiple tagged values for things like format, channel, or pillar.
- Checkbox — yes-or-no flags.
- URL — links to drafts, references, or external assets.
- Post preview — pulls a published post into the row so you can see what shipped.
- Set link — connects the row to a saved set in Posts, so you can group planned content with the published posts it relates to.
- Computed — derives a value from other columns in the row.
You can rename columns, change their type, and reorder them by dragging the column header. Hidden columns stay on the database but disappear from the active view.
Work with views
Each database starts with a default Table view. Add more views from the view tabs above the table:
- Table — a spreadsheet-style grid with filters, sorts, and column visibility.
- Calendar — places rows on a month calendar based on their date column. Useful for content schedules.
Switch views from the tabs at the top. View settings — filters, sorts, hidden columns, rows per page — are saved to the view, not the database, so each view can show the same rows differently.
You can also create a linked view that mirrors rows from a different database, with its own table or calendar layout.
Reorder rows and views
In Table view, drag a row by its handle to reorder it. Reorder views the same way by dragging a view tab. The new order is saved to the database.
Edit rows live
Click any cell to edit it. Changes save in the background while you keep working. If teammates are editing the same database, you will see their changes appear without refreshing.
Use Ctrl+Z (or Cmd+Z) to undo your last change. Ctrl+Shift+Z redoes it. See planner overview for how the planner debounces rapid edits and how undo history is scoped.
Delete and restore rows
To delete a row, open the row's menu and choose Delete. The row is moved to the database's trash area — not removed immediately.
Open the Archived & trash modal from the planner toolbar to:
- review rows that have been soft-deleted,
- restore a row back into the active table, or
- empty trash to remove rows permanently.
Deleted rows remain recoverable for a window after deletion. After that window passes, they are removed permanently and undo can no longer bring them back.
Delete a whole database
To delete an entire database, open the Database picker, hover the database name, and click the trash icon. Deletion archives the database, pauses any automations attached to it, and disables its Notion sync. You can restore the database from the same trash flow until the archive period ends.
Related pages
Planner overview
Understand how the planner is organized, how live editing behaves, and what happens when you delete a row.
Mirror a planner database into Notion
Connect a planner database to a Notion page, understand which side is authoritative, and disconnect a single mirror without removing Notion entirely.