How to Use Notion's NEW Dashboard View | Full Guide & Tutorial

Notion’s new Dashboard View lets business and enterprise users build a single, widget-style dashboard that pulls from multiple databases—tasks, projects, and more—while supporting charts, lists, calendars, and other view types. The practical payoff is a cleaner way to surface key work signals in one place, without the clutter that often comes from stacking many inline databases and linked views.

Getting started requires having at least one database ready (for example, a task database and a project database). From there, users type “/dashboard view,” create a new view, and then add widgets by selecting existing database views. Each widget can be tailored: a task widget can show “high priority but not done” items, and additional widgets can be added with the “plus” control. Notion’s dashboard widgets aren’t limited to tables—users can choose from list, gallery, feed, calendar, map, and chart-based presentations, depending on what best communicates the information.

A standout capability is a new chart “number” type, designed to display a single value at the top of a dashboard section. Instead of relying on donut charts for quick totals, users can show a plain number—such as “2 tasks due today and not done”—by filtering the underlying data (e.g., due date equals today, status is not done). Chart titles can be edited or removed, and visual styling like color can be adjusted. Widgets can also be duplicated and reconfigured, such as pairing a number widget with a list widget that shows the specific incomplete tasks due today.

Dashboards also support multiple data sources. Users can add additional widgets from other databases—such as a projects database—then choose different views for each source (timeline by status, or a filtered view like “all projects not complete”). Layout is customizable through drag-and-drop positioning, along with control over widget dimensions (width and height). Once arranged, dashboards can be made more stable for team use by locking views so accidental edits don’t happen.

Two higher-level controls make multi-database dashboards feel cohesive. First, dashboard settings let users show or hide data source titles and icons, and manage which data sources appear. Second, global filters can apply across multiple sources using shared properties like due dates. For example, a single filter can limit both project timelines and task due dates to “this week” or “this month.” Filters can also be layered by owner, producing a dashboard that changes based on who is selected—showing tasks and projects for Alex, then switching to Sam or Taylor.

There are constraints: dashboards cap at 12 widgets total and no more than four widgets per row, and the feature is limited to business and enterprise plans. Performance can degrade if filters aren’t tight or if too many dashboards exist on one page. The recommended approach is to avoid dumping entire databases into dashboards; instead, filter to the most relevant slices (like “high priority” and “not done”) and lean on charts effectively.