EN PT-BR

securepublish.work

For teams that ship AI dashboards and need company-only access.

Share AI dashboards
behind SSO

Install the Secure Publish skill — your agent publishes the dashboard and only signed-in teammates can open it. No loose file on the open web.

Create account — start now How it works

Sign in with Google. Viewers need the same email domain.

The problem

AI generates dashboards.
Sharing still leaks.

Models spit out dashboards, static sites, and analyses every day. Teams still drop them into Drive, Notion, or a public URL — and the share path becomes the leak.

Drive & Notion sprawl

HTML dashboards become attachments or weak previews. Permissions drift. Reviewers can’t tell what’s current or who can open it.

Public links leak

Anyone with the link can view the dashboard. A Slack forward is enough — the URL alone is the leak.

AI dashboards need company login

Access or VPN covers internal apps. Here the job is publishing the HTML your AI just made — as a signed-in-only page, not a loose file.

How it works

Install the skill.
Your agent handles the rest.

Prefer agents? Install Secure Publish once — the skill publishes the dashboard and keeps it behind company SSO. You don’t have to babysit the share path.

01

Install the skill

Add the Secure Publish skill to your agent environment. One install; it knows how to publish and share behind SSO.

Install example

$ npx skills add https://github.com/clovistx/secure-publish --skill "secure-publish"

Then tell your agent:

“Publish this HTML dashboard with Secure Publish.”

02

Ask your agent to publish

Point it at the AI-generated dashboard HTML. The skill ships it — no loose public file for visitors who aren’t signed in.

03

Teammates open with company login

Share the URL. Signed-in teammates see the dashboard; everyone else hits company login — not an open file.

Proof

See the example dashboard

Try the flow demo (Continue as …), then open Painel Vendas Q3. Labeled simulation — not real company SSO.

Try the flow demo

Skill-first for agents

Install once. Your agent publishes and shares — you stay out of the plumbing.

No loose public file

Unauthenticated visitors don’t get the asset. Company login is required before content is served.

Prefer the CLI?

Secondary / advanced

Prefer the CLI? The command below still works.

$ panel-gate publish ./painel-vendas-q3.html --title "Painel Vendas Q3"

Trust cues

What you can count on

How auth works — and what we explicitly do not claim. No fake logos, no invented metrics.

  • Company email domain after SSO — only emails on your company domain can open the link (after sign-in).
  • No loose file on the open web — visitors without a session don’t get the asset.
  • What we don’t claim — not compliance, not end-to-end encryption, not “impossible to leak.”

Sign in with Google. Microsoft, GitHub, Okta / SAML later.

The landing demo simulates the flow; real Google sign-in runs in the product.

Get started

Create account — start now

Sign in with Google. The same company login protects your dashboards. Install the skill, publish from your agent; the console shows URLs, who opened them, and when.

Create account — start now

Opens the Secure Publish console · company email domain required to view