You want to see which meeting attendees connect to which projects and decisions inside Notion. A relation graph shows these links visually without switching between pages. This article explains how to build a relation graph that maps meeting attendees to their associated meetings, projects, and action items. You will learn the database structure, relation setup, and linked view configuration needed to create a functional attendee network.
Key Takeaways: Building a Meeting Attendee Relation Graph in Notion
- Database schema with three core databases: Attendees, Meetings, and Action Items — each with a relation property linking to the others.
- Relation properties on each database: Creates bidirectional links so a single attendee can be linked to multiple meetings and action items.
- Linked Database View on an attendee page: Displays all related meetings and action items in a table or board view, forming the visual graph.
What Is a Relation Graph for Meeting Attendees
A relation graph in Notion is not a single feature. It is a combination of database relations and linked views that show how records connect. For a meeting attendee network, the graph shows which people attend which meetings, which meetings produce which action items, and which action items are assigned to which attendees. The graph is built entirely with Notion databases, relation properties, rollup properties, and linked database views. No external tools or code are required.
The graph is useful for teams that run frequent meetings and need to track accountability. Instead of searching individual meeting notes for who attended or what was assigned, the relation graph displays all connections from a single attendee page. The underlying mechanism is Notion’s relation property, which creates a two-way link between records in two databases. When you open an attendee page, you see a linked view of every meeting they attended and every action item assigned to them.
Prerequisites for Building the Graph
Before you start, ensure you have a Notion workspace with full access to create databases. You need at least three databases: one for attendees, one for meetings, and one for action items. The databases must be in the same workspace — cross-workspace relations are not supported. You also need the ability to add relation and rollup property types to each database. These property types are available on all Notion plans, including Free, Plus, Business, and Enterprise.
Steps to Create the Attendee Network Relation Graph
Follow these steps in order. Each step builds on the previous one. Do not skip the relation property setup — it is the core of the graph.
- Create the Attendees database
Create a new database in Notion. Name it “Attendees”. Add the following properties: Name (title), Email (text), Department (select), and Role (select). This database stores every person who attends meetings. Each row is one attendee. - Create the Meetings database
Create a second database. Name it “Meetings”. Add these properties: Title (title), Date (date), Purpose (text), and Status (select). This database stores each meeting event. One row equals one meeting instance, not a recurring series. - Create the Action Items database
Create a third database. Name it “Action Items”. Add properties: Task (title), Due Date (date), Priority (select), and Status (select). This database stores tasks that come out of meetings. - Add a relation between Attendees and Meetings
Open the Attendees database. Add a new property. Select Relation as the type. In the relation setup, choose the Meetings database. Name the relation “Meetings Attended”. Notion automatically creates a matching relation property in the Meetings database called “Attendees”. This creates the first link in the graph. - Add a relation between Meetings and Action Items
Open the Meetings database. Add a new Relation property. Select the Action Items database. Name the relation “Action Items from Meeting”. The Action Items database now gets a matching relation property called “Meeting”. This links meetings to the tasks they produce. - Add a relation between Action Items and Attendees
Open the Action Items database. Add a new Relation property. Select the Attendees database. Name the relation “Assignee”. The Attendees database gets a matching relation property called “Assigned Actions”. This completes the triangle: attendees link to meetings, meetings link to action items, and action items link back to attendees. - Add rollup properties for quick summaries
In the Attendees database, add a Rollup property. Set it to calculate from the “Meetings Attended” relation. Choose the Date property from the Meetings database. Set the calculation to “Show original”. Name it “Meeting Dates”. This shows all meeting dates an attendee participated in, directly on the attendee row. - Create a linked database view on an attendee page
Open any attendee page. Type /linked view of database. Select the Meetings database. In the view filter, set “Attendees” relation to “Contains” the current attendee. This displays only the meetings that attendee attended. Repeat this step to add a linked view of the Action Items database, filtered by “Assignee” contains the current attendee. These linked views form the visual graph on the page. - Customize the linked view layout
On the attendee page, change the linked view of Meetings to a Timeline view to see when the attendee was busy. Change the linked view of Action Items to a Board view grouped by Status. This gives you a visual network of the attendee’s activity without leaving the page.
Common Mistakes and How to Avoid Them
Relation property does not appear in the linked view
If the linked view on an attendee page shows all meetings instead of only that attendee’s meetings, the filter is missing or incorrect. Open the linked view, click the filter icon, and add a filter where the Attendees relation contains the current page name. Notion’s filter condition must be “Contains” not “Is” because the relation can hold multiple values.
Rollup property shows a comma-separated list instead of dates
When you set a rollup to show the original value from a relation that has multiple linked records, Notion concatenates them with commas. To see each date on its own line, use the “Show unique” calculation instead of “Show original”. Alternatively, keep the linked view as the primary way to see dates and use the rollup only for a count.
Duplicate attendee entries break the graph
If the same person appears in the Attendees database with slightly different names (for example, “John Smith” and “Jonathan Smith”), the relation graph will not connect them to the same meetings. Use a unique identifier such as an email address property and deduplicate the database before linking records. Notion does not have a built-in merge tool, so you must manually delete duplicates and reassign relations.
Linked view loads slowly on large databases
If you have hundreds of meetings and action items, the linked view on an attendee page may take several seconds to load. Reduce the load by adding a filter to the linked view that limits the date range, for example, only meetings from the last 90 days. You can also archive old meetings to a separate database and link only active ones.
Attendee Network Structure: Database Properties Compared
| Item | Attendees Database | Meetings Database | Action Items Database |
|---|---|---|---|
| Primary property | Name (title) | Title (title) | Task (title) |
| Relation to Attendees | Self (primary key) | Attendees (relation) | Assignee (relation) |
| Relation to Meetings | Meetings Attended (relation) | Self (primary key) | Meeting (relation) |
| Relation to Action Items | Assigned Actions (relation) | Action Items from Meeting (relation) | Self (primary key) |
| Rollup example | Meeting Dates (from Meetings) | Attendee Count (count of Attendees) | Meeting Date (from Meetings) |
| Linked view on page | Meetings attended + Assigned actions | Attendee list + Action items from meeting | Assignee details + Meeting details |
The table above shows how each database connects to the others. The Attendees database holds the central identity. The Meetings database holds the event data. The Action Items database holds the deliverables. Every relation property creates a bidirectional link that you can traverse from any page in the network.
You now have a working relation graph for your meeting attendee network. From any attendee page, you can see all meetings they attended and all action items assigned to them. To extend the graph, add a Projects database and create a relation between Meetings and Projects. Use the rollup property on the Attendees database to show project names linked to the meetings they attended. Press Ctrl + P on Windows or Cmd + P on Mac to quickly search and jump between any attendee, meeting, or action item in the network.