Publish & schedule

Every run can render your report into one or more downloadable formats:

• PDF — print-ready and pixel-accurate, for archiving and email attachments.
• PowerPoint (.pptx) — editable slides, with charts and tables mapped into native shapes.
• PNG — page images for thumbnails, previews, or pasting into other tools.
• Web bundle (HTML) — a self-contained page for hosting and embedding.

Preflight checks run before a report is published, so formatting and data-binding problems surface as warnings rather than broken output.

Publish a report to a live web viewer and share it with a link. Viewers see the designed report, not a flat screenshot, and each publish keeps a durable URL so a link you shared last quarter still resolves.

Need it inside your own product? An access-controlled embedded viewer lets you drop a report into another app behind a signed, publication-scoped token.

See Design reports for how the underlying document is built.

Instead of exporting by hand, point a publication at one or more delivery targets:

• Email — send the rendered report (or a link) to a recipient list, with open and click tracking.
• Slack and Microsoft Teams — post each run to a channel.
• Web publish — refresh the hosted viewer link on every run.
• Cloud storage drops — write the output files to Amazon S3 or Google Drive.
• Webhooks — notify your own systems when a run completes.

Set the cadence once, and each run refreshes the data and delivers on its own.

1. Choose a trigger — a recurring schedule (for example daily or hourly), a fixed interval, or manual and event-based triggers such as a data change.
2. Pick which formats and delivery targets that run should produce.
3. Optionally define variants — versions of the same report tailored per audience, including tag-based include/exclude rules and per-recipient redaction.

Refresh cadence is bounded by your plan, so a schedule that runs more often than your plan allows is flagged rather than silently accepted. SeePlans & billing for the limits on your plan.

Every run is recorded. You can see which runs succeeded or failed, roll a publication's configuration back to a previous version, and track opens and clicks on email delivery so you know a report was actually received.

Published reports are not public by default. You control who can open one:

• Public for an anonymous report the publisher has deliberately released.
• Unlisted for anonymous access by link without search discovery.
• Password protection on a shared link.
• Authenticated access for signed-in readers.
• Single sign-on (SSO / OIDC) so only your organization's members can view.
• Row-level viewer policies that scope the data a given viewer sees.

Public is the findable mode: the viewer sends noX-Robots-Tag exclusion, so crawlers may index a report the publisher has deliberately released. Unlisted and every credential-gated mode sendnoindex, nofollow, noarchive. Search inclusion is never guaranteed, and changing access later cannot instantly remove a URL already held by a third-party index. Use a curated Rahoto sample when customer work should not be made findable. Free-plan viewer chrome may show a “Made with Rahoto” badge linked to an attributed signup path.

You can also serve published reports from your own custom domain. Point a domain at Rahoto's edge with a CNAME; once DNS verification passes, a TLS certificate is provisioned automatically.