Not every audience should have a Delphi account. Sometimes you need to hand a stakeholder, a regulator, a partner, or the general public a read-only view of a command center without asking them to sign in. Public dashboards do exactly that: flip one flag on the command center and its metrics page becomes available at a shareable URL, no authentication required.
What a public dashboard is
A public dashboard is a read-only render of a command center at https://<your-tenant>.outcome.com/public/<dashboardId>. Open the URL in any browser — no Delphi account, no invite, no session — and you’ll see the metrics grid, KPI cards, and any visualizations whose underlying data is classified as public. Chat, mutation, the Data tab, the Permissions tab, and anything above public classification are all hidden.
The tenant boundary is still enforced. A public dashboard on tenant-a.outcome.com/public/X can only read data that belongs to tenant-a — it cannot reach across tenants, and the subdomain is part of how the tenant is resolved. Making a dashboard public lowers the auth requirement for reads; it does not cross the tenant isolation line that every other Delphi surface respects.
Publishing a dashboard
Open the command center, go to the Permissions tab, and look for the Public visibility toggle. The toggle is owner-only — admins and editors cannot flip it. Flip it on, and the next request to the public URL will resolve.
As soon as public visibility is on, the Permissions tab also surfaces a Public URL panel with the live link, a copy button, and an “Open in new tab” affordance. You don’t have to construct the URL by hand or remember the slug — the panel is the canonical place to grab the link to share, and it disappears the moment public visibility is flipped back off.
Behind the scenes this marks the dashboard as public. The public route explicitly checks that flag and returns a 404-equivalent if it’s not set, so even someone who knows the dashboard ID cannot read a private dashboard by guessing at the public URL.
If you want a memorable URL, you can also set a URL-friendly slug on the dashboard (acme-water-quality instead of a raw dashboard ID). The slug-based URL is easier to share in presentations, email, and press materials.
What’s visible
The public view is deliberately narrow. Visible:
- The metrics grid with KPI cards and visualizations rendered using the same components as the authenticated view, just with editing affordances suppressed.
- Any chart or KPI whose source data is classified
public— including KPIs and visualizations whose inherited classification resolves topubliconce lineage propagation has run. - The dashboard’s title and description.
Hidden:
- The Data tab, Alerts tab, Agents tab, Permissions tab, Audit tab, Compliance tab.
- Any chart or KPI whose source data is
internal,confidential, orrestricted. Gated cards render a placeholder rather than the underlying number. - Any editing surface, mutation endpoint, or scenario runner.
- The KPI lineage modal, the Insights button, the Export button, and any other action that mutates state or surfaces non-public detail. Cards know they’re rendering in a public context and hide those affordances themselves rather than relying on the route alone to gate them.
- All authenticated-only surfaces — connected MCP sessions, notifications, recommendations, and action proposals.
This split is what makes public dashboards safe to share with audiences you don’t otherwise trust. The public classification is the boundary; set your dataset classifications carefully and the read-only view handles the rest.
Optional: public chat
By default a public dashboard is read-only — visitors see numbers but cannot ask the agent anything. If you want to give them a Q&A surface as well, you can flip on public chat per agent. The agent editor on the Agents tab carries a public chat toggle alongside the rest of the agent’s configuration; toggling it on opts that specific agent into the unauthenticated chat surface, leaving every other agent on the dashboard untouched.
When public chat is on, the public dashboard view renders a chat affordance — anonymous visitors can ask the agent questions and stream responses without a Delphi account. Every tool the agent invokes on a public chat surface runs under the viewer scope and a public classification filter. An agent talking to an anonymous visitor can never read internal or higher data, never propose actions, and never write back to the dashboard — even if its built-in tool set normally includes those things.
Anonymous sessions are short-lived and scoped to the public surface, so back-to-back questions from the same visitor share context without leaking session state into the rest of the site, and a single visitor can’t flood the chat with rapid-fire requests. Flip the toggle off and the chat affordance disappears immediately on the next page load.
Public chat is opt-in per agent for a reason: it puts your model token budget in front of an unauthenticated audience. Turn it on when the dashboard is built around a question you want strangers to be able to interrogate; leave it off if the value of public visibility is just the numbers.
When to use a public dashboard
Good fits:
- Stakeholder briefings — a live view of quarterly progress you want a board or donor community to watch without creating accounts.
- Press and transparency — a permanent URL for journalists, regulators, or the public to see the same live numbers your team works from.
- Embeds — a public dashboard URL embeds cleanly into an external CMS, microsite, or portal as an iframe for a consistent headline surface.
- Partner dashboards — a scoped view for a single partner organization when creating them a tenant account would be overkill.
Bad fits:
- Audiences who should have editing or exploration access — invite them as analysts or editors instead.
- Command centers where even the
public-classified data is sensitive to outside observation — tighten classifications before publishing, not after. - Situations where the audience needs to see non-public data — they need authenticated access, not a public view.
Turning it off
Flip the public visibility toggle back on the Permissions tab. The next request to the public URL stops resolving, and the change takes effect immediately — there is no cached public state to expire. Anyone who had the URL open in a browser will get a clean 404 on their next navigation.
Audit
Enabling and disabling public visibility is recorded in the audit log like every other permission change, with the actor, timestamp, and target dashboard. If you need to prove that a dashboard was public for a specific window, the audit stream is the authoritative record — you don’t have to trust anyone’s memory.