How to Hide the Reverse Side of a Two-Way Relation
🔍 WiseChecker

How to Hide the Reverse Side of a Two-Way Relation

When you create a relation between two databases in Notion, the software automatically generates a reverse relation property in the second database. This reverse property appears as a column showing linked items from the first database, which can clutter your workspace or confuse team members who do not need to see that data. The feature that controls this visibility is called the “Hide Reverse Relation” toggle, located inside the relation property settings. This article explains how to locate that toggle and hide the reverse side of a two-way relation without breaking the underlying link between the databases.

Key Takeaways: Hiding the Reverse Relation in Notion

  • Relation property > Edit property > Hide Reverse Relation: Toggle this option to remove the reverse property from the second database view.
  • Database view settings > Properties > Hide: Hides the reverse relation column in a specific view without affecting other views or the relation itself.
  • Relation property > Delete property: Permanently removes the reverse relation from the second database, but also breaks the connection between the two databases.

What Is a Reverse Relation and Why Would You Hide It?

A relation property in Notion creates a bidirectional link between two databases. When you add a relation property to Database A and connect it to Database B, Notion automatically adds a corresponding relation property to Database B. This second property is the reverse relation. It shows every item from Database A that is linked to each item in Database B.

By default, the reverse relation is visible in the second database as a column. If you have a large team or a complex workspace, this extra column can make views harder to read. You might also want to restrict what data certain team members can see. Hiding the reverse relation removes the visual clutter and controls information flow while preserving the connection between the records.

There are two ways to handle the reverse relation. You can hide it from a specific view, which leaves the property intact for other views. Or you can toggle the “Hide Reverse Relation” option inside the relation property settings, which hides it from all views in the second database.

Steps to Hide the Reverse Side of a Two-Way Relation

These steps assume you already have a relation property set up between two databases. The method works in all Notion plans, including Free, Plus, Business, and Enterprise.

  1. Open the second database
    Navigate to the database that contains the reverse relation property you want to hide. This is the database where Notion automatically created the reverse property when you linked the first database.
  2. Locate the reverse relation property
    Look at the top of any database view. The reverse relation column appears with the same name as the original relation property. For example, if you named the relation “Project” in the first database, the reverse property in the second database will also be called “Project.”
  3. Open the property settings
    Click the property name at the top of the column. A dropdown menu appears. Select “Edit property” from that menu. The Edit Property dialog opens.
  4. Toggle “Hide Reverse Relation”
    In the Edit Property dialog, look for the section labeled “Reverse Relation.” There is a toggle switch labeled “Show reverse relation.” Click the toggle to turn it off. The reverse relation column disappears from all views in this database immediately.
  5. Verify the change
    Switch to another view in the same database, such as a table view or board view. Confirm that the reverse relation column is no longer visible. The original relation in the first database still works and shows linked items from the second database.

Alternative Method: Hide the Column in a Single View

If you only need to remove the reverse relation column from one specific view, use the view-level property settings instead. Click the view name at the top of the database, then select “Properties.” Find the reverse relation property in the list and toggle it off. This hides the column only in the current view. Other views of the same database still display the reverse relation column.

Common Mistakes and Things to Avoid

Deleting the Reverse Relation Property

Some users delete the reverse relation property entirely by clicking the three dots on the property and selecting “Delete.” This action removes the property from the second database, but it also severs the connection between the two databases. All linked data is lost. Only use deletion if you no longer need the relation at all.

Reverse Relation Still Appears After Toggling Off

If the reverse relation column remains visible after you toggle “Hide Reverse Relation,” refresh the page or close and reopen the database. In rare cases, a browser cache issue can keep the old column displayed. Press F5 or Ctrl+R to reload the page.

Reverse Relation Hidden but Links Still Work

Hiding the reverse relation does not break any links. Items in the first database still show connected items from the second database. You can still click into a linked item and see its connections. The only change is that the column is no longer displayed in the second database views.

Team Members Can Still Access Hidden Data Through Rollups

If you hide the reverse relation to restrict data visibility, note that a rollup property in the second database can still pull information from the first database. To fully control data access, adjust workspace permissions or use database-level sharing settings.

Hiding Reverse Relation vs Deleting vs Hiding in Views

Action Effect on Second Database Effect on Links
Toggle “Hide Reverse Relation” in property settings Reverse relation column hidden in all views Links remain intact
Hide column in a single view’s properties Reverse relation column hidden only in that view Links remain intact
Delete the reverse relation property Property removed from the database Links are permanently broken

Hiding the reverse side of a two-way relation gives you cleaner database views without sacrificing the underlying data connection. Use the property-level toggle for a global hide, or use view-level settings for selective visibility. Always avoid deleting the reverse property unless you intend to remove the relation entirely. After hiding the column, test the original relation in the first database to confirm that linked items still appear. For advanced workspaces, combine hidden reverse relations with rollup filters to display only the data you want in each view.