Download an export bundle

Every published dashboard can be downloaded as a Data Studio export bundle — a ZIP of YAML documents — and imported into your own tenant. The download needs no sign-in and no request: open a dashboard and the bundle is in the panel beside it, under Export bundle.

The two platforms

Data Studio ships in two places, and the panel lists both:

Platform	Control	Why
RUCKUS One	A live download link	It has an export bundle format
RUCKUS AI (SmartZone)	A disabled button reading “Coming soon — the converter is being written”	RUCKUS AI has no bundle format of its own, so the shape a converter would emit is not yet settled

The unavailable platform is listed rather than hidden, because “coming soon” is information you can act on where a missing button is not.

The disabled button is not what makes it unavailable

The download route resolves the platform through the same registry the panel reads and answers 404 for one that is not available — on the server, before anything is read from storage. The gallery’s pages are static files served to anyone who asks for them, so a disabled control could never be the thing deciding this.

Download and import

1. Open the dashboard you want, from the grid or from its /d/{slug} permalink.

2. Click the platform button under Export bundle. The file arrives named after the dashboard’s slug — rks-sw-l2-export.zip.

3. In Data Studio, go to Dashboards → Import and choose the ZIP.

4. Open the imported dashboard. Its charts bind to your own datasets and render against your own data.

What has already been done to the bundle

The file you download has been through two separate operations, and knowing which is which explains what you will see after importing.

Scrubbed once, when it was uploaded. Identity fields are deleted, filters pinned to tenant-scoped columns are dropped, and values with a recognisable shape — MAC addresses, IP addresses, hostnames, emails, serial numbers — are replaced with values from reserved documentation ranges. A bundle that still matches a pattern after that is never stored at all. The full account is in What is removed before publishing.

Re-identified on every download. Each download gets a fresh set of dashboard and chart identifiers. Dataset and database identifiers are left exactly as they were.

Why the identifiers are fresh every time

An import matches objects by identifier, and those identifiers match globally across tenants — not just within one. If two people imported byte-identical copies of the same bundle, the second import would not create a second dashboard; it would update the first person’s record and move its tenant scoping to the importer.

So no two downloads of the same dashboard carry the same dashboard and chart identifiers. One old-to-new map is built for the whole archive and then applied across every file, which is what keeps a layout block pointing at the charts it names. The response is sent no-store for the same reason: a cached copy handed to a second downloader would reintroduce the exact collision this prevents.

Dataset and database identifiers are deliberately excluded from that map. They are how the import binds to a real dataset, so they must survive both operations unchanged.

What to expect after importing

You will see	Why
The dashboard’s layout, charts and sections, intact	Structure is not sensitive and is not touched
Charts rendering against your data	Filters pinned to tenant-scoped columns such as zoneName, ssid and apName were removed rather than rewritten — a rewritten value would match no real row and the chart would render empty
Venue or site names still in chart titles and text	A name like “Riverside” or “Home” is an ordinary word with no shape a pattern can catch. These are reviewed by a person before publishing rather than caught by a rule
Documentation-range values in descriptions	00:00:5e:00:53:01, 192.0.2.4, host-1.example.com and similar are replacements, not real values
Filter dropdowns on tenant-scoped columns still present	A dropdown control is part of the dashboard’s structure, so it survives; only its pre-selected default is cleared

Datasets are referenced, not included

The bundle carries no datasets/ or databases/ directory — datasets are referenced by identifier only. The import binds to a dataset that already exists in your tenant. If the dataset a chart names is not there, that chart has nothing to bind to.

URLs

The canonical download URL is the bare one, and it means RUCKUS One:

https://dashboards.lanpulse.com/d/{slug}/download

The per-platform form resolves to the identical bytes for the default platform:

https://dashboards.lanpulse.com/d/{slug}/download/ruckus-one

Both are rate limited to 20 downloads per minute per address, and both refuse a dashboard that is not currently published. See Public HTTP API.

Next steps

What is removed before publishing Exactly which fields are deleted, which filters are dropped, and the audit that gates the write.

Browse and filter the gallery Find the dashboard whose bundle you want, by role, vertical, product or dataset.

Troubleshooting A download that 404s, a 429, and what an empty imported chart means.