Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 36 ยท Databases

Linked Databases and Views

Show one Notion database in many places with linked views, filter each copy differently and use them to build personal and team dashboards.

Sooner or later you want the same database in more than one place: a task list on your home page, again on a project page, again on a team dashboard, each showing different rows. Copying the database would create separate, unsynchronised data. Instead, Notion offers linked views of databases: a window onto the original.

What a linked view is

A linked view shows the rows of an existing database ("the source") with its own layout, filters, sorts and visible properties. Edit a row in a linked view and you edit the source. Add a row and it goes into the source. Nothing is duplicated.

Create one in a page with /linked view of database (some versions label it /linked database), then choose the source database from the picker. Pick a layout and the settings are fresh, ready to be configured.

Source and linked views

Source database Holds the real rows.
Linked view A window with its own filters.
Same data Edits go to the source.

Linked views never copy rows.

1 / 2

Typical patterns

Personal dashboard. One master Tasks database elsewhere. On your Home page, three linked views: Today (Due is Today), Overdue (Due before Today, Status not Done) and Waiting (Status is Waiting). Each is a small, focused list.

Per-project pages. Each project page contains a linked view of the same Tasks database filtered by Project equals this project. When you create a new project from a template, the filter can use the This page relation shortcut so that every project page filters itself automatically; this requires the Tasks database to have a relation to Projects (covered in Relations Between Databases).

Team views. One central CRM or content database, with a view per team or person, so nobody has to maintain a private copy.

The source database

Every database has one source place where it lives. You can see the source from a linked view's header (an arrow icon or "Open source database" in the view's menu). Keep sources in a single, predictable location, for example a page named "Databases" or a hidden Teamspace, and keep dashboards elsewhere. This stops people from deleting the source by accident while tidying a dashboard.

Deleting the source database deletes the rows for every linked view. Deleting only a linked view is safe. Always check whether the block you are about to delete is a linked view or the source: a linked view usually shows a small arrow icon next to the database title.

Permissions

Linked views display the source's rows, but only to people who can access the source database. A reader who can open your dashboard but not the source database sees a "no access" message or empty rows. Plan sharing for both the dashboard and the source (the collaboration chapter later in the course covers sharing).

A model of linked views

This stand-in holds a single source array and creates several views as functions over it. Changing the source changes every view; adding through a view writes to the source.

JS One source, many linked views (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Rows are not copied (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Linked view or duplicate?

Use a linked view when the data must stay in sync (almost always). Use Duplicate (copying a whole database) only to make an independent starter, for example a client-specific copy of a template, and accept that the copies will diverge.

Building a simple dashboard

  1. Create a page named Home.
  2. Add a /2 columns layout (see Headings, Table of Contents and Columns).
  3. In the left column, add a linked view of Tasks, List layout, filtered to Assignee is Me and Status is not Done.
  4. In the right column, add a linked Calendar view of the same Tasks.
  5. Rename each block with a short heading so you can scan.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a linked view of a database copy?

    A linked view is a window onto the source database, not a copy.
  2. 2. What happens if you delete the source database?

    The source holds the data, so deleting it removes the rows everywhere.
  3. 3. When is Duplicate better than a linked view?

    Duplicate creates separate data; use it for independent starters.
  4. 4. Who can see rows in a linked view?

    Linked views respect the source's permissions.

Summary

  • Linked views show a source database with their own layout, filters and sorts.
  • Edits and new rows go to the source; nothing is duplicated.
  • Keep sources in one place and build dashboards from linked views.
  • Permissions follow the source.

Next: Relations Between Databases