Everything below lives on one page: Versions and sharing, from the Report tab of a project.
Issuing a version
Issuing takes the current state of the report and freezes it as a release, with a version identifier, a timestamp and the person who issued it. Continuing to work on the project does not alter that release.
This is what makes a shared report answerable months later: the version the committee read still exists, exactly as they read it.
What accumulates
Every issue is kept, newest first, with the working draft at the top of the same timeline so you can see how far ahead of the last issue you are.
Each issue carries a plain-language summary of what changed since the previous one — ratings that moved, elements added, rewritten or removed, and sections that arrived or went. Those sentences are counted from the two frozen documents when the version is issued, not estimated, so the numbers are exact.
Comparing any two versions
What changed opens a full comparison of any two versions, or of the draft against a version. It leads with the same summary sentences, then the counts, then the detail section by section, with rewritten prose marked word by word.
A version is only ever compared against another of the same edition. A board pack is a subset of the full report by design, so comparing the two would report the whole technical appendix as deleted every time.
Restoring
Any full issue can be rolled back into the working draft. Restoring does not delete the later releases; it brings an earlier state back to work on, and the history records that it happened. An audience edition cannot be restored — it contains a subset of the report, so restoring from it would discard the rest.
Sharing a specific version
A share points at one release, not at "the latest". An external reader's access does not silently change under them when you issue again — you decide whether to give them the newer version.
Because of that, an earlier issue stays readable by whoever holds it until you close it. The page states this at the top: how many people can open the report, how many of them hold a version you have since replaced, and how many of those have never been given the current one. Close the earlier issues takes that access back in one action.
Withdrawing a version
Withdrawing stops a version being readable by anyone outside your team. Links already sent say the report was withdrawn rather than failing, the version stays in the history with the reason recorded, and it can be reinstated.
Withdrawing and un-inviting are separate on purpose. Withdrawing closes the document and keeps the recipient list, so reinstating restores access to exactly the same people; Stop sharing removes the recipients and leaves the version readable to your own team. You can do both at once when that is what you mean.
Availability
Part of the plans that include report version history. Without it you keep one live issue — publishing again replaces it rather than adding to the history — and who can open that issue is still shown and controlled in the same place.