Panelbotdocs
SearchStart free

Audit trail and accountability

Every diagnostic, change, and approval on your account is recorded in a trail you can review and export, including declined actions. It cannot be edited or deleted through the product.

If it happened, it is on the record

An automated assistant working on your servers should never be a black box. You should be able to answer, at any time, what Panelbot looked at, what it changed, who approved it, and what it refused to do. Panelbot keeps a complete record of exactly that, and it belongs to you. This page describes what the trail captures, why it can be trusted, and how you use it.

What gets recorded

Every meaningful thing Panelbot does on your account leaves an entry. The trail captures:

  • Every diagnostic check. The read-only inspections Panelbot runs to understand a problem are recorded, so you can see what it examined and what it found.
  • Every change. Any action that altered something on a server is logged, along with what it did and how it turned out.
  • Every approval decision. When a higher-impact change needed a person to sign off, the record shows who approved or declined it and when.
  • Every action Panelbot declined to take. This is the part operators tend to appreciate most. When Panelbot refuses a request, for example because an ownership check failed or a change was too impactful to take on its own, that refusal is recorded too. You can see not only what happened but what was prevented, which is often the more reassuring half of the story.

Taken together, these entries let you reconstruct any conversation’s technical side from start to finish, and connect a customer’s chat to the exact checks and changes it produced.

Why the trail can be trusted

A record is only worth as much as your confidence that it has not been quietly edited. Panelbot’s audit trail cannot be edited or deleted through the product. Entries are added as things happen and are never rewritten after the fact. Each entry is kept for 12 months and then removed automatically, so export anything you need to keep longer. Nobody, including us, goes back to tidy up history. That is what makes the trail dependable as an account of what actually occurred rather than a version of events that could have been smoothed over later.

This matters most in exactly the moments you would reach for it: a customer dispute, an internal review, or a “wait, what touched this account and when” investigation. Because the record cannot be altered through the product, it can settle those questions instead of adding to them.

Reviewing and exporting your trail

The trail lives in your dashboard, where you can review it directly. You can trace what Panelbot did across your servers and tie individual actions back to the conversations that prompted them, which is useful both for supporting a specific customer and for keeping an eye on the system as a whole.

The record is also yours to export. When you need the history outside the dashboard, for your own archives, a compliance request, or a deeper review, you can export your account’s audit trail and keep it wherever you need. Your data belongs to you, and that includes the full account of what was done with it. There is more on export and deletion rights in Data handling and privacy.

Accountability by design, not by policy

The point of all this is that accountability is built into how Panelbot works rather than promised in a document. The assistant cannot act without the action being recorded, cannot make a higher-impact change without an approval being recorded, and cannot refuse a request without the refusal being recorded. There is no path through the system that skips the ledger.

That is what lets you hand Panelbot real work on real servers and still be able to answer for everything it did. The record is complete, it is honest about what was declined as well as what was done, it cannot be rewritten through the product, and for the 12 months each entry is kept it is yours to read and to take with you.

Where to go next