Skip to content

Dashboard

The dashboard (/dashboard) is where you land after logging in. Its main part is Needs attention: everything across your clients that wants a person, most urgent first, each with a way to fix it. Beside it are your fleet totals and recent activity.

If your role is scoped to specific clients (see client scoping), everything on the dashboard, the counts and the alerts, reflects only the clients you can see.

Fleet totals

A small panel beside the list with four counts for the tenant (or your client scope): Clients, Endpoints, Printers and Queues. Clients and Queues link to their lists.

Setup

Until your workspace is set up, a Set up ZenPrint checklist sits at the top of the dashboard. Each step ticks itself off when ZenPrint sees it done:

  1. Create an API key
  2. Add the bootstrap script to your RMM and run it on one device
  3. Map your RMM’s groups to clients and locations (only if your RMM reports groups rather than sites)
  4. First client and location appear
  5. A scan finds the first printer
  6. Create the first queue

Each open step links to where you do it. Once you have an API key, the bootstrap step waits for the first device to check in and ticks off on its own while the page is open, so you can run the script from your RMM and watch it land. Close the checklist with × and it stays hidden for you (other admins still see it); it’s still under Settings → Getting started. Once every step is done, both disappear. If a step later becomes open again (for example every API key is revoked), the Settings tab comes back. The checklist shows for admins who can open the scripts and aren’t limited to specific clients. See Getting Started for the full walkthrough.

Bootstrap update banner

An amber banner appears when your endpoints are reporting a bootstrap version older than the minimum the server now expects. It names the reported version and the required one. The fix is to re-download the bootstrap from Settings → Scripts and replace the script in your RMM; the banner clears as soon as any endpoint reports the new version. The banner is informational, and your current bootstrap keeps working until you update. See Bootstrap Script for the upgrade flow.

Billing banner

Two billing states surface as a dashboard banner. An amber banner appears when your trial ends within the next 7 days (or has just ended); after the end date your workspace moves to the Free plan automatically. A red banner appears when you manage more printers than your plan includes; new printers cannot be brought under management until you dismiss or decommission printers you no longer manage, or upgrade. Existing printers keep working either way. When neither applies, no banner renders. Your plan and its printer count also show under Settings → Workspace.

Needs attention

Grouped in three tiers, most urgent first. Inside each, every kind of problem is a box with its total, and one row per location: what’s wrong, where (Client › Location), and a button to the place it gets fixed. A box lists five locations and says how many more there are. When nothing is outstanding it says Nothing needs attention.

Act now

Something is failing or waiting on you.

BoxWhat it meansWhat the row does
Failed installsA queue’s last install attempt failed on some endpoints, or ZenPrint installed it but the endpoint no longer reports it (missing on endpoint). The same count as the queue’s failing badge.Open location; the queue’s page lists the failing endpoints with the actual error.
Alerts not deliveredA webhook gave up after every retry, so alerts sent to it are lost. Only for roles that aren’t limited to certain clients. Cleared by the next successful delivery.Open alerting: check the URL and the receiving end under Settings → Alerting.
Waiting for approvalEndpoints that checked in and wait for you. A pending endpoint gets no queues.Approve all approves that location’s pending endpoints right there. Review opens the location’s Endpoints tab filtered to pending.
No locationEndpoints with no location, because their RMM group path isn’t mapped yet. Only unscoped roles see these: they belong to no client.Move to a location opens the list of them. Map the group under Settings → Group mapping.
Stale assignmentsEndpoint assignments invalidated when the endpoint moved to another client. Reconcile skips them until you decide.Open queues opens the location’s queues. See when endpoints move.

Review

Worth a look today.

BoxWhat it meansWhat the row does
Config driftInstalled queues whose settings on the endpoint differ from the queue’s settings. The next reconcile usually puts them back.Open location. Investigate if the same queue keeps drifting.
New IP addressA scan found a known printer at a new address, held until you decide.Opens the printer, where Use new address and Keep old address are, or the location filtered to New IP address if there are several.
Raw port closedA scan found the printer on IPP or LPD, but Raw printing (port 9100) is turned off. Queues ZenPrint deploys print over Raw, so they won’t print until you turn it on in the printer’s network settings. The next scan clears it.Opens the printer, or the location filtered to Raw port closed.
New printersPrinters the scan found that have no queue yet (not ones you added by hand).Opens the printer, or the location’s printers filtered to New, no queue.
Not scanned recentlyNo endpoint at the location has scanned in the last 7 days, though one did before, so its printers’ health can’t be confirmed. The row names the endpoint that scanned last. Locations without printers aren’t listed.Opens the location. Fix the endpoint or the scan schedule in your RMM.
Missing printersNo endpoint has seen the printer on its recent scans. Same state that fires the printer.offline webhook.Opens the printer, or the location filtered to Missing.
Printers not confirmedThe location was scanned in the last 7 days, but no endpoint confirmed this printer in that time (the endpoints that used to see it haven’t scanned).Opens the printer or the location.
Removals not doneQueues you marked for removal that reconcile deferred (a safety check blocked it, or the removal failed) and that are still on the endpoint.Review opens the location’s Unmanaged tab, where each row says why.
Settings refusedThe printer refused one of the queue’s settings, say duplex on a model without it. The queue still prints.Opens the queue (or the location if several), where you edit its settings.
Disabled driver in useZenPrint disabled a driver that your queues still use, with its reason. Those queues keep working; the driver gets no new queues or fixes. One row per driver.Open queues lists the queues on it, where Change driver moves them.
Low suppliesA supply is at or under the low threshold: the same rule as the red toner dot.Opens the printer or its location.
Duplicate queuesEndpoints still have their old queue next to an installed ZenPrint queue for the same printer. A duplicate you allowed to stay isn’t counted.Remove duplicates marks them for removal right there (removed on the next reconcile, once the ZenPrint queue is confirmed installed). Review opens the location’s Unmanaged tab, where you can also allow a queue to stay.

In progress

Nothing to do; shown so it isn’t a surprise.

BoxWhat it means
Driver capturesPrinters flagged for driver capture, waiting for the next capture run on an endpoint that has the printer installed. The printer page has Cancel capture.

Each box also follows your role: you only see the kinds of problems your role can view (printers, queues, endpoints), and the in-place buttons only if you can make that change.

Recent activity

A live feed of the latest audit entries: who did what, when. Each row is written as a plain sentence naming the things involved (“Assigned queue Acme BW to endpoint WS-042”), with the person and the client/location underneath. View all opens the full audit log (/audit-log) with filtering and search. The feed follows the same per-role visibility as the audit log itself.

The feed shows activity by people in your workspace. Automatic platform actions (plan and entitlement syncs, and other control-plane changes) are kept out of this glance so they can’t crowd out real activity, but they still appear in the full audit log.

When the numbers update

Everything on the dashboard loads when the page does. It isn’t a live stream, so refresh the page to pull current counts and alerts. The underlying data only moves when scripts run anyway: discovery, drift, and missing-printer state all change on the next scan or reconcile, not on a timer.