How to Build a Master Task Database in Notion (with Linked Views)

Build one master task database in Notion and use linked views for each team. Get a clean property set, view templates, and rollout tips that scale.

Workflow Automation Project Management

Sep 15, 2026

How to Build a Master Task Database in Notion (with Linked Views)

TABLE OF CONTENTS

The pattern: one master database, many linked views

Step 1: Create the master Tasks database

Step 2: Build role- and division-specific views

Step 3: Create linked views on each team page

Step 4: Add lightweight dashboards (without overbuilding)

Common mistakes (and how to avoid them)

When to use a template vs. starting from blank

Where Notion AI can help (optional)

Get help building your Notion task database

If your Notion tasks are scattered across department pages, the simplest way to scale is to create one master Tasks database and then use linked views (filtered per team) everywhere else. You keep a single source of truth, but each group sees only what they need.

The pattern: one master database, many linked views

A Notion “database” is your tasks table. Each row is a task page you can open for notes, checklists, files, and more.

A linked view is just a view of that same database placed somewhere else. You can filter it differently on every page (for example: Logistics tasks only, or “Assigned to me” only) without duplicating the data.

Step 1: Create the master Tasks database

Create a new database named Tasks (start from blank or a template). Either way, make sure you end up with these core properties:

Status (Status) — your workflow (To do → In progress → Done)
Assignee (Person) — who owns the task
Due date (Date)
Priority (Select) — keep it simple (P0/P1/P2 or High/Medium/Low)
Division/Team (Select or Multi-select) — the department or area (ERP, logistics, store, etc.)

Optional (use only if it helps):

Revenue impact (Number or Select)
Requester (Person)
Project (Relation) if you also track projects

Tip: avoid using Text properties for things you want to filter/group by. Use Status/Select so teams can’t accidentally create five versions of “High priority.”

Step 2: Build role- and division-specific views

In the Tasks database, create a few “starter” views you can reuse:

All open tasks (Table)

Filter: Status is not Done

By status (Board)

Group by: Status
Filter: Status is not Done

Overdue (Table)

Filter: Due date is before today AND Status is not Done

By division (Board)

Group by: Division/Team
Filter: Status is not Done

These views are the building blocks you’ll place across the workspace.

Step 3: Create linked views on each team page

On a division or role page (for example: “Logistics”), insert a linked view of the Tasks database and set filters like:

Division/Team contains Logistics
Status is not Done

For a personal “home” page, use filters like:

Assignee contains me
Status is not Done

Now each page shows only relevant tasks, but everyone is still editing the same master database.

Step 4: Add lightweight dashboards (without overbuilding)

Once linked views are in place, you can add quick rollups on a higher-level page:

“Open tasks by division” board view
“Overdue tasks” view
“This week” view (Due date is within the next 7 days)

If you also have a Projects database, roll up task completion to show project progress.

Common mistakes (and how to avoid them)

Making separate databases per team. This creates duplicates and inconsistent fields. Start with one master database, then segment with linked views.
Too many properties on day one. Add only what you need to filter, assign, and report. You can always expand later.
No clear Status workflow. Keep status options tight so views stay reliable.

When to use a template vs. starting from blank

Use a template if you need something usable fast and you don’t mind deleting extra properties.
Start from blank if you want a minimal setup tailored to your divisions from the beginning.

Where Notion AI can help (optional)

If you use Notion AI, it can speed up repetitive setup tasks like creating views and filters from a quick prompt. Still, it’s worth sanity-checking the filters so each team only sees what they should.