Skip to content
Dashboard Gallery
Get Support

Browse and filter the gallery

The gallery is a grid of published dashboards with a filter rail beside it. Filters live in the URL, so a filtered view is a link: whatever you select appears as ?facet= in the address bar, and sending that address sends the selection with it.

Each card carries the dashboard’s thumbnail, its title, a one-line summary and up to three category chips — the vertical it belongs to, followed by up to two product chips. The other categories a dashboard carries are on the dashboard itself rather than the card, because a card has room for the two facts people browse by.

Clicking a card opens the dashboard without leaving the page, and changes the address to that dashboard’s permalink.

The rail groups categories by kind. There are five, and they fall into two groups: three a person assigns, and two read out of the export bundle at upload.

KindLabel in the railAssigned byExample values
roleRoleA personBusiness leader, Network engineer, Help desk technician
verticalVerticalA personHospitality, MDU, Higher Ed, K-12, US Federal Government, MWL, Service Provider, LPV, Pro AV
productProductA personWi-Fi, Switching
datasetDatasetRead from the bundleThe Data Studio dataset each chart is built on
vizVisualizationRead from the bundleTable, Big number, and the other chart types used

Role sorts first because it is the broadest way into the gallery — who a dashboard is for. Every role value returns a real set; a vertical may return a single dashboard.

Dataset and Visualization start collapsed. They are mechanical, there are many near-identical values, and they are more useful for narrowing a search than for starting one. The rail collapses them because the server marks those kinds as derived, not because their names are special-cased in the page.

A category with nothing behind it is hidden

Section titled “A category with nothing behind it is hidden”

Counts in the rail are over published dashboards only, so a category with a count of zero is a dead end and the rail leaves it out. The one exception is a category you currently have selected: dropping that silently out of a link someone sent you would be worse than showing it.

Selections are ORed within a kind and ANDed across kinds — the behaviour a filter rail implies.

Selecting Hospitality and Higher Ed shows dashboards in either vertical. Adding Switching to that narrows it to dashboards that are in one of those two verticals and carry the Switching product tag. Selecting more categories from different kinds can easily land on nothing, and the empty state says so:

No dashboard carries every category selected. Clearing one of them will widen the results.

Section titled “A filter link that no longer resolves shows nothing”

If a ?facet= value in a bookmark names a category that no longer exists, the gallery returns no dashboards — not the whole unfiltered gallery. A filter that quietly widens into “everything” looks like a working page, which is the worse failure: you would read a full gallery as the answer to a narrow question.

The rail names the dead value rather than dropping it in silence:

Some filters in this link no longer exist: d-sla. Remove them

Clicking Remove drops just those values and leaves the rest of the selection in place.

Every dashboard has a permalink at /d/{slug} — for example https://dashboards.lanpulse.com/d/rks-sw-l2. That URL works three ways at once: a person gets the dashboard open over the gallery, a link unfurler gets the dashboard’s own title, description and thumbnail, and a crawler gets a real page. A slug that is not published answers 404, and the gallery renders its own not-found state rather than a bare error.

The open dashboard shows:

  • The full screenshot, with Fit, + and zoom controls stepping through 1×, 1.5×, 2×, 3× and 4×. Double-clicking the image toggles between 1× and 2×, and dragging pans — but only once the image is actually bigger than the frame, so a dashboard that already fits does not move when you drag it.
  • The chart count, beside the title in the top bar.
  • The summary and description.
  • Every category it carries, grouped and headed by kind — so the panel says Dataset because the server does.
  • “Built on …” — the internal dataset names, under the friendly labels rather than instead of them. The chip says Client Info and Statistics because that is what the Data Studio UI calls it; this line says binnedSessions because that is what someone rebuilding the chart has to type.
  • The export bundle block — see Download an export bundle.
  • Previous and Next, which move through the dashboards currently in the grid.

Opening a dashboard reports one view for it, and selecting a category reports one selection for that category. These are reader numbers rather than an audited figure, they are never shown publicly, and nothing about you is stored with them — no account, no identifier, no session.