Wato Docs
Artifacts & Dashboards

Artifacts

Publish agent-generated apps, reports, and dashboards as versioned, access-controlled web pages hosted by Wato.

An artifact is a published web asset — an HTML/CSS/JS page such as an app, report, preview, or dashboard — that Wato hosts at a stable URL with access control and version history.

Artifacts let teams share agent-generated work as a real, linkable page without standing up a separate deployment or losing control over who can open it.

Static vs. live

An artifact can be static (self-contained HTML) or live — a page that pulls fresh data at runtime through Wato-approved connectors while connector credentials stay server-side. Live artifacts are covered in Live Dashboards.

How artifacts are created

Artifacts are published in two ways:

  • From an agent session — an agent generates a page and publishes it as an artifact. Live dashboards are bound to an approved view policy at the same time (see Live Dashboards).
  • By uploading files — publish an HTML page (plus any CSS/JS) through the Wato UI.

Each publish creates a new version; the artifact's URL always serves the current version.

Visibility

Every artifact has one of three visibility levels:

VisibilityWho can open it
publicAnyone with the link.
orgAny signed-in member of your organization.
restrictedOnly the creator plus explicitly granted principals (default).

For a restricted artifact, you grant access to specific principals:

Grant typeExample
userA specific Wato user.
emailAn individual email address.
teamAll members of a team.
groupA synced directory group.
orgEveryone in the organization.

Grants are view (read) access. Wato checks the artifact's visibility and grants on every request and serves a 403 to anyone without access — so a restricted artifact stays private even though it has a public-looking URL.

Versioning

Each publish increments the artifact's version. The current version is what the artifact URL serves; older versions are retained for history.

  • Browse versions on the artifact's page under Artifacts.
  • Open the diff view to compare two versions file by file and see exactly what changed between publishes.

Hosting & access

Wato serves each artifact from a stable hosted URL on a Wato artifacts domain. Access enforcement happens at the edge: Wato validates the viewer's session and the artifact's visibility/grants before serving any content. For restricted and org artifacts, an unauthenticated viewer is asked to sign in first.

Where to find them

LocationWhat you do there
ArtifactsBrowse artifacts you can access across your teams.
Artifacts → [artifact]View a single artifact and its versions.
Artifacts → [artifact] → diffCompare two versions file by file.

Next

On this page