Table
The default. Best for editing many properties at once and spotting gaps.
A Notion database is a collection of pages that share the same properties, such as status, date, owner or amount. You can show the same entries as a table, a board or a calendar, and link one database to another so a project knows its client. Here's how to build one, then where the links run out.
Create a database: on any page type /database and pick the inline or full-page option. On a brand-new page you can also choose Table under Get started with.
Add a view: select the + next to the database name or your existing view tabs, choose a layout and name it.
+ › Choose a view typeLink two databases: add a property, search for Relation, choose the other database, then select Add relation.
+ › Relation › Add relationTwo databases and one relation cover most small-team trackers. Swap in your own names.
Name it Clients. Add the properties you'll filter by: a Status select (Active, Paused, Past), an Account owner person property and a Start date.
Same again, named Projects, with a Status, a Due date and a Fee number property. Each row is a full page, so briefs and notes can go inside it.
Turn on Show on Clients before you select Add relation. Now each client lists its projects without anyone typing them in twice.
Watch for: the relation limit. Set it to 1 page if a project should only ever belong to one client.
On Clients, add a Rollup, pick the Projects relation, then the Fee property, then Sum. Add another that counts projects whose status isn't Done.
A board of Projects grouped by Status for the team, a calendar on Due date for deadlines, and a table filtered to "Account owner is me" for each lead.
Every view shows the same entries. Filters and sorts are set per view, so changing one doesn't touch the others.
The default. Best for editing many properties at once and spotting gaps.
Columns grouped by a property, usually Status. Drag a card to change it.
Entries placed on a date property. Good for content and deadlines.
Bars from a start date to an end date, for plans where work overlaps.
List is a clean index of titles. Gallery shows cards with an image, for portfolios or product catalogs.
Counts or totals drawn from the database, such as projects per status.
How you'll know: "Acme", "ACME Ltd" and "Acme Inc" all appear in a text column, and no rollup adds up.
Fix: Use a relation to the Clients database. Then the name exists once and every total can find it.
How you'll know: You want a client's total across projects that themselves roll up task hours, and the option isn't there.
Fix: Notion won't roll up a rollup. A formula can reach through relations instead, which is the usual way round it.
How you'll know: You export to CSV, re-import later, and the relations come back as page links in plain text.
Fix: Relations don't survive a CSV round trip. If you move data out and back in, plan to rebuild the relations.
How you'll know: Tasks, clients, invoices and meeting notes share one table full of empty columns.
Fix: Split by kind of thing, then join with relations. Use linked views when you want them on the same page.
A relation only links Notion to Notion. Your Projects database can relate to Clients, but not to the invoice in your accounting system or the deal in your CRM.
Notion does sync a few tools into a database itself: GitHub and Jira on the Business plan, and Salesforce on Enterprise. Those syncs run one way, and the synced properties are read-only in Notion. For any other tool, Notion points you to Workers, which are code your team writes and maintains, or you sync through the Notion API.
That's the part n-frames takes on. We build and run the sync that fills a Notion database from the system that owns the data, such as invoice status from QuickBooks or Xero, deal stage from HubSpot, or job dates from your scheduling tool, and writes Notion edits back where that makes sense. The Notion integrations page lists the tools teams most often connect.
A collection of pages that share a set of properties, shown as a table, board, timeline, calendar, list, gallery or chart. Every view reads the same entries, so an edit in one shows up in all of them.
A page is one document. A database is a collection where each entry is itself a page, with shared properties you can filter, sort and group across the whole collection.
Yes, with a relation property. Turn on "Show on" the other database to make it two-way, then add a rollup to pull counts, sums or dates from the related entries back.
Partly. Notion's own syncs bring GitHub, Jira and Salesforce data in one way on higher plans. A relation can't point at anything outside Notion, so other systems need a sync built on the Notion API or a Notion Worker. n-frames builds and maintains those syncs.
An inline database sits inside a page among other content, with its controls showing when you hover. A full-page database is its own page in the sidebar. To switch, drag a full-page one under another page and choose Turn into inline from the ⋮⋮ menu, or drag an inline one into the sidebar.
A view of an existing database placed on another page, with its own filters and sorts. It's how you show only this client's projects on the client's page without copying anything.