You need to know who did what, and when. The audit log is a permanent, searchable record of every significant action taken in your Yaplet account. It covers both what your team does — signing in, changing settings, exporting data — and what Yaplet does on its own, such as the nightly cleanups that remove old conversations. Nobody can edit or delete an entry, including you.
Open the audit log
Go to Settings → Workspace → Audit Log. Entries are listed newest first. It is not under Security, which trips people up — Security holds the visitor trust scoring, the audit log lives with your workspace settings.
The audit log comes with a paid plan, from Starter upwards, and with the free 14 days every new workspace starts with. On the plain free plan after those days it is switched off, and no individual module adds it, so if there is no Audit Log entry in your Settings menu that is why.
What each entry shows
| Column | Description |
|---|---|
| Event | What happened, in words (for example "Data exported", "Visitor data erased" or "Member removed"), with the kind of record affected and a shortened ID underneath |
| Done by | The email of the team member who did it, or "System" for automated events |
| Location | The country and the IP address the action came from |
| When | How long ago it happened, with the exact date and time underneath |
Location is hidden until you switch it on. If you are chasing an IP address mid-incident, open the Columns dropdown above the table and tick Location.
Click an event, or the View details icon at the end of its row, to open a side panel with the whole entry. Who shows the email (or Done automatically by Yaplet) plus the country, IP address and device. What shows the Event code (for example data.exported), the Resource type and the Resource ID — click the copy icon next to the ID to copy it. Details holds everything else the event recorded; switch between Fields and JSON. Previous event and Next event (or the k and j keys) walk through the entries on the page.
What gets logged
- Sign-ins — every sign-in is recorded as Signed in (event code
user.signed_in), along with the method used (for example password or Google). - Team and permissions — a member added, updated, enabled, disabled or removed, and a pending invitation edited before it was accepted.
- Boards and tickets — a board exported, imported, duplicated or deleted, a ticket deleted, and a whole ticket column cleared.
- Data exports — every CSV export of your organization's data (
data.exported). - Visitor erasures — every permanent deletion of a visitor's data (
visitor.erased), including how many chats and messages went with it. - Visitor bans — a visitor banned or unbanned (
visitor.banned,visitor.unbanned). - Subscription events — a subscription created, updated, canceled or reactivated, and modules or volume tiers changed.
- Phone numbers — a number purchased or released.
- Newsletter — contacts imported, exported, bulk-deleted, or moved to a different state, and a campaign launched, paused, resumed or canceled.
- Blocked words — every change to your organization's blocked-word list.
- Widget, workflows and AI sources — a widget updated, a workflow switched on or off, and an AI training source added or updated.
- DPA and account — the Data Processing Agreement being signed, and the account being deleted.
- API keys — a key created, regenerated or deleted, and a key's AI access switched on, off or changed.
- Changes made by AI — every change, delete and send that Yaplet or an AI app connected to your account makes, shown as AI change or, in red, AI delete or send. The entry names the person the AI acted for, the action, the record and the connection (Yaplet itself, the app's name or the API key's name). The values the AI sent are not stored, and anything the AI only read is not logged.
- Automatic deletions — the nightly retention cleanups write an entry whenever they remove something: old conversations, old Yaplet chats, empty chat records, and idle anonymous visitors. Because they run every night, this is a routine line item rather than a rarity. See What Yaplet deletes automatically.
Search and filter
Use the search box to find entries by user email or resource ID. Click Show filters to narrow the log by Action, User email, Resource type or Resource ID, and use the date range to narrow things down to the window an incident happened in. The log opens on the last month, and you can look back up to 92 days at a time. Click a column header to change the sort order.
Retention
Audit log entries are kept for the lifetime of your account and are never deleted automatically — including the entries generated by data erasures. The record saying "visitor erased" survives even though the visitor's own data is gone, which is exactly what makes it useful as proof. The page itself shows the last month by default and up to 92 days at a time.
Who can see the audit log
The menu entry and the page are gated on one permission, called Audit Log. Once your plan includes the audit log, owners and admins always have it, because they bypass the per-member permissions. Anyone else sees it only if you switch that permission on for them — so it is not owner-only, and you can give a compliance colleague read access without making them an admin.