> For the complete documentation index, see [llms.txt](https://docs.fullsession.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullsession.io/9.-dashboards.md).
# 9. Dashboards
Sessions, heatmaps, and funnels each answer a specific question. **Dashboards** bring the answers together — a customizable grid of **cards** (charts, metrics, and lists) that tells you how your product is doing at a glance. This chapter covers the prebuilt templates, building and configuring your own cards, scoping a dashboard with filters and segments, and getting data out.
***
### 9.1 Dashboards Overview
A **dashboard** is a page made of **cards** arranged on a grid. Each card visualizes one piece of your data — a metric, a trend, a breakdown, a list of sessions — and together they give you a tailored picture.
#### The dashboard list
Your dashboards are listed with their **name, owner, and visibility** (private or team). From here you can open, edit, archive, or delete them, and **set one as your default** so it opens automatically for you (you can have one default per site).
#### Cards and the card library
Cards aren't locked to a single dashboard. When you build a card it's stored in your **card library**, and the same card can be added to **multiple dashboards**. A card's visibility can be **personal** (only you) or **team** (everyone), just like dashboards themselves.
#### Refreshing
Dashboards don't auto-refresh in real time. Use **Refresh All** to reload every card, or refresh an individual card from its menu. (There is no live/auto-updating mode.)
#### Drilling from dashboard to detail
Dashboards are a starting point, not a dead end. **Table-based cards** (Breakdown and Pages) let you click a row to **Add to Filter** or **View Sessions** — jumping from a summary number into the real recordings behind it (section 9.7).
> **Note** — clicking an individual *point* on a line or bar chart does **not** drill in. Drill-in actions are available on **table rows** (Breakdown and Pages cards).
***
### 9.2 Prebuilt Templates
You don't have to start from a blank page. FullSession ships with **five role-based dashboard templates**, each pre-built with relevant cards. Pick the one that matches your role and you'll have a useful dashboard in seconds.
#### The available templates
| Template | Built for |
| -------------------------- | ----------------------------------------- |
| **Growth / CRO / RevOps** | Conversion, growth, and revenue teams |
| **Product Management** | Product teams tracking usage and adoption |
| **Engineering / QA / SRE** | Developers, QA, and reliability engineers |
| **Executive Overview** | Leadership wanting high-level KPIs |
| **CS / Digital Ops** | Customer success and digital operations |
#### Using a template
Creating from a template requires the **create dashboards** permission. Click a template card and FullSession creates a **new dashboard pre-filled with that template's cards**, populated with your live data. From there you can freely add, remove, rearrange, and reconfigure cards (sections 9.4–9.6) — the template is just a fast starting point.
> **Tip** — start from the template closest to your role, then trim and tweak. It's almost always faster than building from blank.
***
### 9.3 Creating & Managing Dashboards
#### Creating a dashboard
1. Click **Add Dashboard**.
2. Fill in:
* **Name** *(required, up to 100 characters)*.
* **Description** *(optional, up to 240 characters)*.
* **Private** — check *"Private (visible only to you)"* to keep it to yourself, or leave it unchecked to make it visible to your whole team.
3. Create the dashboard — it opens ready for you to add cards.
#### Editing, archiving, and deleting
| Action | What it does |
| ------------------ | ---------------------------------------------------------------------------------------- |
| **Edit** | Change the name, description, or visibility |
| **Set as default** | Make this the dashboard that opens first for you (one default per site) |
| **Archive** | Hide the dashboard from the main list without deleting it; an admin can restore it later |
| **Delete** | Permanently remove the dashboard (with a confirmation prompt) |
These actions are governed by permissions — editing requires the **edit** permission, deleting requires the **delete** permission (section 9.8).
> **No "duplicate dashboard."** FullSession doesn't copy a whole dashboard in one click. Because **cards are reusable across dashboards** (section 9.1), the practical approach is to create a new dashboard and add the existing cards you want to it. (Archiving, not duplication, is how you set a dashboard aside.)
***
### 9.4 Cards: Adding & Arranging
Dashboards are built on a **drag-and-drop grid**, so composing one is fast and visual.
#### Adding cards
1. Click **Add charts**.
2. Choose from the **card library** — your existing cards plus any available template cards — or build a new card (section 9.5).
3. The card is placed on the grid, populated with live data.
#### Arranging the grid
The grid is fully malleable:
* **Drag** a card to move it.
* **Resize** by dragging its edges — make key cards larger, supporting ones smaller.
* **Remove** a card from the dashboard via its menu (with confirmation).
* **Enlarge** any card to a full-screen view for a closer look.
Layout changes are saved automatically.
#### Layout best practices
* **Most important, top-left** — put the headline metric where the eye lands first.
* **Group related cards** — keep error cards together, funnel cards together.
* **Size by importance** — give a critical KPI a larger tile.
* **Don't overcrowd** — if it feels cramped, split into a second dashboard.
***
### 9.5 Card Types
FullSession offers a focused set of card types, each suited to a different question.
| Card type | Shows | Typical use |
| ---------------- | ------------------------------------------------------------------- | -------------------------------------- |
| **Metric** | A single KPI value, optionally compared to the previous period | "Total sessions, +12% vs. last period" |
| **Time Series** | A metric over time | Spotting trends and spikes |
| **Breakdown** | A metric distributed across a category, as a **bar chart or table** | Sessions by device, country, browser |
| **Pages** | Top pages by views or load time, with a link to the heatmap | Finding your busiest or slowest pages |
| **Sessions** | A browsable, replayable list of sessions matching filters | Jumping straight into recordings |
| **Feedback** | Feedback sentiment over time | Tracking CSAT and survey responses |
| **User Journey** | How visitors flow through pages, as a **Sankey** diagram | Understanding common paths |
| **Label** | A text block | Headings and notes on the dashboard |
> **Visualizations are line, area, column, bar, and spline** (powered by Highcharts). There are **no pie/donut charts** and **no goal/gauge** cards — comparisons are expressed through the Metric card's previous-period option and through breakdowns.
Templates may also include specialized widgets such as **funnel** cards, **sessions-review** tiles (Worth Watching / Recent / Flagged), and small **trend sparklines** (Sessions, Friction Rate, Feedback, Errors). The eight types above are the ones you build directly in the card builder.
***
### 9.6 Configuring a Card
When you create or edit a card, the **card builder** lets you define exactly what it measures and how it looks, with a **live preview** that updates as you go.
#### Choose a measure
Pick what the card counts. Available measures include:
| Group | Measures |
| -------------------- | ----------------------------------------------------------------- |
| **Volume** | Total Sessions, Total Events, Unique Users, Identified, Anonymous |
| **Engagement** | Active Time, Duration, Pages Viewed |
| **Interaction** | Clicks, Rage Clicks, Dead Clicks, Error Clicks |
| **Errors** | Error Sessions, Response Errors |
| **Forms & Feedback** | Abandoned Forms, Total Feedbacks, Answered Feedbacks |
#### Choose an aggregation
For numeric measures, pick how values are combined: **sum, average, median, min, or max**.
#### Group by (breakdown)
Break a metric down by a dimension, such as:
**device, browser, operating system, country / region / city, landing page, exit page, referrer, page, user ID, screen size**, error categories (error logs, uncaught exceptions, unhandled rejections, response errors), or click **text / selector**.
#### Time interval (Time Series)
For time-series cards, choose the bucket: **hour, day, week, or month**.
#### Series & comparison
* A card can have **up to five series**, so you can compare multiple filtered slices on one chart (e.g. mobile vs. desktop sessions).
* The **Metric** card can show **one to four measures** at once, and can display a **previous-period comparison** so a number arrives with context ("+12%").
#### Per-card options
Some card types have their own settings:
| Card | Options |
| ---------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Pages** | Page type (visited / landing / exit), order by most-viewed or slowest, and show percent / views / heatmap columns |
| **Breakdown** | Bar or table shape, show percentage, show heatmap, and group everything beyond the top 5 as "Others" |
| **Sessions** | Show a live **sessions** list or only **pinned** (flagged) sessions |
| **Feedback** | Overview or trends, optionally scoped to a single feedback form |
| **User Journey** | Max steps and top nodes per step |
> **Tip** — build the card, watch the **live preview**, and confirm the number looks right before saving. If it's off, your measure, aggregation, or filter is usually the cause.
***
### 9.7 Filters, Segments & Drill-in
#### Scoping a dashboard
Rather than a single global date picker, dashboards use a **shared filter/segment bar** that applies across all cards. You can:
* Apply **filters** to the whole dashboard, or
* **Connect the dashboard to a Segment**, so that segment's definition scopes every card on the page.
When a segment is connected, all cards reflect that audience — for example, a dashboard connected to a "Mobile Users" segment shows every card for mobile visitors only. Build the segment once (\[Chapter 11 — Segments]) and the whole dashboard inherits it.
> Date scoping is handled through the filter/segment bar rather than a dedicated dashboard-level date field.
#### Drilling into sessions
The **Breakdown** and **Pages** cards are tables, and each row offers two actions:
| Action | What it does |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| **Add to Filter** | Adds that row's value (e.g. a country or page URL) to the dashboard's filters, narrowing every card |
| **View Sessions** | Opens the sessions that match that row, so you can watch the real recordings behind the number |
This is what keeps a FullSession dashboard from being a static report: a surprising number in a table is always one click away from the sessions that explain it.
***
### 9.8 Export, Sharing & Permissions
#### Exporting a card to CSV
Each card (except the Label card) has a **download** action that exports its data as a **CSV**, named after the card. Exports are capped at **10,000 rows** — narrow your filters or date range for a focused set.
> CSV is the only export format — there is **no PDF, image, or scheduled email-report** export. The CSV contains the card's underlying data, not the visualization.
#### Sharing: private vs. team
Dashboard (and card) visibility is a simple, two-level choice:
| Visibility | Who sees it |
| ----------- | -------------------- |
| **Private** | Only you |
| **Team** | Everyone on the site |
A team dashboard means everyone works from the **same view of the truth**. (There is no finer-grained "share with specific people or roles" — visibility is private or team.)
#### Permissions
What each teammate can do with dashboards is governed by permission keys assigned to their role (\[Chapter 16 — Team & Account Management]):
| Permission | Allows |
| --------------------- | ---------------------------------------- |
| **Create dashboards** | Add dashboards and use templates |
| **Edit dashboards** | Change name, description, and visibility |
| **Delete dashboards** | Remove dashboards |
| **Create charts** | Add and build cards |
If you don't see an action described here, your role may not include the corresponding permission.
> **The big picture** — start from one of the **five role-based templates** or a blank dashboard; build cards (Metric, Time Series, Breakdown, Pages, Sessions, Feedback, User Journey) in a live-preview **card builder** with rich measures, aggregations, and breakdowns; arrange them on a drag-and-drop grid; scope the whole dashboard with **filters or a connected segment**; drill from **table rows** into real sessions; export cards to **CSV**; and share **private or team-wide**. There's no dashboard duplication, no pie charts, no chart-point drill-down, and no scheduled reports.
***
> **Next up:** \[Chapter 10 — Insights & Cards] goes deeper into the individual cards — the measures, breakdowns, and comparisons that make each one — and how to read the page and engagement statistics FullSession computes automatically.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.fullsession.io/9.-dashboards.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.