Work

Dashboards, insights and alerts

Chart your own work in Volobox: insights answer a question about workspace data, dashboards collect them, and alerts say when to look.

Dashboards and insights answer the questions a team keeps asking about its own work: open tasks by state, tickets per desk, pull requests waiting, AI cost per day. They live inside the workspace, next to the work they measure. Alerts are the other half: conditions that hold right now and that someone should look at.

A dashboard: figures with their trend, a stacked bar chart of tasks closed per week, a pie chart of open tasks by area, an area chart of open requests and a leaderboard.

Insights

An insight is a saved question about your data: one SQL query and a chart that draws the result. Charts include bar, line, area, pie, number, number with trend, progress, status bar, leaderboard, funnel, heatmap and table.

An insight runs on a separate read-only analytics connection, without an AI model, so a refresh spends no AI and always returns the same shape.

Nobody has to write SQL. Create with AI takes a description in your own words, writes the query and any filters (such as a project picker), runs a preview and picks the chart. You can also write the query yourself, or start from a template.

Explain with AI describes the latest result in a few sentences. It is the only part of reading an insight that uses a model.

Sources

  • Built-in datasets: tasks, projects, milestones, tickets, pull requests, repositories, workflow runs, AI usage, meetings, people and groups, among others.
  • Data connections: HTTP APIs an administrator sets up.
  • MCP servers you may use.
  • App datasets: records an app's Admin shares with Insights. See Apps.

The built-in datasets hold ids, states, dates, counts and names. They never hold a task's description, a message, a customer's text, an email or a secret.

Note

Making insights is a separate permission, because its holder reads every row of the built-in datasets.

Dashboards

A dashboard is a grid of insights with headings and notes between them.

  • A personal dashboard can be shared read-only with people and groups.
  • A project dashboard appears on the project's Overview for everyone on the project.
  • Templates such as Sprint health, Support desk and My week give a starting set.

Each reader keeps their own filters. Present fills a screen with the dashboard, and a chat digest posts a daily or weekly summary of its figures to a chat.

Where insights appear

Beyond dashboards, you can:

  • keep insights on Home
  • chart a filtered task, ticket or pull request list with its Chart button, and save it as an insight
  • place an insight or a dashboard in a Docs page
  • reference an insight in a chat so others see its chart

A card shows its chart only to readers who may open the insight.

Refresh and alert rules

Opening an insight always shows a recent result. An insight can also Run in the background on a schedule, which builds a history trend.

An alert rule watches an insight for you. It fires on a value above or below a line, a rise or drop since the previous check, a result that comes back empty, or a value that is unusual compared with recent checks. It is checked on its own schedule, and its Urgency sets the alert's severity.

A rule that cannot check says so instead of looking healthy.

Alerts

An alert is raised by its source, kept up to date while the condition lasts, and resolved by itself when the condition clears.

It is not a notification and not an Inbox card. It has its own icon in the top bar, Needs attention on Home, and an Alerts page. You see only the alerts addressed to you.

  • Severity: Info is listed only, Warning is counted in the top bar, and Critical also plays a short sound and notifies your phone.
  • Acknowledge tells everyone the alert reaches that you are on it.
  • Snooze quiets it for you alone, for a time you pick.
  • Investigate asks the assistant what changed behind an insight alert.

Sources include insight alert rules, usage limits, workflows, apps, webhooks, calendar connections, booking pages and shared mailboxes. Administrators choose who gets each of Volobox's own sources, and can post most of them to a group or project channel. A workflow can start when an alert is raised, escalated, acknowledged or resolved.

The Alerts page: active alerts from a workflow, an insight alert rule, a webhook and an agent, each with its severity, Acknowledge and Snooze.