> ## Documentation Index
> Fetch the complete documentation index at: https://docs.communityhub.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Sharing and Exporting Visualizations in Data Hub

> Every Data Hub visualization has a public View link usable for web embedding or digital signage, plus CSV export for the underlying variable data, and an in-development bulk Data Downloader for larger exports.

Data Hub visualizations don't use share invites or permission-scoped links. Instead, every visualization has two surfaces — see [Build Dashboards](/guides/building-dashboards#setup-vs-view) — and it's the **View** link that gets shared or embedded.

## Web embeds

The View URL for a visualization is a standalone page that can be embedded directly, for example:

```text theme={null}
https://<your-subdomain>.communityhub.cloud/dh-public/time-series-chart/slide/<id>/chart-window/yesterday
```

Query parameters on the View URL control display options such as showing or hiding the header and chart title (`show-header`, `show-chart-title`) and the time window shown (`chart-window`, e.g. `yesterday`, `today`, `last-30-days`).

<Note>
  This page is a stub for the full list of supported query parameters and embed patterns per visualization type — that reference hasn't been written up yet.
</Note>

## Digital signage

Visualizations are also the content source for physical digital signage screens (installed at partner sites). This is a hardware/display concept distinct from web embedding — if you're setting up or troubleshooting a physical signage screen, that's a separate process from generating a View link.

## CSV export

Variable data can be exported as CSV directly from a variable's Graph or Table view. See [Core Concepts](/core-concepts#variables).

<Note>
  Export has been an active area of bug-fixing across visualization types (heatmap, load profile, multi-variable charts) — if an export button isn't working as expected, it may be a known issue rather than something to configure differently.
</Note>

## Data Downloader

<Warning>
  **In development — interface not yet designed.** The Data Downloader's screens and interaction flow haven't been built yet; what follows describes the intended functionality and default parameters the design will target, not a feature you can use today. Defaults below are revisable once the interface exists or usage patterns are known.
</Warning>

The Data Downloader is a bulk-export tool for larger datasets, distinct from the single-variable CSV export above. It reuses the same Data Visualizer search and filter workflow — selecting variables, time range, resolution, units, and standardization — but instead of exporting one variable's view immediately, it submits an **asynchronous export job**.

**Intended flow:**

<Steps>
  <Step title="Configure the export">
    Select variables, time range, resolution, units, and standardization using the same search and filter interface as the Data Visualizer, plus whether to include metadata.
  </Step>

  <Step title="Submit the job">
    The export is queued and processed as system resources permit, reusing Data Hub's existing bulk-export job-queue infrastructure — it isn't generated instantly.
  </Step>

  <Step title="Download the result">
    Once complete, the export appears on a recent-downloads page within your account as a downloadable file.
  </Step>
</Steps>

**Planned defaults:**

| Parameter           | Default                                                                                |
| ------------------- | -------------------------------------------------------------------------------------- |
| Output format       | CSV only at launch                                                                     |
| Retention window    | Download links expire 7 days after the export completes                                |
| Maximum export size | 1 year of data per variable, per job — larger ranges may be split across multiple jobs |

**Authentication:** the same registered, Auth0-authenticated user account required for the [Data API](/api-reference/introduction) — no separate credential is issued for the Data Downloader.

<Note>
  The Data Downloader has no public API of its own — it's accessed exclusively through Data Hub's web interface. For programmatic access, use the [Data API](/api-reference/introduction) instead.
</Note>