Publish a report by period

Editions publish a report once a month, quarter or year. Each one keeps its figures, has a permanent link, and joins an archive readers can browse.

An edition is a report frozen for one period, with a link that keeps working. Use them for anything you put out on a rhythm, such as a monthly report, where people need to go back and read what March said.

Without editions, a report's links always show its latest version. With them, links still open the latest by default, and every earlier period stays one click away.

Turn on editions

1. Open the report, and choose Editions in its … menu. You need edit access to see the page, and permission to publish to turn them on.

2. Under Publish, choose Each month, Each quarter or Each year. Quarters and years follow your organization's fiscal year.

3. If the report is already published, choose the period it covers under What's published now covers. You can pick from the last 12.

4. Choose Turn on editions.

Halo starts building that first edition. If the report isn't published yet, your next publish starts them.

Publish an edition

1. On the Editions page, choose Start and the next period, such as Start April 2026. The editor opens with an Editing April 2026 badge, and its dates read as of that period's last day.

2. Choose Publish, then Publish now…, and Publish as April 2026.

There's no picker for the period: each publish goes out as the period after the latest edition, or the one holding today if it's the first. Publishing doesn't wait for the period to end: the dialog warns you, such as "November 2026 hasn't ended yet", and lets you go ahead. You can also schedule a publish, and the schedule says which period it will be.

Someone who can't publish uses Request publishing as usual, and the request names the period. See Approval.

Readers stay on the edition before until the new one's figures are built. Its row on the Editions page says Building, then Published. If it says Didn't build, whoever published gets a notification, and links keep showing the edition before. Someone who can publish can choose Try again, or publish again, which goes out as that same period.

Each row also has Open and Copy link, with who published it and when, and a … menu for correcting or withdrawing it.

Dates that won't follow your editions

An edition reads as of its period's last day, so a date that's written down, or that names the period before, goes on showing the wrong period. When the draft has one, the editor's top bar says so, such as 2 dates to check. It looks for:

• fixed dates inside the next edition's period;

• the period before used as its own: Last month on a monthly report, Last quarter on a quarterly one, Last year on a yearly one;

• a calendar preset, such as Year to date, where your editions follow a fiscal year.

Each one offers the preset that reads the period, such as Use Month to date, or Leave it, which holds for this session. Change all does them together, and you can undo it. Saved charts placed from the library aren't checked here.

What stays and what doesn't

A reader of a public link can still change a filter, and Halo then asks current data for the answer. The page says so once: "Figures for changed filters come from current data."

To stop that, turn on Edition readers see only the published figures, at the foot of the Editions page. Filter controls then show their published values and can't be changed, and nothing asks current data. It's off by default, and in Halo Data and signed embeds the controls still work.

Reading editions

Periods are written 2026-03 for a month, 2026-q1 for a quarter, 2026 for a year, and fy2026-27 for a fiscal year that crosses January. A fiscal quarter is fy2026-27-q1.

On a public link, the period's name opens a menu of the six most recent, and All editions opens the archive. An older edition says "You're viewing March 2026", with a link to the latest, and every edition says "Data through" its last day at the foot of the page.

In Halo Data, someone who can edit the report gets See all editions on an earlier period.

In Halo Data, Print follows the edition you have open.

In email, PDFs and embeds

Scheduled email. The schedule's form asks which to send: The latest edition, on a schedule, or Each new edition, when it's published, which sends once for each. {edition} in a subject or message becomes the period's name, and the email links to that edition.

PDFs and files. A PDF with no filters and no member reads the edition's frozen figures, so it matches the link. A filtered or per-member PDF asks your data as of the period's last day, and its footer says "Figures come from current data, as of" that date. CSV and JSON files also read as of that date, and the email says so. In Halo Data, Download PDF is only offered on the latest edition.

Embeds. An embed opens the latest. To pin one, add ?edition=2026-03 to its address, or edition to <halo-report>. A signed embed's token decides, with its own edition claim. See The halo-report element and Signed embeds.

Link previews. Post an edition's link elsewhere and its preview names it, as "March 2026 · Monthly sales", with a picture from that edition.

Compare two editions

With two or more published, Compare editions on the Editions page asks for From and To, then opens the two side by side, as Compare does for versions. Above them, Figures lists what each scorecard and gauge published in either, with the change where both have a number.

Those numbers come from each edition's own stored figures, not current data. Live values in text aren't listed, and an edition built before figures were kept has none until it's corrected.

Correct an edition

If something in an edition is wrong, publish over it. You need permission to publish, and edit access to the report.

1. Fix the draft, and let it save.

2. On the Editions page, open the edition's … menu and choose Correct with the draft…. You can say What changed.

3. Choose Correct edition.

Its row says Correcting while the new figures build, and readers keep seeing the edition as it was. Once they're ready, the correction takes its address, and readers see "Corrected" with the date and your note at the foot of the page, and a Corrected badge in the archive. If the build fails, the edition stays as it was.

Undo correction…, in the same menu, brings back what it replaced, for 30 days.

Withdraw an edition

To take an edition down, choose Withdraw… in its … menu. You need the Manage content permission, and edit access to the report. You can give a reason, which readers see.

• It leaves the archive, and its address says "This edition was withdrawn", with your reason, and offers the latest edition.

• If it was the latest, the one before becomes the latest. If none is left, the report isn't published any more.

• Links stop reaching its figures within a minute, and a browser's own copy goes within another. Copies at the edge of Halo's network stay until they expire, out of reach.

Anyone who already read it may have kept it, so withdrawing can't take back what's been seen.

Withdrawn editions wait in their own list on the Editions page. Restore brings one back for 30 days. After that, or after Delete figures now, its figures are gone from storage and it can't be restored. Its period, its address and the audit log stay, and Publish again… publishes the draft as that period, with new figures. It returns to its address and the archive marked as corrected.

When a dataset changes under an edition

An edition's figures are what it published, so a later row policy can't reach them. So if you save a change to a dataset's row policies, or hide another field, and published editions read that dataset, Halo lists them and asks what should happen:

• Keep published: they go on showing what they published, including rows the change would now keep from someone.

• Withdraw them: as above, and you can restore them for 30 days.

Without the Manage content permission and edit access to a report, you can only keep its editions. The report's creator and whoever published the edition then get a notification, so they can withdraw it. Each choice is in the audit log. Labels and descriptions save as usual, and so does anything on a dataset no edition read. Restoring an older version of a dataset asks too, since it saves that version as the newest. If Halo saves the change but can't finish what you chose, it says so, and you can withdraw an edition from the report's Editions.

Turn them off

Turn off editions, at the foot of the Editions page, stops publishing by period. The latest edition stays published, past editions keep their figures, and nothing publishes as a period after that.

If something goes wrong