Revisions and moderation
Revisions
Every save of a record keeps the previous state. You can see what changed, who changed it and when, and you can restore an earlier version.
This is not an audit product bolted on afterwards — it is how records are saved, so it covers every content type including the ones you create tomorrow.
The activity trail
Beyond content, the platform keeps a trail of what happened in each agenda: a stock movement, a sent invoice, an imported documentation set, a changed permission. Every agenda has one from the day it ships.
Notes belong with the trail
Agendas carry notes as well as events, so the reason for something sits beside the record of it. A trail that records what happened but never why is half a trail.
Moderation
A content type can require review before publication. States and the transitions between them are configured — draft, in review, published, archived — and permissions decide who may make each transition.
Back office → Content → Moderation for the queue, System → Workflows for the states themselves.
Approvals
Beyond content, business documents can require approval — the four-eyes rule. An order above a threshold, a purchase invoice, a discount: configured per document type, with the approver's decision recorded in the trail.
Deletion
Deleting is deliberately rare in this platform. A documentation file removed from a repository unpublishes its page and keeps its content and revisions. A taxonomy term nobody uses is reported, not deleted. The reasoning is the same in both cases: an unpublish is recoverable in a minute, a delete costs a restore from backup.