Notion linked database views display existing records on another page, with a presentation suited to the people using it. Your team can work from the same underlying information without maintaining a second task list. Notion’s linked database guide explains this shared-content approach.
Table of Contents
Start with the question each team needs to answer
Illustrative example: a small facilities company keeps its jobs in one database. The operations coordinator wants to know what needs allocating today. An account manager wants to review unfinished work for a particular client. These are different ways of looking at the same jobs, so a second independently maintained list would create unnecessary reconciliation.
Write a short purpose above each view: “Allocate today’s work” or “Prepare the client review”. Agree who maintains the underlying status and deadline. A dashboard will not resolve inconsistent data entry or a disagreement about what “Complete” means.
If you need to connect separate kinds of records, such as projects and meeting notes, use our Notion relations guide. A linked view displays records elsewhere; a relation describes a connection between records.
Add a linked view to the working page
- Open the page where the team will use the information and type /linked.
- Choose Linked view of data source and select the intended source.
- Copy an existing view or create a new one, then give it a useful name.
- Open a familiar record and confirm you selected the correct working database.
The current menu label appears in Notion’s linked-view instructions; its setup guide describes choosing an existing or new view. Avoid selecting an old trial database simply because it has the same name. Ask the database owner to identify the source when several plausible results appear.
Know which changes affect everyone’s records
| Action | Effect to expect |
|---|---|
| Change the linked view’s filter, sort or grouping | The original database’s views are unaffected. |
| Hide a property using the view’s visibility settings | The field is hidden in that view; it has not been removed. |
| Edit a record or the source’s properties | The underlying source changes too. |
Notion distinguishes local view changes from edits to the source’s title, properties and pages in its data-source documentation. Its view settings guide covers property visibility. Keep “hide this column here” separate from changing the property itself.
For the facilities company, correcting a deadline during the client review changes the job the coordinator works from. Agree who may make that correction and where they should explain it. Moving work out of sight is a presentation decision; marking it complete is a business decision.
Make the view useful without making exceptions disappear
Open the database settings and use Filter under View settings to choose a property condition. Use Sort to set the order. Notion provides Save for everyone for a shared filter or sort; without it, the change applies only to you. Filter and sort instructions.
For the operations page, begin with unfinished jobs and inspect the deadline and owner. For a client review, choose the relevant client and unfinished status. Add one condition at a time and keep a small sample of records you expect to see. Avoid a complicated filter that nobody can explain during a handover.
Include a job without an assignee, one without a deadline and one just marked complete in your rehearsal. Decide where each should appear. If the daily page hides unresolved exceptions, keep a clearly named place to review them rather than hoping somebody remembers.
Review permissions separately from filters
Linked data retains the original source’s access rules; sharing the surrounding page does not grant broader source access. Notion documents this permission boundary. A filtered client view should therefore not be treated as a substitute for properly restricted access.
Can edit content protects the original database’s structure while allowing record changes. Those users can still create linked databases and customise views, filters and sorts there. This exception is explicit in Notion’s database collaboration guidance. Do not describe that permission as preventing all view customisation.
Ask a colleague with the intended access to open the working page and a sample record. Check what they can read and change. Notion applies the broadest access a person has received, so review other sharing routes if the result is more permissive than expected. Permission overrides.
Check the result before making it the team’s starting page
Use harmless sample records to compare the linked page with the source. Change a status in one place and inspect the other; change the linked view’s sort and inspect the source’s view separately. Then ask a colleague to explain which edits change the job and which change only its presentation.
For consistent new entries, our Notion database templates guide covers reusable starting structures. Keep the source owner and each view’s purpose documented, and revisit the filters when the team changes its working process.
Sources reviewed 26 October 2026 against official Notion documentation. The facilities-company example and suggested checks are illustrative, not reported product tests.
