If you manage projects, track inventory, or organize client data in Notion, you often need to connect two separate databases. A relation property lets you link entries from one database to another so that information flows between them without manual copying. This article explains what a relation does, what prerequisites you need, and how to set it up step by step. You will also learn how to avoid common mistakes that break the link between databases.
Key Takeaways: Linking Two Notion Databases with a Relation
- Add a Relation property in the source database: Opens a menu to select the target database for the link.
- Rollup property: Pulls a value from the linked entry, such as a due date or status, into the source database.
- Delete a relation: Removes the property from either database to break the connection permanently.
What a Relation Between Two Notion Databases Does
A relation is a database property that creates a link between two separate databases in Notion. Each database retains its own structure, but entries in one database can reference one or more entries in the other. For example, a Projects database can link to a Tasks database so that each project row shows all its related tasks.
Relations work in both directions. When you add a relation property in Database A that points to Database B, Notion automatically creates a reciprocal relation property in Database B. This reciprocal property shows which entries in Database A are linked to each entry in Database B. You can rename or hide the reciprocal property, but you cannot delete it without removing the original relation.
Before you create a relation, both databases must already exist in the same Notion workspace. You cannot create a relation between databases in different workspaces. Each database should have at least one entry to test the link after setup.
Steps to Create a Relation Between Two Notion Databases
Follow these steps to link two databases with a relation property. The process is the same on the Notion desktop app, web app, and mobile app.
- Open the source database
Navigate to the database where you want the relation to appear. This is the database that will display the linked entries from the target database. For example, if you want a Projects database to show tasks, open the Projects database. - Click the plus icon in the table header
In the top-right corner of the database view, click the + icon to add a new property. A dropdown menu appears with property types. - Select Relation from the property type list
Scroll down or type “Relation” in the search box. Click Relation. A dialog opens asking you to choose the target database. - Choose the target database
In the dialog, click the Select a database field. A list of all databases in your workspace appears. Click the name of the database you want to link to. For example, select the Tasks database. - Optional: Name the relation property
By default, Notion names the new property after the target database. You can rename it by clicking the property name at the top of the column and typing a new name. For example, rename it “Related Tasks.” - Click Create relation
Click the blue Create relation button. Notion adds the relation property to your source database and automatically adds a reciprocal relation property to the target database. - Link entries between databases
Click inside any cell in the new relation column. A dropdown shows all entries from the target database. Click one or more entries to link them. You can also type to search for a specific entry. Linked entries appear as blue pills in the cell.
To verify the link works, open the target database. You should see a new column named after the source database. Click a cell in that column to see which source entries link to the current entry.
Common Mistakes and Things to Avoid When Creating a Relation
Relation property shows no options in the dropdown
If the relation cell displays an empty dropdown, the target database has no entries. Add at least one entry to the target database before trying to link. Also check that the target database is not filtered or locked in a way that hides its entries.
Accidentally created a duplicate relation
If you add a relation property twice pointing to the same target database, Notion creates two separate relation columns. This can confuse your team because both columns link to the same database but are independent of each other. Delete the extra property by clicking the property name, then clicking Delete.
Reciprocal relation property is missing
The reciprocal property always appears in the target database after you create a relation. If you cannot see it, check that you have permission to view the target database. If the target database is set to “Can view” only, you may still see the property but cannot edit it. Ask the workspace owner to grant you edit access.
Linked entries disappear after changing the database view
Relations persist even when you change the database view type, such as switching from Table to Board view. If linked entries appear missing, check that the relation column is not hidden in the current view. Click the view name, then Properties, and ensure the relation property is checked.
Notion Relation vs Rollup: Key Differences
| Item | Relation | Rollup |
|---|---|---|
| Purpose | Links entries between two databases | Pulls a value from a related entry into the source database |
| Requires a relation first | No | Yes, a rollup depends on an existing relation |
| Example use | Show all tasks assigned to a project | Show the due date of the earliest task in a project |
| Data displayed | Names of linked entries | Computed values like text, number, date, or formula from the linked entry |
| Editable directly | Yes, you can add or remove links | No, values are read-only and update automatically |
After you create a relation, consider adding a rollup property to display specific information from the linked entry without opening the other database. For example, use a rollup to show the status of a task directly in your project table.
You can now link two Notion databases using the relation property and manage cross-database connections in your workspace. Next, try adding a rollup property to pull a deadline or progress percentage into your main database. To keep your workspace organized, name relation properties clearly so other team members understand the connection at a glance.