Publishing

In Plotly Studio's agentic workflow, artifacts are outputs created during a session, such as charts, tables, reports, and apps.

You can publish artifacts from any step in a session, including:

A report
A data app
A single analysis step with its charts and tables

Note that published artifacts are Dash apps and are managed the same way as traditional Dash apps hosted on Plotly Cloud or Dash Enterprise.

How artifacts map to session steps

Each artifact is associated with the specific step that created it in a session.

If you ask for a report or app, that artifact is attached to that step.
If you later ask the agent to iterate on an existing artifact, the new result is saved as a separate artifact on a new step.

This means multiple artifact versions can exist in the same session, and each one can be published independently.

Data app

Publish an artifact

To publish an artifact:

In your session, find the step associated with the artifact you want to publish.
Select Publish on that step.

Publishing may take about a minute. For Plotly Cloud users, the artifact is published to the team associated with the session.

Note

In the Plotly Studio agentic workflow beta, publishing creates a new deployed artifact. Updating an existing deployed artifact in place is not currently supported.

What happens after you publish

Publishing usually takes about a minute. After publishing completes, you can:

Copy the artifact URL.
Open the deployed artifact.
Republish the artifact.
Open the artifact's settings and logs in the deployment platform.

Security and permissions

For artifacts deployed to Plotly Cloud, you can:

Inspect the app logs.
Configure app security and sharing in the deployed app settings. See Access control and sharing.
Manage runtime configuration with environment variables when needed.

Cloud access controls

For artifacts deployed to Dash Enterprise:

Go to the App Info at https:<hostname>/apps/<app_name> to adjust access control and sharing.

DE access controls

Beta limitations

Publishing is step-based, so each iteration creates a separate publishable artifact.
In-place update of an existing deployed artifact is not yet available in beta.