Preview, PDF Export, and Sharing
When the modules look right, check the on-screen canvas against the PDF, then send the file and the audit Public Link. Clients should not need a login to the Report Builder.
On-screen preview vs exported PDF
The builder canvas is the preview: letter-sized sheets, chapter bands, and the same section copy as the PDF. Layouts should match — intro beside tables, Users inset, findings recaps, and five-stat rows staying inside the page.
The PDF is generated with WeasyPrint (a print engine, not a browser). A few honest limits:
- Charts that use JavaScript on screen (for example ApexCharts on a logged-in preview) are drawn as non-JS SVG/CSS twins in the PDF so pages are not blank.
- The first page of a long table keeps the left-hand intro; later pages continue the table in the same right-hand column.
- On Windows, WeasyPrint needs GTK libraries on
PATH. If Generate PDF fails with a message about the PDF engine and GTK, that is an environment install issue, not a broken report.
The logged-in /reports/<id>/preview/ URL still works for bookmarks (Back to builder only — no Print button). Prefer the builder canvas and the downloaded PDF for sign-off.
How to export a PDF and what to check
- Click Generate PDF in the builder header.
- Wait for the status to finish (plan usage limits apply).
- Download the file and open it in a PDF viewer — do not rely on the canvas alone.
- Skim every chapter page, not just the cover.
Before you send it, confirm the file is the pinned audit you meant (client name, date, and hubs), and that empty modules are hidden rather than printed as blank chapters.
Sharing via Audit Public Link
The client-facing path is the Portal Audit Public Link on the Portal Audits list (/audits/public/<token>/). Audits get a token by default.
Builder Share (a separate public HTML URL from Report Settings) was removed. Do not look for Enable public page on the report. If someone still has an old /reports/public/<token>/ bookmark, treat it as leftover — send the audit Public Link and the PDF instead.
What clients see vs what stays partner-only
Clients (Public Link + the PDF you send):
- The Portal Audit readout on the Public Link (the working audit view, including branding you set on the organization or client).
- The composed PDF: cover, contents, selected hubs, findings. Workflow Issues appear as counts. Users follow the list limit you set.
Partner-only:
- The Report Builder,
/reports/, Settings, Save, and Generate PDF. - Conflict reload messages, module config, and the ability to pin a different source audit.
- Map/Signals tools (Workflow Connections, map-pinned Workflow Health) that were never part of this audit’s Select Reports.
Quick pre-send checklist
- Users limit — default 20, or 0 for all; Showing X of N when truncated. Do not ship a 80-row dump unless the client asked for it.
- Workflow Issues — counts of workflows, not name chips. Readable on the first scan.
- Blank chapters — hide or remove modules whose snapshot is empty (“This snapshot does not include this data”).
- Five-stat rows — Ticket Automation / Deal Workflows KPI cards stay inside the page, not past the right margin.
- Cover chrome — logo, client name, and date as you intend; Prepared by / for fall back correctly.
- Pinned snapshot — Settings still points at the audit you just ran, not an older one.
- Public Link — works without a HubCreate login; you are not sending a builder URL.