How to share a dashboard with only the people who should see it
Your agent built a dashboard of revenue, pipeline or spend, and five people should see it. The difference between a dashboard of fixed numbers and one that reads Stripe or HubSpot live, and how to share each behind sign-in.
A finance lead asks her coding agent for a dashboard: monthly recurring revenue, failed payments, refunds, and the ten largest customers. An hour later it is on her screen, and it is better than the one the team pieced together in a spreadsheet.
Now the CFO, two people in finance and the head of ops should see it. Nobody else should. Revenue by customer is not something to leave at a link that anyone can open.
This article is about sharing a dashboard with exactly those people. We make Spryloom, and the last two sections describe it, so read them knowing who wrote them. First, a choice that decides almost everything else.
Is it a picture of the numbers, or a window onto them?
There are two kinds of dashboard, and they are built differently.
- A dashboard of fixed numbers. The agent pulled the data once, from an export or an API while building, and wrote the numbers into the HTML. It is a report with charts, true as of the day it was made, updated by making it again.
- A live dashboard. It asks Stripe, HubSpot or Airtable for the numbers each time someone opens it, or on a schedule. It needs a server, because it needs an API key.
Ask your agent which one it built if you're not sure. Many dashboards should stay the first kind. A month-end pack that is reviewed once doesn't need to be live, and a page with no key in it has much less that can go wrong.
The usual ways to share one
Send a screenshot or a PDF. Fine for one meeting. The copies can't be taken back, and every update is another email.
Share it from the tool that holds the data. If the numbers already live in a BI tool your company pays for, or in Stripe's or HubSpot's own reports, sharing there is often the right answer. IT already knows their permissions. The limit is that each viewer needs an account there, and your agent's dashboard isn't in it.
Host it and add a login. Put the file or the app on a general host and add sign-in, either inside the app or with an access product in front, such as Cloudflare Access. This works, and suits a team with someone to set it up. For one HTML file, How to put a login in front of an HTML page compares those routes in detail.
Publish it behind sign-in with Spryloom. The rest of this article.
A dashboard of fixed numbers: publish it as a page
A page is plain files with no server, behind the same sign-in as an app.
spry publish revenue-dashboard.html --visibility invited spry invite revenue-dashboard --email megan@yourcompany.com # later, with new numbers: same command, same address spry publish revenue-dashboard.html --visibility invited
Megan gets an email with an Open button that signs her in. It works once, for seven days; after that she asks for a sign-in link by email. Anyone not invited gets the sign-in page; the file is never sent to them.
To update the numbers, the agent rebuilds the page and publishes again. The CFO's bookmark keeps working.
A page may load chart libraries from cdnjs, jsDelivr and unpkg, and fonts from Google Fonts. What it can't do is call an outside API. Its scripts talk only to the page itself, which is exactly why a page never has a key in it.
A live dashboard: publish it as an app
When the numbers have to be current, the agent builds a small app: a Node server that holds the key, fetches the numbers, and serves the charts. Two pieces of setup make it work.
Declare the outside host. An app reaches its own database and nothing else unless spryloom.yaml says otherwise:
app: name: Revenue dashboard description: Monthly recurring revenue, failed payments and refunds, from Stripe. runtime: frontend: react backend: node build: npm run build start: node server.js access: visibility: invited admins: [megan@yourcompany.com] egress: - api.stripe.com
- What the invitation names.
- A Node server that holds the key.
- Only people you invite. Megan is an admin.
- The one outside host. Anything else stays unreachable.
The hosts an app may declare are a fixed list. For dashboards the useful ones are api.stripe.com, api.hubapi.com (HubSpot), api.airtable.com, api.notion.com, api.github.com, api.linear.app, and sheets.googleapis.com with oauth2.googleapis.com. A host that isn't on the list is refused at publish.
Give it the key as a secret. Never in the code, never in spryloom.yaml, which is committed. An app can't be given a secret before it exists, and secrets reach it when it is published:
spry secrets revenue-dashboard set STRIPE_API_KEY=...process.env.STRIPE_API_KEY.The value is in no image layer and no log line, and spry secrets revenue-dashboard list shows names and dates, never values.
Use the narrowest key the service offers. Stripe, for example, lets you make restricted keys that can only read. A dashboard has no reason to hold a key that can issue refunds.
Not everyone sees the same thing
A page shows everyone the same file. An app knows who is asking: each request arrives with x-spryloom-email and x-spryloom-role, and Spryloom removes any copy sent from outside. The agent can use the role to show per-customer detail only to admins (Megan, and the owner), and totals to everyone else.
That is a rule in the app's code, written by your agent. It is the one place where you should test with two accounts before sending the link; How do you test an AI-built app before coworkers use it? shows how.
Keeping history
Stripe doesn't keep the dashboard's own history of what MRR was each Monday. For a trend line the service can't give you, the app can declare a database and a job that saves a snapshot:
data:
postgres: true
tables: [snapshots]
jobs:
- name: nightly-snapshot
command: node jobs/snapshot.js
schedule: "0 6 * * *"
timezone: America/New_York
A job runs at most once every 10 hours, so a daily snapshot fits and an hourly one is refused. Your AI-built finance dashboard works. Now comes the hard part. covers what else to check before finance relies on the numbers.
What Spryloom doesn't do
- Outside services come from a list. If your numbers live in a database or warehouse that isn't on it, the app can't reach it. Ask us at hello@spryloom.com, or export the data and publish a page.
- Pages can't be live. A page's scripts can't call an API. Live numbers mean an app.
- No Google or Microsoft sign-in. Everyone signs in with a link sent to their email.
- It isn't a BI tool. There is no query builder or chart editor. The dashboard is the code your agent wrote, and changes are made by asking the agent.
- A page is a login, not a redaction. Everything in the file is visible to everyone invited. Leave out what some of them shouldn't see, or make it an app with roles.
- Limits. 25 invited people per app, 20 secrets per app, and outside traffic of 500 MB a day per app.
Start here
In Claude Code, add the plugin once:
/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom
Then say "publish this dashboard for Megan and the CFO, only people I invite". If you already have the HTML file, from a terminal:
npx -y spryloom publish revenue-dashboard.html --visibility invited
Then open the address in a private browser window. You should see a sign-in page, not your revenue.