Workspace dashboard
All the sites of a workspace on one screen — availability and response time over seven days compared to the seven before, the month's incidents and deployments, and the list of what is degrading.
Pro plan and aboveUpdated on 17 September 2026
On this page
When you run several sites, the morning question is not “is everything fine?” but “which one should I look at first?”. The Dashboard (workspace menu → Dashboard) answers it for all the projects of the workspace at once.
What PostShip does
The workspace's figures
At the top: the availability of all sites over seven days — the share of successful passes —, the incidents of the last thirty days and how many are ongoing, the cumulated time spent in incident, the month's production deployments.
Thirty days of passes
One bar per day, all sites together: its height says how many passes were made, its colour the share of failures — green at zero, orange under 5%, red beyond. A month reads at a glance: the hard week stands out.
Look at first
The sites that deserve a look, in order: those with an ongoing incident, then those whose availability lost at least half a point compared to the previous seven days, then those whose median response time grew by at least a third. The list says why. It disappears when everything is fine.
Site by site
A table: availability over seven days and its trend, median response time and its trend, incidents and deployments over thirty days. A green arrow goes the right way, a red one the wrong way; a dash when nothing moved — or when there are not enough passes to tell (at least twenty on each side). Sites are ordered by urgency: ongoing incident, degradation, then increasing availability.
Settings
None: the dashboard is computed on opening, from what PostShip has already measured.
What triggers an alert
Nothing: alerts come from projects. The dashboard is the overview, not one more siren.
Limits and plans
| Free | Pro | Team | Agency | |
|---|---|---|---|---|
| Workspace dashboard | — | Yes | Yes | Yes |
See plans.
Troubleshooting
The trend says “—” although the site moved
At least twenty passes are needed on each of the two weeks to compare; a site checked every hour gets there in a day, a paused site never.
The median response time does not look like what I see
It is the median time to first byte, measured by the probe, over the successful passes of the last seven days: neither the full load, nor what your visitors measure (see Real experience).
A paused site still appears in the table
It keeps its past figures; its trends turn to “—” for lack of new passes. It carries the “paused” tag.