Immutability
How resources keep their history, and how revisions let you make changes and roll them back.
Resources in withHuman are immutable. Once created, they remain part of your organization's history and cannot be permanently deleted through the app or API. You can update their configuration or archive them when they're no longer needed, while keeping a record of what came before.
A complete audit trail
The audit log records who did what, when, and to which resource. Those resources remain available, so you can follow a request from start to finish without losing its context.
For resources with revisions, that history includes the configuration used at the time. If you change an approval pipeline today, you can still see the exact rules it used to handle yesterday's requests.
Archiving
Archiving takes a resource out of active use and keeps its history available. An archived agent, for example, still appears in the record of its past requests and decisions.
Some resources can be restored later. See the Agents guide for how archiving and restoration work for agents.
Revisions
Most resources support revisions, including approval pipelines, escalation paths and webhook endpoints. Each revision is a numbered snapshot of the resource's configuration.
Every update saves a new revision and leaves the previous versions intact. You can inspect an earlier revision, activate it again or use it as the starting point for a new change.
Drafts and activation
Saving a revision doesn't make it live. You can keep it as a draft while the current revision stays active, then activate it when you're ready. Only one revision of a resource can be active at a time.
For approval pipelines, the newly active revision applies to new requests. Requests already being evaluated keep their existing rules, and requests waiting for human review aren't evaluated again. Requests already following an escalation path also keep the revision they started with.
Rollbacks
To return a live resource to an earlier configuration, activate that revision. This is a rollback. Newer revisions stay available, so you can switch back to one of them later.
A rollback affects future use of the resource. It doesn't reverse past decisions or undo actions an agent has already taken. The audit log records each activation and rollback.