How to Set Up Notion Dashboard Views

Notion dashboard views turn any database into an at-a-glance reporting surface. Instead of toggling between table, board, and calendar views one at a time, you arrange them side by side in a single layout with shared filters. Here is how to set one up from scratch, configure it for a real workflow, and keep it running smoothly as your data grows.

What Dashboard Views Actually Do

A dashboard view is a container that holds up to 12 widgets. Each widget is a database view: a table, board, calendar, timeline, list, or chart. You can pull views from the same database or from different databases entirely, which means a single dashboard can combine project tasks, client records, and revenue figures in one place.

The key feature is global filtering. When you set a global filter on a dashboard, it applies across every widget whose underlying view contains that property. Filter by "Q2 2026" once, and every chart, table, and board updates simultaneously. No more clicking into each view to set the same date range five times.

Prerequisites

Dashboard views require a Notion Business or Enterprise plan. If you are on the Free or Plus tier, you will not see the dashboard option in the view picker. You also need at least one database in your workspace, though dashboards become most useful when you have two or more databases tracking related information.

Step 1: Create the Dashboard View

Open any full-page or inline database. Click the + Add a new view button in the view switcher at the top. Select Dashboard from the list. Notion drops you into Edit mode immediately.

Alternatively, type /dash anywhere on a page to insert a new dashboard view inline. This is faster when you want a dashboard embedded inside a project brief or team wiki page rather than as a standalone database view.

Step 2: Add Widgets

Click the + icon on any row or at the bottom of the dashboard to add a widget. You have two options: pick an existing view from the current database, or create a new view from scratch. Each widget inherits all the filters, sorts, groups, and visualization settings from its underlying view.

A practical starting layout for a project tracker dashboard looks like this. Row one: a bar chart showing tasks by status and a donut chart showing tasks by assignee. Row two: a board view filtered to "In Progress" items only and a timeline view showing the current sprint. Row three: a table view filtered to overdue tasks sorted by due date.

You can add widgets from other databases too. Click +, then select From another database to pull in views from your CRM, content calendar, or finance tracker. This cross-database capability is what makes dashboards significantly more useful than stacked inline views.

Step 3: Arrange the Layout

Drag widgets horizontally to place them side by side. Notion allows up to four widgets per row, though two or three per row generally reads better. Hover between two widgets to reveal the resize handle, then drag left or right to adjust relative widths.

For row height, hover over the boundary between two rows and drag the divider up or down. A useful technique for table widgets: set the row height so only four or five rows are visible. The data is still there and scrollable, but the dashboard stays compact and scannable.

Give board and timeline widgets more horizontal space than chart widgets. Boards with many columns get cramped at narrow widths, while a simple bar chart reads fine at one-third width.

Step 4: Configure Global Filters

Click the filter icon at the top of the dashboard. Select Filter multiple sources to create a global filter. Choose a property that exists across the views you want to filter, such as a date property, status, or person property.

Global filters work best for criteria that users change frequently: date ranges, team member, project phase. Keep complex AND/OR filter logic inside the individual view filters rather than at the dashboard level, since dashboard-level filters do not support compound conditions yet.

One practical pattern: set a global date filter defaulting to "This week" and a global person filter defaulting to "Me." Team members open the dashboard and immediately see their own tasks, deadlines, and metrics without touching any settings.

Step 5: Lock and Share

Click Done to exit Edit mode and lock the layout. In View mode, users can still interact with global filters and click into individual widgets, but they cannot accidentally drag or resize anything.

Dashboard permissions follow the underlying database permissions. If someone has read access to the database, they can view the dashboard. If they have edit access, they can enter Edit mode and rearrange widgets. For executive dashboards where layout consistency matters, consider sharing the database with "Can view" permissions for most team members.

Performance Optimization

Dashboards can slow down noticeably when widgets load large unfiltered datasets. Three rules keep them fast.

First, filter aggressively inside each widget. A table showing all 2,000 tasks will load slower than one filtered to "This sprint" showing 30 tasks. Second, prefer chart widgets over table widgets for summary data. A bar chart summarizing 500 records renders faster than a table displaying all 500 rows. Third, keep the total widget count reasonable. The 12-widget maximum exists for performance reasons, but even 8 or 9 densely populated widgets can feel sluggish on slower connections.

Known Limitations

Dashboard views do not support text blocks, callouts, or any content between widgets. Every element must be a database view widget. If you need explanatory context alongside your dashboard, use the hybrid approach: embed the dashboard view inside a page that also contains headings, callouts, and toggle blocks around it.

There are no collapsible sections within a dashboard. All widgets display simultaneously, which means careful widget selection matters more than in a traditional page layout where you can hide sections behind toggles.

Global filters lack AND/OR grouping at the dashboard level. If you need "Status is Active AND Priority is High," you will need to set that as a filter inside the individual widget views rather than as a single dashboard-level filter.

Practical Templates

For a weekly team standup dashboard, use three widgets in one row: a board view grouped by assignee showing this week's tasks, a chart showing completed versus remaining items, and a table of blockers filtered by a "Blocked" status tag.

For a sales pipeline dashboard, combine a board view of deal stages, a bar chart of revenue by stage, a timeline of expected close dates, and a table of deals closing this month sorted by value. Add a global filter for deal owner so each rep sees their own pipeline.

For a content calendar dashboard, pair a calendar view of publish dates with a board of content status, a chart of posts by category, and a table of drafts needing review. Filter globally by content type or author.

When to Use Dashboard Views vs. Other Approaches

Dashboard views are strongest when you need cross-database visibility with shared filters and a fixed layout. They replace the common pattern of building a "dashboard page" by manually embedding six inline database views and hoping the page layout holds together.

For simple single-database reporting, a filtered table or board view is still faster to set up and easier to maintain. For truly custom visualizations or statistical analysis beyond what Notion's built-in charts offer, tools like VSLZ let you upload or connect data and generate charts and analysis from a single prompt without the widget-by-widget configuration.

Summary

Create a dashboard view from any database, add widgets pulling from one or multiple databases, arrange them in rows of up to four, set global filters for shared context, and lock the layout for your team. Keep widgets focused and filtered to avoid performance issues. Use the hybrid approach with surrounding page content when you need explanatory text alongside your data views.