Planner overview
Understand how the planner is organized, how live editing behaves, and what happens when you delete a row.
The Planner is where you plan, schedule, and organize content. It uses customizable databases that live underneath your profiles, so every database belongs to a specific Instagram account or brand context — not to your account as a whole.
How the planner is organized
A planner database is a single content workspace. Inside it you have:
- Columns — the fields that describe each piece of content (title, status, publish date, content type, attachments, and any custom fields you add).
- Views — different ways to look at the same rows. The planner ships with Table and Calendar views. You can create more views per database and switch between them from the view tabs.
- Rows — individual planned posts or content items.
- Linked views — a view that mirrors the rows of another database. Useful when you want a calendar of one team's planner to appear inside another planner.
Profile-scoped, not global
Planner databases are organized by profile. The database picker groups everything by the profile it belongs to, and switching profiles changes which databases you see. This keeps content for different brands cleanly separated.
If you work with a team, members who do not have access to a profile will not see the databases inside it — even if they can see the planner page itself. See workspace vs Instagram source for a refresher on how profiles and accounts relate.
Live, multi-person editing
When more than one person on your team edits the same database, changes appear in near-real-time without anyone needing to refresh. You will see edits from teammates land in the table or calendar as they save.
The planner debounces rapid edits per cell. If you type quickly into a title field, those keystrokes are coalesced into a single change before being saved. This keeps the live editing experience smooth and prevents your undo history from filling up with single-character entries.
Undo and redo
Use Ctrl+Z (or Cmd+Z on Mac) to undo your most recent planner change. Ctrl+Shift+Z redoes it. You can step back through your last several edits — including row creates, deletes, batch updates, and rows generated by automations.
Undo history is per-session and clears when you switch databases. It does not roll back changes made by other people on your team.
Deleting and restoring rows
Deleting a row in the planner is soft — the row is moved to a trash area on the database, not removed immediately. You can open the trash from the planner toolbar to restore rows or empty it. Deleted rows are recoverable for a window after deletion before they are removed permanently.
Deleting an entire database also archives it, pauses any automations attached to it, and disables Notion sync for that database. The action is reversible from the same trash flow until the archive period ends.
Where to go next
- Planner databases — create your first database, choose column types, and work with views.
- Planner Notion sync — mirror a planner database into a Notion page.
- Planner automations — generate recurring rows on a weekly or monthly cadence.
- Workspace vs Instagram source