Reports saved from chat start life as drafts — real, re-runnable reports that have not been published to the team yet. Saving also keeps the governed method that knows how to run the report again. The draft report and its method are created together, so you do not have to match them up later.
Drafts live behind the Drafts filter on the Reports page, out of the main catalogue and sidebar, so work-in-progress never clutters what the team sees.
From the Drafts view, each draft offers:
- Open — preview it and check the numbers before anyone else relies on it.
- Amend with AI — describe a change in plain language, review the proposed change, then apply it to the same draft. The change is checked before it is saved; an amendment that would not run is rejected rather than saved broken.
- Publish — moves the report into the main catalogue and sidebar for everyone whose role allows it, and puts the matching governed method into service at the same time. Publishing is an administrator action.
- Archive — removes the draft from the working list when you do not need it. Archived reports stop appearing in the catalogue.
What publishing means
Publishing is one authorised act. The report and its governed method go live together; if the publish action cannot complete safely, the product does not publish only one half of the pair. You can fix the draft and try again.
A tidy habit
Chat makes saving easy, so drafts accumulate. A quick weekly pass — publish the keepers, archive the experiments — keeps the catalogue meaningful.