Notion linked data sources: separate shared content from local views

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Identify what is shared

Notion distinguishes a database's data source from the views used to display it. A linked data source exposes existing pages. Changes to its pages, properties or source title affect the original source, while view settings such as filters and sorts remain independent of the original database's views.

The current guide also says linked sources respect access to the original database. Sharing a dashboard page alone may not give its reader access to the data displayed inside it.

A fictional personal dashboard

Assume a delivery team keeps one shared task source. An individual wants a dashboard showing only their active tasks. Our recommended design starts by deciding that task identity and status should remain shared, while the dashboard's presentation serves that person's working context.

If the person changes a task's status, the team should expect a shared record change. If they change the dashboard's ordering, they should expect a presentation change. Write these expectations before configuring the dashboard.

Create an edit matrix

• Task title and status: shared operational information with a named owner.
• Task description: shared content that other readers may rely on.
• Dashboard filter: presentation logic for the intended audience.
• Dashboard sort order: a reading preference, not a new task priority policy.
• Access: the original source's authorization remains part of the design.

Rehearse with one synthetic record

1. Create a clearly marked sample task in the authorized source.
2. Link the existing data source into a controlled dashboard.
3. Find the same sample and compare its identity with the original.
4. Edit a harmless sample value through the linked presentation.
5. Inspect that value at the original source.
6. Change a dashboard view setting and compare the original view separately.
7. Check the dashboard using an authorized representative reader account where possible.

Choose a copy only for an independent lifecycle

Our information-design advice is to use shared records when two audiences need the same operational truth. Consider an independent dataset when the purpose is a frozen training exercise or a separately governed planning model. Document who maintains the copy and how it diverges.

Do not call a manually duplicated dataset a synchronized dashboard without validating an actual synchronization mechanism. Likewise, do not assume a linked presentation is safe for experimentation on real task values just because it appears on a personal page.

Acceptance criteria

Accept the design when readers understand which edits change shared information, which settings affect their presentation and which source permissions are required. Keep a visible source reference and an owner for the dashboard logic. This is an editorial implementation procedure, not a live account test or a guarantee of access for any particular reader. Moving data sources is a separate structural change and should receive its own current permission review.