Reviewing What Team Members Did
How Pilotbot keeps an audit trail of team actions so owners and managers can see who did what, and when.
Pilotbot Team
Author
On this page
When more than one person can act on your accounts, you want a record of who did what. Pilotbot keeps an audit trail of team actions so nothing important happens without a trace.
What the Audit Trail Covers
The trail records meaningful actions taken in your workspace — for example turning ads on or off and other operational changes — along with who performed them and when. It gives you accountability across your team without you having to watch over anyone's shoulder.
Who Can View It
Reviewing team activity is available to the Owner and to the Manager role. Traders, Viewers, and standalone Auditors can do their own work but don't manage the team's audit view. This keeps oversight in the hands of the people responsible for the workspace.
Using It in Practice
- Spot-check operations — confirm a teammate made a change you expected.
- Investigate a surprise — if an ad's state changed unexpectedly, the trail shows whether a person did it (and who) versus the system's own safety cascade.
- Build trust as you grow — as you add people, the record lets you delegate confidently.
A Note on Automatic Actions
Not every change is a person. Pilotbot's own safety rules — like switching the bot off for an ad that went offline on the exchange — are system actions, not team actions. The dashboard explains those where they happen, so you can tell an automatic safety step apart from something a teammate did.