How to Set Up Notion Dashboard Views

Notion Dashboard Views turn any existing Notion database into a visual reporting layer without leaving your workspace. You pick a database, add a Dashboard view, then choose which properties to chart as bar graphs, pie charts, or KPI cards. Notion AI can suggest the right chart types based on your property names and data types. The dashboard updates live as records change, with no export step or separate BI tool required. Most setups take under 15 minutes.

What Notion Dashboard Views Can Do

Dashboard Views shipped on March 10, 2026, as a new view type for all Notion databases. Instead of displaying records as table rows, board cards, or calendar events, the Dashboard view renders your database properties as charts and metric tiles on a free-form canvas.

Each element on the canvas is called a widget. Each widget is tied to one or more properties in your database. Available widget types include bar charts (grouped or stacked) for comparing counts across categories, pie and donut charts for understanding proportions, KPI cards that show a count, sum, or average from a numeric property, and progress bars for tracking completion percentages.

All widgets respond to the dashboard's active filters. If you filter the dashboard to a specific assignee or date range, every chart on the page updates to match. Multiple dashboard views can live on the same database, so different stakeholders can each have a layout tuned to what they need.

Before You Start: What You Need

Dashboard Views require a Notion workspace on the Plus, Business, or Enterprise plan. Free plan users can view dashboards shared with them but cannot create new ones.

You also need a database with structured properties. A database full of free-form text notes will not chart well. The most useful source databases have a Status or Stage property with defined options, one or more Select or Multi-select fields for categories, and at least one numeric property such as budget, deal value, or story points if you want sum or average widgets.

Project trackers, CRM databases, sprint boards, and content calendars all work well. Before building the dashboard, review your database and add any missing Select or numeric properties you want to track. A clean schema makes the dashboard more useful and makes Notion AI suggestions more accurate.

Step 1: Add a Dashboard View to Your Database

Open any full-page database in Notion. Click the Add a view button near the top-left of the database header. In the view selector panel, scroll past Table, Board, and Calendar to find Dashboard. Click it, give the view a descriptive name such as "Sprint Overview" or "Sales Pipeline," and click Done.

The dashboard canvas opens blank. No widgets are present yet. The canvas shows an Add widget prompt in the center and an Add widget button in the top-right corner.

Step 2: Add Widgets

Click the Add widget button. A side panel opens listing the available widget types.

A practical starting point for any ops database is a bar chart by Status. Select Bar chart, set the property to Status, and set the metric to Count of entries. Save it. The bar chart appears on the canvas showing how many records fall into each status bucket.

Common widget sets by use case:

For a project tracker: a KPI card showing the total count of open items, a bar chart of tasks by assignee showing workload distribution, and a pie chart of items by priority showing how much is high-priority versus low.

For a CRM database: a bar chart of deals by pipeline stage, a KPI card showing the sum of all deal values as total pipeline, and a second KPI card filtered to Stage equals Closed Won showing revenue closed this period.

For a content calendar: a bar chart of pieces by status (Draft, Review, Published), a KPI card counting pieces published in the current month, and a grouped bar chart breaking output down by content type or channel.

Aim for three to seven widgets per dashboard. More than that starts to resemble a dense spreadsheet rather than a glanceable overview.

Step 3: Arrange the Layout

Widgets can be dragged by their header bar and dropped anywhere on the canvas. Resize a widget by dragging its lower-right corner. Notion snaps widgets to an internal 12-column grid, so elements align automatically without manual pixel adjustment.

A layout that reads cleanly puts KPI cards in a compact strip across the top row as a summary, then larger bar and pie charts fill the rows below. Reserve wider widgets for charts with many categories that benefit from horizontal space. Taller widgets work well for pie charts and progress bars.

Notion saves dashboard view configurations automatically when you navigate away.

Step 4: Use Notion AI to Suggest Charts

If you are not sure which widgets to add, Notion AI can analyze your database properties and recommend a starter layout. Open the empty dashboard, click Ask AI, and type a prompt such as "suggest charts for my project tracker" or "what should I track for a sales pipeline database."

Notion AI reads your property names, types, and sample values, then generates three to five widget recommendations. Numeric properties get sum or average KPI suggestions. Select and Status properties get bar or pie chart suggestions. Date properties can generate count-by-week or count-by-month bar charts.

Accept suggestions one by one to preview each, or accept all at once and adjust afterward. Each suggested widget is fully editable after it appears on the canvas.

As of April 2026, AI chart suggestions are available on workspaces with Notion AI enabled. Notion AI is included on Business and Enterprise plans and available as a monthly add-on for Plus workspaces.

Filtering and Multiple Dashboard Views

Dashboards inherit the filter and sort controls from the database. Adding a filter to a dashboard view scopes all widgets to only the records that match the filter criteria.

This means one database can support multiple reporting audiences from the same data. Create one dashboard view filtered to Team equals Engineering, a second filtered to Team equals Sales, and a third unfiltered for leadership. Each view shows the same underlying records, sliced for a specific audience.

Filters can reference relative date ranges. A filter where Due Date is within the current week scopes the entire dashboard to active work, which is useful for standups and weekly check-ins. A filter for Created Date within the last 30 days turns the dashboard into a rolling-window activity report.

What Dashboard Views Do Not Support

Dashboard Views pull from a single database. They cannot aggregate data across multiple separate Notion databases. If your work data is spread across five different databases, a unified dashboard is not possible without consolidating the data first.

There is no scheduled auto-refresh on a timer. The dashboard updates when the underlying records change or when the page is reloaded. It is live but passive.

Calculated cross-property metrics such as conversion rate from Stage A to Stage B are not supported as widget calculations. Those derived metrics need to be built as formula properties inside the database first, and then a KPI widget can reference the formula property.

If you are working with external data from spreadsheets or CSV exports that need cleaning and analysis before they land in Notion, VSLZ lets you upload a file and ask for aggregated summaries in plain English, which you can then add as structured properties in your Notion database for charting.

Practical Tips for Getting More Out of Dashboards

Use linked databases if you want a dashboard visible from multiple places. A linked database view can live on a project page, a team home page, and a leadership page simultaneously, all pulling from one source database.

For recurring reporting, pin the dashboard view as the default view on your database. Anyone who opens the database will land on the dashboard first rather than the table.

Consider naming your dashboard views by audience rather than by content. "Engineering View" and "Executive View" communicate purpose more clearly to collaborators than "Dashboard 1" and "Dashboard 2."

If your database has dozens of properties, start with the three or four that matter most for decision-making. A focused dashboard with five widgets that everyone checks beats a comprehensive dashboard with fifteen widgets that nobody reads.

Summary

Notion Dashboard Views give ops teams and founders a native, no-code reporting layer inside the tool they already use for tracking work. The setup is: add the view, pick widgets, arrange the layout, and optionally let Notion AI suggest a starter configuration from your existing properties. For routine status reporting, project health checks, and pipeline reviews, this removes the need to export data to a separate BI tool.

The real value comes from building multiple filtered views from a single database. One source of truth, multiple audiences, no manual data duplication or tab-switching required.