Audit Log

Track important actions across your organization — user changes, board and ticket deletions, data exports, visitor erasures, subscription events, changes made by AI, and more.

Overview

The Audit Log gives you a searchable record of significant actions that happen in your Yaplet organization. Every entry captures who did what, when, and from where — helping you stay on top of security, compliance, and team activity. You'll find it at Settings → Workspace → Audit Log.

Viewing the Audit Log requires the Audit Log permission (listed under Settings in a member's permissions).

What Gets Logged

Yaplet automatically records events such as:

  • User actions — logins, permission changes, profile updates
  • Data operations — CSV exports, visitor erasures
  • Boards — a board being exported (including whether the reporter's personal details and the activity logs were included in the file), imported, duplicated or deleted
  • Tickets — a ticket deleted, or a whole column cleared. Only deletions are recorded here; everyday ticket edits and moves are not written to the Audit Log
  • Subscription events — plan changes, billing updates
  • API keys — a key created, regenerated or deleted, and a key's AI access (MCP) setting changed ("API key AI access changed")
  • Changes made by AI — every change, delete and send that Yaplet or a connected AI app (through the MCP server) makes in your account, shown as AI change or, in red, AI delete or send. See below
  • Automated processes — the nightly data-retention cleanups, logged as "System": expired conversations, expired Yaplet conversations, empty conversations and idle visitors

Log Entry Details

The log is a table with these columns:

ColumnDescription
EventWhat 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 byEmail of the user who performed the action, or "System" for automated events
LocationThe country and IP address the request came from. This column is hidden by default; switch it on from the Columns dropdown
WhenHow long ago it happened, with the exact date and time below it

Click an event, or the View details icon at the end of its row, to open a side panel with the whole entry:

  • Who — the email (shown as Workspace member), or Done automatically by Yaplet for system events, plus the Country, IP address and Device (for example "Chrome on Windows")
  • What — the Event code (e.g., data.exported, visitor.erased, board.deleted, tickets.deleted, data_retention.auto_delete), the Resource type (e.g., visitor, export, chat, board, board_tickets) and the Resource ID
  • Details — everything else the event recorded. Switch between Fields and JSON, and copy it with Copy. An event with nothing extra says This event recorded no extra details.

Use Previous event and Next event (or the k and j keys) to walk through the entries on the page.

Changes made by AI

Whenever Yaplet or a connected AI app creates, updates, deletes or sends something, one entry is written here:

  • Done by — the person the AI acted for: the person using Yaplet, the person who connected the app, or the person who switched the API key's AI access on
  • Event — AI change for creating and updating, AI delete or send for a permanent delete or a message to someone outside your team
  • Details (open the entry) — the action's name and plain title (for example tickets.update, "Update ticket") and the connection: Yaplet itself, the app's name, or the API key's name
  • Resource type / Resource ID (in the entry's side panel) — the record the AI acted on

The values the AI sent are not stored in the entry, because they can contain personal data. Reads — anything the AI only looked at — are not logged.

Shift changes are tracked separately

Changes to a shift are not written here — apart from the AI change entry above when an AI made them. Each shift keeps its own history — who changed what, and the old and new value — which you open from the shift itself. That history also covers shift changes made through Yaplet or a connected MCP client: they are attributed to the signed-in person, and the AI change entry here shows that an AI made them, so an assistant can never make an untraceable change.

Filtering and Sorting

Use the built-in filters to narrow down log entries (the Show filters / Hide filters button toggles them):

  • Action — pick one type of event, or All actions
  • User email — filter by who performed the action
  • Resource type — pick the kind of resource involved, or All resource types
  • Resource ID — find the entries for one specific record
  • Date range — the log opens on the last month, and you can look back up to 92 days at a time

The log is sorted by date (newest first) by default, and you can switch the order from the column headers.

© 2026 Yaplet. All rights reserved.