English Português

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 I already have an account How it works

Sign in with Google, Microsoft, or GitHub. 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.

Step 1 of 4

You ask, your agent publishes

Ask your agent in chat. It publishes and hands you the link.

Your agent

Publish this report for the company.

sales-report.html

Ran npx @securepublish/cli publish …

Published for the whole company:

acme.securepublish.work/​qm4tz7hk2c/​sales-reportCompany only

  1. Your agent

    Publish this report for the company.

    Published for the whole company

    acme.securepublish.work/​qm4tz7hk2c/​sales-report

    You ask, your agent publishes

    Ask your agent in chat. It publishes and hands you the link.

  2. Private link

    acme.securepublish.work/​qm4tz7hk2c/​sales-report

    Company only — lock from the start.

    Private from the start

    Only your company and people you invite can open it.

  3. Sign in to view

    [email protected]

    [email protected] sees the report.

    Your coworker signs in with company login

    They open the link, sign in with their work account, and see the page.

  4. Access denied

    This dashboard only opens for people who sign in with the company email. Sign in with your company account or ask whoever published it for access.

    Not on your team or invite list? It won't open

    Signing in isn't enough: the email has to match your company domain or be on the invite list.

  1. You ask, your agent publishes

    Ask your agent in chat. It publishes and hands you the link.

  2. Private from the start

    Only your company and people you invite can open it.

  3. Your coworker signs in with company login

    They open the link, sign in with their work account, and see the page.

  4. Not on your team or invite list? It won't open

    Signing in isn't enough: the email has to match your company domain or be on the invite list.

  5. From your agent to your coworker, no public link.

Illustrative demo. Company, link, and figures are fictional.

Install example

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

Requires Node 22 or newer.

Then tell your agent:

“Publish this HTML dashboard with Secure Publish.”

Proof

See the example dashboard

Try the flow demo (Continue as …), then open Sales Dashboard — 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.

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, or GitHub.

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

Get started

Create account — start now

Sign in with Google, Microsoft, or GitHub. 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 I already have an account

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