Public Links
Thirty-two random bytes, hashed before they are stored, handed back exactly once and good until a day you name. Revoking writes a timestamp and the row stays behind to explain the dead address.
One address per board, and only one
activenever returned again
sha256: 4d81…07ba
Closed won
Widget renderer ships with the widget module.
Open pipeline
Widget renderer ships with the widget module.
Revenue by month
Widget renderer ships with the widget module.
Win rate
Widget renderer ships with the widget module.
- An address nobody mintednot found
- An address from another workspacenot found
- One that lapsedgone · expired
- One that was revokedgone · revoked
Product figures from the platform’s own defaults - not customer averages
How it works.
Generated once, kept as a fingerprint
Thirty-two bytes from the system generator become sixty-four hex characters on the wire. What lands in the table is their SHA-256 digest. The plain value is returned in the creation response and never again, so losing it means minting a new one, not looking the old one up.
One live address per board
Minting a new one revokes whatever was there inside the same transaction. There is never a moment with two working addresses, and there is never an old address quietly still working after somebody made a replacement.
Lapsing and revoking are separate acts
Pick any expiry inside a year. Extending adds days to whichever is later, now or the current expiry, so an address that already lapsed can be brought back without changing its value. Revoking stamps the row and keeps it, which is what lets an audit later explain why a URL stopped.
What a stranger with the address sees
The board's name, description, timezone and window label, and its tiles in their grid positions drawing their figures. Each tile resolves against the workspace the board belongs to rather than against whoever opened the link, so the reader sees the board as its owner sees it and nothing beside it.
One moment in every number.
Every number passes through the same seven. Public Links is the lit one, and everything either side of it is a different page in this category.
- 01Query
what is asked, and of what
- 02Shape
the measure and the dimension
- 03Draw
the visual chosen for that shape
- 04Arrange
where it sits on a dashboard
- 05Filter
narrowing it after the fact
- 06Drill
going from the number to the rows
- 07Share
who else gets to see it
The specifics.
8 facts- Token
- Thirty-two bytes, hex on the wire, SHA-256 at rest. A leaked table leaks no working address
- Shown
- Once, at creation. The status endpoint returns state and never the value
- Expiry
- Seven days unless you say otherwise, a year at most, extendable in place
- Revocation
- Immediate, stamped, and the row retained
- Replies
- An unknown address and one from another workspace are both a flat not-found. Lapsed and revoked answer with a gone status naming which
- Who may mint
- The board's owner alone. An admin who can open the board still cannot publish it, and neither can anybody holding a copy they did not make
- What renders
- The board as laid out, with every tile drawing its own figures. Treat a link as publishing the numbers and the way they were built, because it publishes both
- Not the same as
- Embedded Widgets, which draws for people who are already signed in. This is the one route by which a figure reaches somebody with no account at all
What this is assembled from.
A number on a dashboard was built somewhere before it was drawn. These are the parts it is made of.
More in Reporting & Analytics
12 capabilitiesSeven data shapes, twenty-two visuals, shareable without the portal.
A widget declares a data shape; the visual is a separate choice. Swap between the visuals valid for that shape and the query does not run again.
Columns, funnels, treemaps, radar, scatter, gauges and pivots - offered only where the data shape supports them, so no chart can misread its own data.
Click a bar and the rest of the dashboard follows it, so the next question is asked by pointing at the answer instead of rebuilding the filter.
Wire a chart's clicks to a second dashboard. The value travels on the URL and is read by the board that was named before it paints for the first time.
Cross one dimension against another with row, column and grand totals - the shape a finance team asks for when a chart will not settle the argument.
Colour a number by the rule that matters - under target, over threshold, inside a band - so a dashboard reads correctly from across the room.
Draw the target on the chart itself, so performance is read against the number that was promised rather than against the shape of the bars.
Put a window against the one before it, or against the same window a week, month, quarter or year back, on a card as a difference or a chart as a series.
Seventeen operators in a nested and-or tree, so the report that needs two exceptions and a date range stays one widget instead of becoming three.
Group by day through year, by equal-width bands, or by breakpoints you set, each band carrying a sort key so the axis reads in bucket order.
Six palettes including a print set, pinned per widget, each carrying eight series colours plus the axis, grid, card and tooltip colours drawn around them.
Total calls, answered rate, average duration and missed calls, split by direction and outcome, over the call records rather than a sampled export.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Reporting & Analytics
See public links on your own floor.
Thirty minutes, your numbers and your data. We will set public links up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included