Read and verify the Wally activity log

Every action Wally commits for your organization is recorded — from the chat drawer, from the Developer Console, and from your own API keys. Org admins and owners can read that ledger at **Admin -> Wally Activity**.

**What each row tells you**

- The tool that ran, and the exact document it wrote to.
- Who confirmed it, and when.
- Whether it came from inside the app or from an API key.
- Its position in the audit chain, and the first characters of its hash.

**Filtering**

Use the Status filter to separate committed actions from ones that were undone or whose undo window expired. Use the Tool box to narrow to one kind of action. The Chain filter shows only rows that have or have not been sealed into the chain.

**Verify chain**

Press **Verify chain**. The server walks your whole ledger in order and recomputes every hash from the record it is stored with.

- *Chain OK* means no row has been altered, removed or renumbered since it was written.
- *Chain broken at sequence N* names the exact row where the recomputation stops matching. That row, or the one before it, was changed after the fact.

This is the same verification the accounting ledger and the action-invocation ledger use, so a clean result means the same thing everywhere.

**"Recorded but not yet sealed"**

If a burst of activity arrives faster than the chain can be advanced, the action is still recorded in full — it is just not yet given a position in the chain. Those rows show as **unchained** and the verify result counts them separately. This is a throughput outcome, not a sign of tampering. Press **Seal unchained rows** to bring them into the chain, then verify again.