01
Stable share URL
The report address stays put while content evolves.
One link to deliver a complete HTML report
ReportArk turns a finished HTML package into a stable review link. Readers open the real report in the browser. Approved teammates comment next to the evidence. You update the content without changing the URL.
Keep the original report experience
HTML, CSS, images, fonts, and in-report interactions stay intact. You share the report people were meant to read — not a screenshot deck or a flattened PDF.
- Full static packageUpload a zip with index.html plus the assets the report already needs.
- Readable in the browserReviewers open a normal link. No repo clone, no local server, no file hunt.
- Built for real deliverablesAudits, benchmarks, research comparisons, launch plans, and agent outputs all stay interactive.
Stable links
Share with control
Give people one address to open. Pause sharing when work should stop circulating. Add a password when the audience needs an extra gate.
02
Optional access password
Add a password gate when a plain link is not enough.
03
Pause and resume
Turn sharing off without deleting the report or losing comments.
Discuss beside the evidence
Viewing can stay link-based. Commenting stays signed-in. Feedback lands on the heading, table, chart, or finding it refers to — and email keeps the right people in the loop.
- Element anchorsPin a comment to the exact part of the page under review.
- Threads on the pointKeep the conversation attached to the finding instead of a separate chat scroll.
- Email notificationsRelevant people hear about new discussion without living in the product all day.
Same URL, new content
Update the report without changing the link
When the analysis changes, upload a new version. Reviewers keep the original address. The current package is what the link opens.
01
In-place content updates
Owners replace the package without minting a new report id.
02
No broken handoff
Slack messages, tickets, and emails that already hold the link keep working.
03
Clear current pointer
The share surface always resolves to the ready current version.
Fit agent and API workflows
Agents and scripts should not stop at “file written.” ReportArk gives them a Skill, scoped API keys, and a completion rule: return the openable link.
- html-report-sharing SkillCopy one Skill so an agent can package, upload, and return the link.
- Scoped API keysGrant only the report and comment permissions automation needs.
- Link as the done stateMake the share URL the acceptance test inside the same conversation.
Owner workspace
See what you shared and what happened next
After delivery, keep the operational picture nearby: your reports, previews, access summary, and sharing controls.
01
Report lists with previews
Scan what you own without opening every package from scratch.
02
Access summary
Owners can check how the share surface is being used.
03
Sharing controls in one place
Password, pause state, and ownership actions stay on the report itself.
Ship the report as a link, not a local path
Upload a finished HTML package, or let your agent publish it and bring the review link back into the conversation.