Dashboards View
Dashboard views convert a database into an at-a-glance command center by arranging multiple widgets — tables, boards, calendars, charts, and timelines — into a single organized layout. Instead of switching between separate views or different databases to get the full picture, a dashboard brings everything together in one place.
They're ideal for:
- Team status reports
- Ticket and incident overviews
- Sales pipeline summaries
- Content and campaign performance tracking
Create a Dashboard View
From an Existing Database
- Open any database (full-page or inline)
- Click
+to add a new view - Select Dashboard
You're placed directly into Edit mode so you can start building immediately.
Via Slash Command
Type /dash on any page, select Dashboard view from the menu, name it, and begin editing.
With Closot AI
Ask Closot AI to generate an initial dashboard draft — for example: "Create a dashboard for my @ Tasks database showing key metrics." Switch to Edit mode afterward to refine the layout, adjust row heights, and fine-tune individual widget views.
Building Your Dashboard
Adding Widgets
Each widget displays one specific database view. To add one:
- Enter Edit mode
- Click the
+icon on any row or at the bottom of the dashboard - Select an existing view or create a new one for that widget
Limits: A dashboard supports up to 4 widgets per row and 12 widgets total.
Managing Widgets
Right-click any widget (or click its title) to access:
- Duplicate — creates a copy with identical settings
- Delete — removes the widget from the dashboard
Arranging Widgets
Drag any widget to reposition it within or between rows. If drag-and-drop isn't available in your setup, use the move options available through the widget's actions menu.
Resizing Widgets
- Width: Hover between two widgets and drag the divider handle left or right
- Height: Hover over the boundary between rows and drag the divider up or down
Customizing Widget Content
From each widget's view options, you can adjust:
- Filters (e.g., "Status = Open")
- Sorts (e.g., newest first)
- Groups (e.g., by assignee or priority)
- Visualization type (list, board, chart, etc.)
Filters and sorts applied while in View mode are not saved by default. To make them permanent for all viewers, select Save for everybody — requires edit permissions on the database.
Global Filters
Apply a filter across multiple widgets simultaneously instead of configuring each widget individually:
- Click the filter icon at the top of the dashboard
- Select Filter multiple sources
- Choose a property and define the filter criteria
How global filters work:
- A global filter only affects widgets whose underlying views contain the filtered property
- Multiple global filters can be active at once, each targeting different properties
- They work across widgets pulling from different data sources, as long as those sources share the relevant property
View Mode vs. Edit Mode
| Mode | Purpose |
|---|---|
| View mode | For consuming the dashboard — open pages, use visible filters, interact with items based on your permissions |
| Edit mode | For designing the layout — add, remove, and rearrange widgets; adjust row heights; swap the displayed database views |
Editing Widgets vs. Editing Views
There are two distinct types of edits you can make:
Edit widget layout — move a widget to a different row, resize its height, or remove it from the dashboard entirely. These changes affect only this dashboard.
Edit the widget's database view — update filters, sorts, groups, or visualization type through view options. Depending on workspace settings, these changes may also appear wherever else that view is used.
Permissions
Dashboard views follow the same permission model as the underlying database:
- Edit access — can create dashboards, modify layout, and configure widget views
- View access — can open dashboards in View mode and interact with content based on permissions
Edit access to the database is required to change the dashboard layout.
Performance
Dashboards with many widgets or large unfiltered views can load slowly. Keep things responsive by:
- Keeping each widget focused — don't load more data than is needed
- Using filters to limit what each widget fetches (e.g., "Created this week," "Status is not Done")
- Avoiding large, unfiltered table widgets — use charts or grouped views to summarize instead
- Not placing multiple dashboard views on the same page
Dashboards vs. Inline Views in Columns
| Use a Dashboard view when | Use inline database views in columns when |
|---|---|
| You want a stable, app-like surface that's hard to accidentally change | You want a freeform page mixing databases with rich text, images, and callouts |
| You want a clear split between design time and daily use | You want to experiment quickly without creating a reusable view |
| You want clean row alignment where widths resize together | You want highly customized layouts that vary page to page |
Layout Patterns
Team Status Hub
- Row 1: Chart of pipeline by stage or total ARR by segment
- Row 2: Table of top priority projects + Table of risks and blocked items
- Row 3: Timeline of key milestones
Incident or Ticket Overview
- Row 1: Chart of open tickets by severity + Chart of tickets by channel
- Row 2: Table of unassigned tickets + Table of tickets breaching SLA
- Row 3: Timeline of tickets by created date
Executive Reporting
- Row 1: Chart of pipeline by stage or total ARR by segment
- Row 2: Table of top priority projects + Table of risks and blocked items
- Row 3: Timeline of key milestones