What the assistant changed
Anything the assistant actually did leaves a receipt — a card naming the change, who made it, when, and whether it can still be reversed.
What this does
Section titled “What this does”The assistant makes changes on your behalf, which raises an obvious question: what did it actually do? Receipts answer it in two places.
- Recent changes — the second tab of the assistant panel, wherever you open it. What was changed from here, most recent first.
- What the assistant changed — the full page at
/dashboard/assistant/changes, for everything changed through the assistant anywhere in the organization. It’s linked from the panel’s tab; there’s no sidebar entry.
The full page groups receipts into Still undoable by you, Waiting for a second approver, Applied, and Undone.
Undo a change
Section titled “Undo a change”Open Recent changes in the assistant panel and choose Undo on the receipt.
Undo is not a general “revert” button. It exists only where the change has a real inverse — creating something can be deleted, renaming something can be renamed back. Where no genuine inverse exists, the receipt says why instead of offering a control that would fail:
| Message | What it means |
|---|---|
| Only the person who made this change can undo it. | Undo is restricted to whoever ran it. |
| Already undone. | It was reversed — including by a double-click, which only ever produces one reversal. |
| Too long ago to undo. | Past the 24-hour window. |
| This can’t be undone automatically. | The change has no inverse. Reverse it by hand where you made it. |
| This change didn’t complete. | It failed, so there’s nothing to reverse. |
Undo runs from the assistant panel, not from the full changes page — the reversal is performed where the conversation is.
Receipts are not the audit log
Section titled “Receipts are not the audit log”This distinction matters, and the page itself says so:
This is not the audit log. Receipts are written by the browser that ran the action, so treat them as a convenience rather than proof — the audit trail is the record of account.
Use receipts to see what just happened and to reverse it. Use the audit log when you need the authoritative record — it is written server-side, hash-chained, and covers changes made anywhere in the product, not only through the assistant.
Both exist because they answer different questions. A receipt answers “what did I just do, and can I take it back?”. The audit log answers “what happened in this organization, provably?”.
Reference
Section titled “Reference”| Field | Meaning |
|---|---|
| Done | Applied successfully |
| Waiting for a second approver | Queued as an approval request — nothing has changed yet |
| Undone | Reversed |
| Failed | Did not complete |
| Reversal | This receipt is the undo of an earlier one |
| Undo window | 24 hours from when the change ran |
| Who may undo | Only the person who made the change |
| Retention | 180 days, purged weekly |
Troubleshooting
Section titled “Troubleshooting”A change I made isn’t in the list. Receipts cover changes made through the assistant. Anything you did by hand in the product is in the audit log, not here.
Undo is missing on a receipt. That change has no automatic inverse. Reverse it where you made it — the receipt names what was touched.
The receipt says “Waiting for a second approver” and nothing has changed. That’s correct. It’s an approval request, not a completed change. See Approvals.
Two people see different receipts. The undoable bucket is per-person, because only the person who made a change may undo it. Everyone with permission sees the applied and queued changes for the organization.