Publish and share

Create an app from a chat or an agent, keep it updated, and control who can see it.

Publish one

Describe the page

In a chat, describe what the page should show and who it's for:

Build a pipeline dashboard for the EMEA team: open deals by stage with amounts,
deals with no next step flagged, and the five deals whose close date moved this
month. Group by owner. Publish it at /apps/emea-pipeline.

Be explicit about the audience and the path. An app at a memorable path gets bookmarked; one at an auto-generated path gets lost.

Iterate on the design

Apps are HTML, so "move the flagged deals to the top" and "make the stage column narrower" are valid instructions. Iterate before you share the link, not after.

Freeze it as a template, if it's recurring

Once the layout is right and the report recurs, save it as a template. Later runs reuse the design and only the data changes — see Apps overview.

Attach it to an agent

To keep it current, make the app the delivery destination of a scheduled agent (delivery). The agent's trigger becomes the refresh cadence.

Apps are shared by link. Shared links across the workspace are managed under Settings → Shared links, where you can see what exists and revoke anything.

Before sharing outside your company, check the obvious:

Whose data is on the page? A pipeline dashboard has deal names, amounts and owners on it.
Does it refresh? A live app you shared with a customer keeps updating. That's usually the point, and occasionally a problem — if you want a snapshot, produce a file instead.
Can you revoke it? Yes, from Shared links. Do that when an engagement ends rather than leaving links alive indefinitely.

A live app link keeps showing current data to whoever holds it. Treat an external share like a standing subscription to that data, not like sending a PDF.

When you want a frozen artifact — a board pack, an attachment for procurement — have the agent produce a file (PDF, DOCX, PPTX, XLSX) instead. Files are attached to the run and don't change afterwards. Apps are for state that should stay current.

Embedding

Apps render as standalone pages, which makes them straightforward to link from a Slack message, an email digest, or a CRM record — the pattern most teams use is a short Slack summary from an agent with a link to the app for the full picture.