Dashboards

Dashboards lets you compose a page of widgets that read across the whole workspace at once: tasks, projects, customer records, time and goals in one place, rather than four screens and a mental sum. Start from a template if you want a name and a purpose to work from, or start from nothing, and then add the widgets the question needs. Each widget runs its query through the shared query engine when the dashboard opens, so a dashboard is never a saved snapshot. You can keep several and switch between them, because the question a team lead asks on a Monday is not the question a project manager asks on a Thursday.

• Widgets that aggregate across tasks, projects, customer records, time and goals in one view
• Starter templates that fill in a name and a purpose, so the first dashboard is not a blank page
• Several dashboards, switchable, because different questions want different pages
• Each widget runs its query when you open the dashboard, so nothing here is a saved snapshot that goes stale
• A guided create flow rather than a prompt box, so a dashboard is named and shaped deliberately

• Dashboards are part of the analytics module. The whole route is gated on it, and nothing is fetched at all for a workspace without it.
• A widget shows what you are allowed to see. Two people on the same dashboard can legitimately see different numbers, because permissions apply to the underlying data.
• The screen can remove a widget, and it can delete the open dashboard after a confirmation. Either one leaves the tasks, projects and records the widgets were reading untouched.
• Widgets read data and never change it. Nothing you do here changes a task, a project or a record.
• The Atlas phone app lists your dashboards and shows each widget as a number, a short list of bars or a compact list of rows. It is read only, apart from deleting the dashboard after a confirmation. Building and editing widgets stays on the web.

1. 1Open Dashboards. If you have none, pick a starter template rather than an empty page.
2. 2Name the dashboard for the question it answers, not for the person who made it.
3. 3Add widgets for the numbers that question needs, across whichever modules hold them. Each widget is a metric, a chart or a table.
4. 4Switch between dashboards from the tabs at the top as the question changes.

Why can I not open Dashboards?

It is part of the analytics module. If your workspace does not have that module, the route is closed and nothing is loaded.

Why does my colleague see a different number?

Because a widget shows what the reader is allowed to see. The dashboard is shared; the data behind it still respects permissions.

Do I need to refresh a dashboard?

A dashboard runs each widget's query when you open it or switch to it, and it does not refresh on its own. Reload the page to read the latest data.

Does removing a widget delete anything else?

No. It removes the widget from the dashboard. Every task, project and record it was reading is untouched.