Dashboard

Every level of your workspace — your User Space, and each Organization, Group, and Project — has its own dashboard: the page you land on when you open it. A dashboard is built from widgets that give an at-a-glance view of that level’s resources.

Widgets are configurable. Anyone with admin access to a level can add, edit, reorder, and remove its widgets; everyone else with access sees the same layout. Changes appear for all viewers live, without a refresh.

Widget types

Type	Shows
Table	The top rows of a resource matching a search — e.g. the 10 most recent failed tasks
Count	A live count of a resource matching a search — e.g. how many task templates have errors

Both widget types support these resources: Tasks, Task Templates, Schemas, Services, and Automations.

Every widget links through to the matching list view with its search already applied, so a widget doubles as a saved shortcut into a filtered list.

Configuring widgets

In edit mode, each widget has a few settings:

• Title — the heading shown on the widget.
• Search — a query in the same syntax as the resource’s list view. This is what the widget lists or counts; an empty search matches everything.
• Sort (table widgets) — which field to sort by, and the direction.
• Rows (table widgets) — how many rows to show: 5, 10, or 15.
• Size — how wide the widget is in the grid: Small, Medium, or Wide.

Reorder widgets by dragging them in edit mode. The dashboard lays widgets out in a flow grid that wraps to fit the available width.

Note

Widget searches can go stale — for example, if a label or template referenced by the search is later deleted. A stale widget simply shows nothing rather than erroring.

What each viewer sees

• Configuring widgets requires admin access to the level. Members without admin access see the dashboard but cannot change it.
• Widget contents always run as the viewer. A widget describes what to show, but each person only sees data for resources they are allowed to read. If you lack access to a resource, its widget appears empty for you — even though a teammate with access sees it populated.

Empty dashboards

A new level starts with no widgets — nothing is seeded by default. Admins see a placeholder prompting them to add the first widget; everyone else sees an empty dashboard until an admin configures it.