Notion linked database views at scale: the clean fix for slow dashboards

Why Notion dashboards get slow

• A database has thousands of rows
• A page contains many views (dozens of views can be heavy)
• Views display too many properties, especially wide tables
• People duplicate dashboards and accidentally create multiple sources of truth

The scalable architecture (master DB + one linked view per person)

1) Keep one master database

2) Create a dashboard page for each person or role

• Add a linked view of the master database
• Filter it to only what that person owns
• Example: Officer = “Cynthia”
• Hide everything they do not need
• Use a light view (List or Table) with only the key properties visible

3) Why this works

• Everyone edits the same underlying records
• Inputs always roll up correctly to the master
• Page load improves because each view only loads a slice of the data

What not to do

• Do not create separate databases per team member if the data should stay synced.
• Do not try to “link to a linked view.” Linked views are just views of the same source.

Practical optimization checklist

• Reduce the number of views on the master dashboard page
• Use filters instead of creating dozens of redundant views
• Hide unused properties
• Prefer narrow tables
• Move heavy views into toggle headings so they are not always expanded

CTA