When you create a relation between two Notion databases, the relation is one-directional by default. This means you can see linked records in one database, but not the other. A bidirectional relation shows linked records in both databases, which is essential for project management, CRM, or any cross-referenced workflow.
The reverse name is the label that appears in the second database for the linked records. By default, Notion names it after the original relation, but you can set a custom reverse name for clarity. This article explains how to create a bidirectional relation with a custom reverse name in Notion.
You will learn the exact steps to set up the relation, rename the reverse property, and avoid common mistakes like circular references or broken links.
Key Takeaways: Building a Bidirectional Relation With Custom Reverse Name
- Database properties > Relation > Show on the other database: Enables the bidirectional link between two databases.
- Relation settings > Rename reverse property: Changes the label that appears in the second database for the linked records.
- Relation property in each database: After setup, both databases display a property that links to records in the other database.
What a Notion Bidirectional Relation Does
A relation in Notion connects records from one database to another. For example, a Tasks database can link to a Projects database. With a one-way relation, only the Tasks database shows the linked project. A bidirectional relation adds a property to the Projects database that shows all tasks linked to that project.
The reverse name is the name of that property in the second database. By default, Notion uses the name of the original relation property. If your original relation is called “Project,” the reverse property in Projects will also be called “Project.” You can change this to something more descriptive, like “Related Tasks.”
Before starting, both databases must already exist in the same Notion workspace. You cannot create a relation across different workspaces. Also, you need edit permissions for both databases.
Steps to Create a Bidirectional Relation With a Custom Reverse Name
These steps assume you have two databases. In this example, Database A is “Tasks” and Database B is “Projects.” You will create a relation from Tasks to Projects, then customize the reverse name in Projects.
- Open Database A and add a Relation property
Navigate to the Tasks database. Click the + button in the last column header. Select Relation from the property type list. A dialog appears asking you to choose the second database. - Select the second database
In the dialog, click the dropdown under “Connect to” and choose Projects. Notion will create a relation property in Tasks and automatically create a corresponding property in Projects. Do not close the dialog yet. - Enable bidirectional linking
In the same dialog, locate the toggle labeled Show on the other database. Turn this toggle on. This is what makes the relation bidirectional. Below the toggle, a text field appears labeled “Reverse property name.” - Enter a custom reverse name
In the “Reverse property name” field, type the name you want to appear in the Projects database. For example, type Related Tasks. This name will be the property name in the Projects database. Click Create relation to finish. - Verify the reverse property in Database B
Open the Projects database. You should see a new column named “Related Tasks” (or whatever you typed). This column shows all Tasks records that are linked to each project. If you do not see it, refresh the page or check that you have edit permissions.
Linking Records After Setup
Once the relation exists, you can link records. In the Tasks database, click the relation cell for a task and select a project. That project’s “Related Tasks” property will automatically update to show the linked task. Both databases now reflect the connection.
Common Mistakes and Things to Avoid
Relation property shows as a rollup
If the reverse property appears as a rollup instead of a relation, you may have accidentally selected “Rollup” when creating the relation. Delete the property and start again. A bidirectional relation uses the relation property type, not rollup.
Reverse name does not appear in the second database
This happens when you turn off “Show on the other database” during setup. To fix, edit the relation property in Database A. Click the property name in the column header, choose Edit property, and turn on the toggle. You can also rename the reverse property there.
Circular relation between two databases
A circular relation occurs when you create two separate relations between the same pair of databases. For example, a relation from Tasks to Projects and another relation from Projects to Tasks. This creates duplicate properties and confusion. Use one relation with the bidirectional toggle instead of two separate relations.
Cannot delete the reverse property without breaking the relation
If you delete the reverse property in Database B, the bidirectional link breaks. The original relation in Database A may still work, but it will be one-way. To remove the bidirectional feature, edit the original relation and turn off “Show on the other database.” Then delete the reverse property.
Notion Relation vs Bidirectional Relation vs Rollup
| Item | One-way Relation | Bidirectional Relation | Rollup |
|---|---|---|---|
| Purpose | Links records in one direction | Links records in both directions | Displays aggregated data from a related record |
| Shows in second database | No | Yes, as a relation property | Only if used with a relation |
| Custom reverse name | Not applicable | Yes, you set it during creation | Not applicable |
| Data type | Relation | Relation | Text, number, date, or computed value |
| Use case | Simple link, e.g., assign a category | Cross-reference, e.g., tasks per project | Sum of task hours per project |
Bidirectional relations are ideal when you need to navigate between linked records from either database. Rollups are not a replacement for relations; they display calculated data from a relation.
Conclusion
You can now create a bidirectional relation between two Notion databases and set a custom reverse name for clarity. The key settings are the “Show on the other database” toggle and the “Reverse property name” field in the relation dialog.
After setting up the relation, test it by linking a few records in each database. Verify that the reverse property updates correctly. For advanced workflows, consider combining bidirectional relations with rollups to display aggregate data like total task counts per project.
A practical tip: use descriptive reverse names that match the context of the second database. For example, use “Assigned Projects” in a Team Members database instead of the default relation name. This keeps your database schema readable for collaborators.