Notion relations connect pages held in different databases. Use one when a meeting note should point to its project, rather than asking colleagues to copy the same project details into every note. Decide what the relationship means before adding the property.
Table of Contents
Define the connection before building it
Illustrative example: a consultancy keeps projects in one database and meeting notes in another. Each client review belongs to a project. Write down the rule in a sentence: “This meeting discusses this project.” Then ask whether a meeting can genuinely cover several projects or should always have one primary project.
Choose names that make sense to the person entering the information. Project is clearer than Link 1. Avoid creating a second project record just because a colleague cannot immediately find the first. Agree a recognisable naming convention and someone responsible for resolving duplicates before building reporting around the connection.
Add the relation and choose its direction
Add a Relation property, choose the target database and select pages. Links start one-way; enable the corresponding target property for two-way updates. Creating relations and two-way links.
For the consultancy, decide whether someone opening a project should also find its meeting notes. If so, name the corresponding property Meeting notes. Rehearse with harmless records and inspect both ends after adding and removing a link. Record which database is which; similarly named practice and live databases can be easy to confuse.
Choose one related page or several
The relation can be limited to 1 page or set to No limit. Choose the restriction that matches the intended relationship. Relation page limits.
If each meeting must have one primary project, a single-page choice makes that intention easier to follow. If cross-project reviews are common, agree how staff should use multiple links. Do not force a convenient database rule onto work that genuinely has a different shape. Ask a colleague to classify an awkward real-world example before committing to the structure.
Check access separately from the relationship
Use Share to review page access. Can edit content permits database-page and property-value editing, but prevents changes to database structure, views, sorts and filters. Notion applies the broadest access granted to a person, so a narrower setting does not cancel wider access elsewhere. Sharing and permission levels.
Ask the intended contributor to open both sample records using their normal account. Check whether they can find the right project, read the material they need and update the intended field. Do not broaden access to an entire client collection just to make a selector easier to use. Have the database owner review the sharing arrangement when the intended audience changes.
Treat rollups and copies with care
A rollup summarises a property through a relation. CSV exports produce text URLs and cannot restore relations on reimport. Database duplication converts two-way relations to one-way. Rollups, duplication and CSV limitations.
Before depending on a summary, compare it with the related sample records by hand. Decide who investigates missing links or inconsistent values. Keep an explanation of what the summary is meant to represent. A tidy total is less useful when nobody can explain which records should contribute to it.
Keep repeatable setup from fixing the wrong project
Our Notion database templates guide covers reusable entry structures and warns about fixed relation defaults. For a shared meeting-note structure, make choosing the current project an explicit check. Inspect a sample for two different projects before adopting the template across the team.
Our Notion database buttons guide addresses deliberate handover actions. Keep the relationship understandable before adding a button that changes other records. Assign an owner to maintain property names, explain unusual cases and review connections after database changes. These are proposed checks, not results from testing a Notion workspace.
Sources reviewed 20 October 2026 against official vendor documentation. Examples and suggested rehearsal checks are illustrative, not reported product tests.
