Publishing and sharing reports
What a report is, how its versions work, and how to share it — with colleagues, teams, clients and, where your organisation allows it, the public. Comments, PDFs and analytics too.
A report is HTML an agent or a person published — a report, a dashboard, a briefing, a prototype — at a secure address inside your organisation's sign-in. Most arrive from an agent. You can also publish one yourself from Publish report: drop an HTML file, a ZIP or a folder.
Publishing takes a seat: organisation owners, administrators, workspace administrators and publishers can publish. Viewers cannot, and do not count against your plan's seats. Anybody can open what has been shared with them.
A report's page
Reports lists your organisation's reports, filtered to My reports, Shared with me, Living, Awaiting approval or Archived when you want fewer. A report's own page shows its live address (with a button to copy it), how many times it has been opened, its versions, the feedback on it, and who it is shared with. Open report shows it as readers see it.
Versions
Every publish is a new version, and every version is kept. The address never changes: readers always see the current version unless you pin one. Each version is scanned when it arrives and marked Scan passed, Warnings or Blocked; a blocked version never goes live.
- Restore
- Make an earlier version current again. The address stays the same, and the versions after it are kept.
- Pin
- Show everyone one version until you unpin it. Publishing carries on underneath, and unpinning brings readers straight back to the latest.
- Compare
- An earlier version beside the current one.
Your organisation's publishing policies can hold a new version for an administrator's approval before it goes live; the report then shows Awaiting approval. Rules that hold a publish apply on Business and above.
Workspaces
A workspace is a team that publishes and receives reports together. A report can be filed in one — use the workspace chip on the report's page to move it — and sharing a report with a workspace shares it with the workspace's members. Creating workspaces is on Team and above; an organisation that moves to a plan without them keeps the ones it has.
Sharing a report
Share on a report's page opens three tabs. The owner, organisation administrators and anyone who can publish can change who sees a report. Every share goes through your organisation's sharing settings, which can refuse it.
| Tab | What it does |
|---|---|
| People & teams | Grant access to people, groups, workspaces or the whole organisation — they find it in their list. Also switches on anyone at an email domain your administrators allow, and public access where it is permitted. |
| Send | Email the report to up to 50 addresses with a covering note, optionally letting them comment back. Each recipient gets their own link, which keeps working as the report is updated. |
| Secure links | Create a link with an expiry, restricted to email domains, requiring email verification, or allowing comments. The link is shown once, so copy it when it is made. Revoke a link at any time. |
Guests and public links
A guest is somebody outside the organisation a report was shared or sent to. They prove their email address with a one-time code, then read — and, if allowed, comment — under that address. Whether guests are allowed at all, which domains may be shared with, and how long new links last by default are your administrators' choices, under Admin → Sharing.
Access requests
Somebody who opens a report they cannot see can ask for access. The request appears in the owner's inbox and on the report's page, where the owner, an administrator or anyone who can publish approves or declines it. Approving goes through the same sharing settings as any other share.
Comments and feedback
Readers with permission to comment select a passage and comment on it, or comment on the report as a whole. The Feedback panel on the report's page gathers the open threads, those sent to an agent in a brief, and those the latest version addressed. From there you can turn the open feedback into a brief for the agent that publishes the next version; an agent can also read open comments itself. Open feedback on reports you own is listed in your inbox. Which comment notifications reach you is up to you, in Settings.
Download PDF renders the current version exactly as a reader sees it. It counts as a download, so your organisation's downloads setting and its policies apply, and it is recorded in the audit log.
Analytics
On Team and above, a report's page shows unique readers, total opens, how many readers were inside the organisation and how many outside, opens over the last 30 days, views per version and recent readers. Whether you see readers' names or only counts is an administrator's setting.
Developers publishing from code will find the API, the CLI and the MCP tools in Publishing reports. Deliverd's plans and their limits are in Billing and plans.