Let's say you have two databases for your theoretical business 😉
One that tracks customers
One that tracks items purchased
You want to know both which customers bought which items, as well as which items were purchased by which customers. This is a job for relations!
In the two tables above, the columns labeled
↗ Items Purchasedand
↗ Customersare relation properties, which can be added like any other database property.
Here, when you add an item bought into the Customers database, the customers who bought them automatically appear in the
↗ Customerscolumn in the Items database.
Example use cases
Connect your database of restaurants with your database of neighborhoods so you can see which restaurants are in which neighborhoods at a glance.
Connect your database of meeting notes with your database of clients to provide quick access to the notes relevant to each client.
Connect your database of tasks with your database of bigger projects to understand how projects are broken down into tasks, and how tasks contribute to projects.
Connect your database of candidates with your database of interviewers to keep track of who interviewed whom.
To relate two databases, you need two databases. So let's assume you've made the Customers and Items databases above for the purpose of this walkthrough.
Add a new column/property to your Customers database.
In the property menu, give it a name in the box provided, like
You'll be asked to find the database you want to create the relation with. You can use the input at the top to search for this database.
You'll see a preview of the relation. In this case, we've created a relation from the Customer database to the Items database.
Click the blue
Add relationbutton to finalize the creation of the new relation property.
Now when you click in a cell in this relation column, you'll bring up a menu where you can search for and choose items from the other database to add.
For example, this is how you can add which clothes each customer bought.
To add multiple items at once, click the name of the item. To delete an item, hover over and then click the
–button on the right.
Tip: To change the database you're connecting to, re-select
Relation as the property type for that particularly property. You'll be prompted to choose a new database.
Relations are created as one-way by default. But you can easily toggle on a corresponding relation in the destination database.
With two-way relations, the edits work both ways! So if you add a customer to the Items database in the relation column, the change pops up in your Customers database.
Follow the above instructions to create a new relation property.
Click the toggle that says
Show on [name of related database]. In our example, this says
Show on Items DB.
Give this corresponding relation a name.
Below, you'll see a preview of the two-way relation. In this case, we've created a relation from the Customer database to the Items database, and a relation from the Items database to the Customer database.
Click the blue
Add relationbutton to finalize the creation of these two new relation properties.
When you create a relation, you're essentially adding Notion pages stored in one database into the property field of another.
These pages can be opened and edited like any other! Click on the page in the relation column. Then click on it again in the window that pops up.
You can also remove any related page by hovering over and clicking the
–at the right.
You can choose to limit the number of pages that can be included in your relations property – with the option to select
1 pageor to have
If you select the option to limit it to
1 page, people using your database will only be able to select 1 page in the relation. This is especially useful for situations where only one page should be related to one another, for example - if only one order number should be associated with each purchase.
Let's say you want items in the same database to have relationships with each other. For example, you have a tasks database and you want each task to relate to other tasks.
Start off by creating a new relation.
Then search for and choose the database you're currently working in.
You'll now see that the database is related to
Just as with relations between two databases, you can choose to make this a one-way relation or two-way relation.
To make it a two-way relation, toggle on
Separate properties. You'll see a second property show up.
Rollups help you aggregate data in your databases based on relations. Going back to our customers and items example above, let's say you wanted to know how much each customer spent based on what they bought.
First, create the relation so you know who bought what.
Add a new column/property and choose
Property typemenu. Give it a descriptive name.
Clicking on any cell in the rollup column will bring up a new menu asking you for:
The relation property you want to roll up.
The property of those related pages you want to roll up.
The calculation you want to apply to them.
So, for our example, you'd choose to roll up the relation property
Items Purchasedand the
Priceproperty within those pages. Then you'd choose
Sumas the calculation.
Doing this adds up the prices of each item related to a customer's name, giving you the total dollars they spent in your rollup column.
There are 17 different calculations you can apply as a rollup. Here are all of them:
Show original: This just shows all related pages in the same cell. It's the same as the relation property itself.
Show unique values: This shows each unique value in the selected property for all related pages.
Count all: Counts the total number of values in the selected property for all related pages.
Count unique values: Counts the number of unique values in the selected property for all related pages.
Count empty: Counts the number of related pages with an empty value for the property selected. So, if one item a customer bought didn't have a price and that was the property selected, the rollup column would say 1.
Count not empty: Counts the number of related pages with assigned values for the property you selected.
Percent empty: Shows the percentage of related pages with no value in the property you selected.
Percent not empty: Shows the percentage of related pages with a value in the property you selected.
These rollup calculations are only available for
Sum: Computes the sum of the numeric properties for related pages (like above).
Average: Computes the average of the numeric properties for related pages.
Median: Finds the median of the numeric properties for related pages.
Min: Finds the lowest number in the numeric property for related pages.
Max: Finds the highest number in the numeric property for related pages.
Range: Computes the range between the highest and lowest numbers in the numeric property for related pages (
These rollup calculations are only available for
Earliest date: Finds the earliest date/time in the date property for all related pages.
Latest date: Finds the latest date/time in the date property for all related pages.
Date range: Computes the span of time between the latest and earliest dates in the date property for related pages.
In both tables and boards, you can apply calculations to your rollup column to get a sense of sums, ranges, averages, etc. for your entire database.
Let's say you want to find the total money spent by all customers in our example.
At the bottom of your Customers table, under your rollup column, click
Sumto add all the values in that column together and get a grand total.
When you export a relational database as a CSV file, the relation properties will export as plain text URLs. For now, you can't re-import that CSV back into Notion to re-establish the relations with other databases.
Yes, but the following will happen which can be kind of confusing:
If you create a copy of the Customers database in the example above, you'll see a new relation property automatically appear in the Items database.
This happens because relations sync two ways in Notion. When a database is duplicated, you also duplicate its relationships with other databases. You'll get the hang of it! 💪
Unfortunately not, as this could create unintended loops. We recommend sticking to rolling up other properties 😊