Get AI summaries of any video or article — Sign up free
Notion Masterclass: Build a Personal Dashboard from Scratch thumbnail

Notion Masterclass: Build a Personal Dashboard from Scratch

6 min read

Based on Thomas Frank Explains's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Build the dashboard as a multi-column Notion page with styled headings, then use toggles to keep dense content collapsible.

Briefing

A personal dashboard in Notion can function as a single “home base” that links to tasks, notes, projects, and reference pages—while also letting people take quick actions (like adding inbox items) without leaving the page. The core build centers on a multi-column layout with linked and embedded views, so the dashboard becomes both a navigation hub and an interactive workspace rather than a static collection of links.

The tutorial starts by defining the dashboard’s purpose: quick access to a task manager, a note-taking system, project tracking, and even embedded database views. The example dashboard is designed around a “link-heavy” philosophy—favoring page links and linked database views so updates stay consistent across the workspace. The builder begins with a blank full-width page, adds styled headings (gray backgrounds and emojis), and sets up a multi-column structure: Tasks on the left, Notes to the right, with Web Links and Reference sections beneath.

In the Tasks column, the dashboard pulls in multiple views from a free “Ultimate Tasks” system—Today, Tomorrow, and Next 7 Days—by creating links to those pages and pinning the dashboard itself to the favorites bar for fast sidebar access. A habit tracker template is added as another quick entry point. The most interactive element is an inbox-style task area: instead of embedding a raw “all tasks” database and rebuilding filters, the tutorial duplicates the already-configured inbox view from Ultimate Tasks and pastes it into the dashboard. That embedded inbox sits inside a toggle (collapsed by default) and is tuned to load fewer items on first page load (10 instead of 50) to keep the dashboard responsive on narrower screens.

The Notes column uses a free note-taking system template. A linked database is required so that notes added from the dashboard appear in the original note inbox—unlike a copied database, which would create a separate dataset. The linked view is configured with filters that ensure only relevant notes show up (status not empty, and URL not empty), plus a sort that surfaces the most recently updated notes first. A Notion workaround is used to duplicate the view configuration: a “dummy” view is created to access duplication controls, then the view is adjusted to a list format for better fit in the dashboard’s layout.

Web Links and Reference sections round out the page with quick bookmark-style access and linked page blocks for frequently visited materials. A quick links bar is added via a toggle containing a table of contents link, improving navigation especially on mobile where the dashboard collapses into a single column. Additional dashboard blocks include a callout reminder (“work hard… quit at a reasonable time… spend time with your friends and your family… go outside”) and a synced block demo to show how one block can appear in multiple locations while staying linked.

Finally, the dashboard adds a daily tasks checklist using a gallery view of a database inside a toggle, filtered to hide archived items and set to show a small number of cards initially. A weather widget is embedded at the end using Indify (free), configured for Denver and displayed for today and tomorrow. The result is a practical, mobile-friendly dashboard that supports both navigation and fast capture—built with linked views, toggles, and embeds so the dashboard stays current as the underlying systems evolve.

Cornell Notes

The dashboard is built as a Notion “home base” that combines navigation and quick capture. It uses a multi-column page with linked page blocks and linked database views so tasks and notes added from the dashboard update the original systems. The task inbox is duplicated from an already-filtered Ultimate Tasks view to avoid rebuilding complex filters, then placed inside a collapsed toggle with reduced initial load (10 items). The notes inbox requires a linked database (not a copied database) so new notes appear in the same dataset; filters handle quirks with the Notion web clipper. A mobile-friendly quick links bar, a daily checklist, and an Indify weather embed finish the dashboard.

Why does the tutorial emphasize “linked” views instead of copying databases into the dashboard?

Linked database views keep one source of truth. When the dashboard uses “link to database,” the inbox shown on the dashboard is a window into the original database, so adding items from the dashboard updates the same underlying records. Copying a database would create a separate dataset, so new notes or tasks added in the copy would not appear in the original inbox. The notes section makes this distinction explicit: the note inbox can’t be duplicated like the tasks views because it lacks the linked-view arrow, meaning it would otherwise become an independent copy.

How is the task inbox made interactive without rebuilding filters and sorts from scratch?

Instead of embedding a generic “all tasks” database and recreating the inbox logic, the tutorial duplicates the existing inbox view from the Ultimate Tasks system (the view already has the right filters and sorts). That duplicated linked view is then cut and pasted into the dashboard. The inbox is set to list view for narrow columns, wrapped in a toggle labeled “inbox,” and configured to load fewer items on first page load (10) so the dashboard stays fast while still surfacing what’s due today.

What filters are used for the notes inbox, and why do they matter?

The linked notes inbox applies two main conditions: (1) status is not empty, and (2) url is not empty, combined with an OR. The url condition exists because the Notion web clipper doesn’t respect forcing functions tied to status; clipping adds a URL, so url not empty becomes a reliable way to ensure clipped notes land in the inbox. Sorting is set to updated descending so the most recently worked-on notes appear first.

What’s the “dummy view” trick used for duplicating a complex view configuration?

Notion makes it awkward to duplicate a view unless there’s another view to access duplication controls. The workaround is to add a temporary “dummy” view, use the view dropdown/three-dot menu on the original table view to duplicate it, then convert the duplicated view to a list view. After the needed list view is created, the dummy view (and any extra copy) can be deleted.

How does the tutorial improve mobile usability for a dashboard with many sections?

It adds a quick links bar using a toggle containing a table of contents link. On mobile, the dashboard collapses into a single column, so long sections would otherwise require lots of scrolling. The quick links toggle lets users jump directly to a heading (and highlights the section when it’s already visible), making navigation practical on iPhone or Android.

How is the weather widget added, and what does “embed” accomplish here?

The tutorial uses Indify to generate a small weather widget configured for Denver and set to show two days (today and tomorrow). Instead of bookmarking, it uses “create embed” in Notion, which inserts a tiny web page that displays only the widget. The embed’s width and height can be adjusted to fit the dashboard column layout.

Review Questions

  1. When would a copied database fail to behave like an inbox, and how does a linked database fix that?
  2. What steps are used to keep the inbox fast on first load, and why does that matter for dashboard usability?
  3. How do the notes inbox filters relate to the behavior of the Notion web clipper?

Key Points

  1. 1

    Build the dashboard as a multi-column Notion page with styled headings, then use toggles to keep dense content collapsible.

  2. 2

    Use page links and “link to database” views so the dashboard stays synchronized with the underlying task and note systems.

  3. 3

    Create the task inbox by duplicating an already-configured inbox view (filters/sorts included) rather than rebuilding those rules from scratch.

  4. 4

    For the notes inbox, use a linked database and apply filters that account for web clipper behavior (status not empty OR url not empty).

  5. 5

    Wrap large inboxes in toggles and reduce initial load (e.g., 10 items) to keep the dashboard responsive.

  6. 6

    Add mobile navigation support with a quick links bar (toggle + table of contents link) so users can jump to sections quickly.

  7. 7

    Use third-party embeds like Indify for widgets (e.g., weather) to add real-time utility without cluttering the page with manual updates.

Highlights

The dashboard’s interactive inboxes work best when they’re built from linked views—so actions taken on the dashboard update the original task/note systems.
The task inbox is inserted by duplicating an existing filtered view from Ultimate Tasks, avoiding a tedious rebuild of filters and sorts.
A linked notes inbox needs special filters (status not empty and url not empty) to handle how the Notion web clipper behaves.
A “dummy view” workaround makes it possible to duplicate complex Notion views and then convert them to list format for better dashboard fit.
Indify weather is added via an embed, producing a compact widget that can be sized to match the dashboard columns.

Topics

  • Notion Personal Dashboard
  • Linked Databases
  • Ultimate Tasks
  • Note-Taking Inbox
  • Indify Weather Widget