Dashboards & Insights
Dashboards built from the work itself.
Say what you want to see, and an agent writes the query and picks the chart. Tasks, tickets, and pull requests are already there to count, every refresh after that runs without AI, and the charts show up on Home, in Docs pages, in chats, and on each project.
Describe it
From a sentence to a chart that stays current
Open New insight and write what you want to see: open tickets per desk for the last quarter, tasks created per week, pull requests waiting for review. Create with AI opens the editor with Fill with AI already working. It reads the datasets you may use, writes the query, adds filters such as a date range or a project picker, runs a preview, and picks the chart. Nobody has to write SQL, and anyone who wants to can read the query, change it, or write their own.
The result is an insight: a saved question drawn as a bar, line, area, or pie chart, a number with its trend, a progress bar toward a goal, a leaderboard, a funnel, a heatmap, or a table. It runs on a read-only connection with no AI model involved, so a refresh costs nothing in AI usage and comes back in the same shape every time.
Charts open the work behind them: select a bar to see that task, ticket, or pull request, or the list filtered to it. When an agent draws a chart in a chat, Build an insight like this turns it into an insight that stays current. With the Insights Builder skill, your personal assistant builds insights, alert rules, and dashboards from your private chat, each change on an approval card.
Part of the workspace
Numbers where people already look
Insights do not live on a reporting site of their own. The same chart can sit on your Home, in a Docs page, in a chat, and on a project's Overview, showing its latest result to the people who may open it.
On your Home
Keep the insights you check every morning on Home, each with its latest chart and when it was updated. Select one to open it with fresh numbers.
Chart a list as it is filtered
Tasks, pull requests, and support queues have a Chart button that counts the list as you filtered it, by state, priority, assignee, repository, or client. Save as insight keeps it.
Inside Docs pages
Type / in a Docs page to place an insight or a whole dashboard. Readers see the latest chart, and one that has gone stale runs again as they open the page.
In chats, read by agents
Share an insight in a chat and everyone there sees its chart as a card. Agents read the insights shared with them and can explain what one shows.
On a project’s Overview
A project dashboard sits on the project’s Overview for everyone on the project, with its project filter already set. Start it from a template or from scratch.
Explain with AI
One click writes a few sentences about the latest result, compared with the run before it. Ask a follow-up, or carry on in a chat with your assistant.
Home and the rest of your day are on Personal Productivity. Charts that agents draw in their replies are on AI Agents.
Sources
Your workspace data first, then the systems around it
Most insights need nothing but the datasets Volobox already keeps. When the rows live somewhere else, an insight fetches them on every run and reads them like a table.
Built-in datasets
Tasks, milestones, projects, tickets, desks, pull requests, repositories, workflow runs, AI usage, people, and groups, ready to query by name.
Data connections
HTTP APIs an administrator adds, with notes for authors that Fill with AI reads when it writes the request. Each connection lists who may use it.
MCP servers
A tool on an MCP server you may use can feed an insight. Its answer becomes a table the query reads.
App datasets
A custom app’s Admin can share its records with Insights, so dashboards chart them next to the rest of your work.
Learn moreKeep watch
Alert rules that tell you when a number moves
Turn on Run in the background and an insight runs on a schedule whether or not anyone is looking: every few hours, every day at a set time, or on chosen weekdays. Those runs build a History trend, and a number can show how it changed against the previous period.
Add alert rules on top: a threshold, a change between runs, a run that returns nothing, or an anomaly far from the recent average. Each rule checks on its own schedule and can wait for a few breaches in a row before it fires.
A rule that fires raises an alert for you and can post to a chat, again when it resolves. Investigate asks your assistant what changed and what is behind it, and a workflow can start the moment an alert is raised.
Alerts
One place for what needs attention
An alert is a condition that holds right now. It has its own icon in the top bar and a Needs attention list on Home, apart from the bell and the Inbox, and it resolves by itself once the condition is gone.
Info, Warning, Critical
Info is listed, Warning counts in the top bar, and Critical plays a short sound and reaches your phone at once. Do Not Disturb holds them back.
Acknowledge or snooze
Acknowledge tells everyone the alert reaches that you are on it. Snooze is yours alone and changes nobody else’s view.
From across Volobox
Insight alert rules, usage limits, workflows, apps, a webhook Volobox turned off, a calendar to reconnect, a booking without a host. Administrators choose who gets each system alert and can post them to a channel.
Share and present
A dashboard for you, for a project, or for the screen on the wall
Arrange insights on a grid with headings and notes between them. Each reader keeps their own filters, and a dashboard brings its numbers up to date when it opens.
Personal and project dashboards
Share a personal dashboard with people and groups, who read it while only you change it. A project’s dashboard is read by everyone on the project and edited by its collaborators and managers.
Start from a template
Sprint health, Support desk, and My week come with their insights, ready to filter by project or date range.
Filters for each reader
One date range, project, or person filter drives every widget that uses it. Everyone keeps their own saved filters and Changed marks, and editors set the default.
Each viewer’s own result
An insight such as My open tasks runs for whoever opens it, so one dashboard shows each person their own work.
Present
Put a dashboard on a screen without menus or editing. It reads the latest numbers again every minute while it is on.
A summary in a chat
Post a dashboard’s summary to a chat every day or every week: the latest figures and how they moved since the last post, with a link back.
Who sees what
Read-only by design, governed like the rest of Volobox
Insights read the workspace without changing it, and each one has an owner who decides who may open it.
A read-only connection
Every query runs on a separate, read-only analytics connection and is checked before it saves. The built-in datasets hold ids, states, dates, counts, and names, never a task’s description, a message, a customer’s text, or a secret.
Permission and sharing
Insights is a permission, and making insights is a second one, for the people who may see workspace-wide figures. A widget shows only to readers who may open its insight, and readers who cannot make insights see each one only for its default project and the projects they can open.
Connection secrets out of reach
The token, key, or password a data connection signs in with is read from a secret on every run. It never reaches the person writing the insight or a model.
More on how Volobox keeps data and access in your hands on Trust.