A version records what a piece of content looked like at a given moment and who changed it. You see what applied before, compare two states and go back to an earlier one if a change didn't work out.
In CIRO NOISE, versions aren't limited to the wiki. Tasks, quotes and invoices, pitch pages, concept boards, brand kits and Instagram carousels have a version history too. The same rules apply to all of them.
How versions are created in CIRO NOISE
CIRO NOISE saves automatically every one to two seconds while you write. So that this doesn't produce hundreds of versions, the rule is: if the same person saves again within 10 minutes, CIRO NOISE updates the current version instead of creating a new one. One working session becomes one version.
Saving explicitly, publishing, sending and restoring, on the other hand, always create a version of their own that is never overwritten later. If nothing in the content changed, no new version is created.
Compare and restore
In the version history you see the person and time for each version and can read what changed. Anyone who may edit the content can restore it. Restoring is itself a new version, so nothing gets lost there either.
There's one limit in finance: an issued invoice, an accepted or declined quote or a document in a locked period can't be reset to an older state, because German bookkeeping rules (GoBD) don't allow it.
An everyday example
Pascal shortens the wiki page "Sales onboarding" and accidentally deletes the section on accounts. The next day Kira opens the version history, sees in Pascal's version what was removed and restores the previous day's state.