Seeing and undoing what Levi did

Levi, your AI teammate · nineloops support

The activity log in Settings, what each entry records, one click undo, undoing a whole instruction, and what cannot be taken back.

Every action Levi takes is written down at the moment it happens. Not a chat receipt that disappears when you close the conversation: a row in the database, with the records it touched.

Where to read it

Settings, then Levi activity. Owners and admins see everything Levi has done in the workspace. Everyone else sees everything Levi did as them. You can filter by outcome, by person and by app, and search what it did.

What each entry records

What it was asked to do: the exact request, in full.
What came back: the real result, rather than the model's description of it.
The app and the table it touched, and how many records.
Who it ran as, and when.
The outcome: done, failed, waiting for a person, blocked by your rules, or undone.
How the records looked immediately before the change, which is what makes undo possible at all.

Undo

Where an entry can be put back it has an Undo button. Something Levi created is undone by removing it. Something Levi changed is undone by writing the earlier version back. Removing a built tab is undone by bringing it back, records intact.

Undo runs with your own permissions, not with Levi's and not with those of whoever asked. If your role cannot edit those records, nothing is changed and it says so, rather than reporting a success that did not happen.

Undoing a whole instruction

One instruction can produce several actions. Where that happened the log groups them together, and you can undo the whole turn in one go. Anything in that group that cannot be put back is reported rather than skipped quietly.

What cannot be undone

Anything that reached a person. A sent email has arrived and a WhatsApp message has been delivered, so the entry is recorded and marked as not revertible rather than offering a button that would lie to you.
A change that touched more than 200 records at once. Past that no earlier version is kept, and the entry says so instead of pretending.
Anything that failed, was blocked, or is still waiting on a person, because nothing was changed in the first place.

Nothing can delete or rewrite an entry in this log, including Levi, which is blocked from writing to it at all. The same block covers the audit tables, billing, member roles and the permission matrix, so Levi cannot tidy up after itself or quietly widen its own access.

Still stuck?

Raise a ticket and a person who works on nineloops will pick it up.

<a href="/support">All support articles</a>