In Notion, add a new property to a database, choose Relation, search for the database you want to connect to and click Add relation. Relations are one-way by default, so toggle Show on the other database if you want a two-way relation. You can also limit a relation to 1 page or leave it with no limit.
Linking clients to projects, as an example
Say you've got one database of clients and another of projects. Right now you type the client's name into each project by hand, and the two never quite match. A relation property fixes that. It connects data between two databases, such as customers and the items they've bought, so each project points to a real client page instead of a line of text.
Once the link exists, you can click from a project straight to its client, and, if you set it up two-way, see every project from the client's page. If you haven't built the databases yet, my guide on creating a database in Notion is the place to start.
Adding the relation property
- Open the database and add a new property, then give it a name, such as Client.
- Search for Relation as the property type.
- Search for the database you want to connect to. A preview of the relation appears.
- If you want it two-way, toggle Show on [name of related database] and name the matching relation, such as Projects.
- Click the blue Add relation button.
- Click a cell in the new column and pick pages from the other database.
That's it. Your projects now point at clients, and if you switched on the two-way option, each client shows its projects too.
One-way by default, two-way when you ask
Relations between two different databases are one-way by default. The project database shows the client, but the client database shows nothing about projects. When you toggle Show on the related database and click Add relation, edits then show in both databases.
Notion Help's Relations and rollups article flags this as the common surprise: the other database shows nothing until you switch the toggle on. If you're staring at a client page wondering where the projects went, that's why. The same article notes that relating a database to itself works differently from relating two separate ones.
Settings worth knowing after it's created
Limit to one page
You can limit a relation to 1 page, or choose No limit. For something like Client on a project, 1 page makes sense, because each project belongs to one client. For Tags or Team members, leave it open.
Choose what's shown
You can pick which properties of the linked pages are Shown in relation or Hidden in relation, so the cell shows the useful details without clutter. Property visibility can be set to Always show, Hide when empty or Always hide, which keeps empty relation fields from crowding your page.
Remove or change a link
To remove a related page, hover over it and click the minus button. To point the property at a different database, re-select Relation as the property type and choose the new database.
Relating a database to itself
You can relate a database to itself by choosing the database you're currently working in. That's handy for things like parent and child tasks, or linking one article to related articles in the same content database. Remember the caveat from Notion Help: a self-relation behaves differently from one between two databases, so check how it looks on both sides before your team starts using it.
Once relations are in place, rollups are the natural next step for pulling values across, though that's a job for another day. My overview of how Notion databases fit together covers the bigger picture.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
The same idea in another database tool
Airtable lets you link records between tables with linked record fields, and its help article says that's available on all plan types. If you're weighing the two tools, my roundup of Notion alternatives goes further.
My advice before you link everything
Start with one relation that removes the most retyping, usually client to project, and make it two-way from the start so nobody goes looking for missing links. Set the 1 page limit where it makes sense, hide empty fields, and only add more relations once your team is using the first one. A small, tidy set of links beats a web of half-used ones every time.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Is a Notion relation two-way?
It's one-way by default. Toggle Show on the related database to make it two-way.
Can I limit how many pages a relation holds?
Yes, to 1 page, or you can choose no limit.
Can a database relate to itself?
Yes. Choose the database you're working in as the related database.
How do I change the related database?
Re-select Relation as the property type and choose another database.
How do I hide an empty relation?
Use Property visibility and choose Hide when empty.
