# Export and share

Choose a PDF for a visual handoff, YAML for an editable map, or Team for a shared
live view. Each preserves a different part of your work.

## Export a PDF

Choose **PDF** in the toolbar, or **⋯ → Export PDF** on a narrow screen. Desktop
opens a native save dialog; a browser downloads the file. Viewers can export too.

The export fits the whole topology onto one A4 landscape page as vector drawing,
with diagram labels and a legend. It is not a screenshot of the current viewport
or Tree view. Large maps may be scaled down considerably.

Page cards contribute their title and URL, not the remote site's rendered
content. Terminal output and chat conversations are not included. Health is a
snapshot of the current frontend state, not a durable incident record.
The exporter does not recompute the aggregate group-health badges shown by Tree
and canvas views.

## Share the YAML

Share a copy of the workspace file or commit it to your own Git repository. The
recipient can open it in Desktop. There is no built-in Git remote, sync service,
or automatic credential transfer.

The YAML contains more than the diagram: it can include endpoint addresses,
notes, and command definitions. Review it before sharing. The recipient needs
their own network access, system tools, and authentication to run checks.

Opening YAML does run configured fixed checks as the app requests health. Custom
commands require workspace trust or a process override; see
[checks and actions](checks-and-actions.md).

## Share a live view with Team

The [Team Daemon](daemon.md) hosts one topology and collects from its own machine.
Give viewers a read-only browser link and editors the separate editor credential.
Both see the shared map; only editors can save or request actions.

Closing a browser does not stop daemon collection. Desktop workspaces do not
automatically synchronize with Team: the operator chooses the daemon's YAML file.

For programmatic reads, use the [JSON API or MCP](operational-graph.md).
