Skip to main content
Regulated practices — law firms, accounting firms, and consulting practices working under client data agreements — need to demonstrate not just that access controls exist, but that those controls were actually enforced. Parlé writes every sensitive action across your organization to an append-only audit log, and rejects ordinary attempts to edit or delete an entry.

​
Reading the log

Org Admins can read their organization’s audit log in Org settings → Audit log.
Plan requirement. Reading and exporting the audit log is available on the Business plan and above, and only to Org Admins. On other plans the Audit log tab shows an upgrade prompt. Parlé records the same actions on every plan, and nothing already recorded is removed if a plan changes, so a later upgrade shows the full history.
The log shows your organization’s own entries only, newest first, as plain sentences such as who did what to which project. Each entry also shows the action code and, where Parlé has it, the IP address the action came from. Times are shown in your organization’s time zone (UTC if none is set).

​
Filters

Use the filters above the list and select Apply filters: The list loads a page at a time; select Show more for older entries. If a filter matches too much for Parlé to read in time, narrow the date range or add a filter.

​
Exporting

Select Export CSV or Export JSON to download the entries that match the current filters. One export holds up to 50,000 entries; if your filters match more, Parlé asks you to narrow the date range or add a filter.
  • CSV columns: Timestamp (UTC), Local time, Actor, Actor user id, Event, Action, Resource type, Resource, Resource id, Project, Project id, Changes, IP address.
  • JSON holds the same entries, with the filters used, the time zone and the time of the export.
  • The file is named like parle-audit-log-20261024-153000.csv.
Export is a download from the screen. There is no audit API, no SIEM feed and no webhook: those are not available.

​
Reading the log is recorded too

Opening the audit log and exporting it are themselves written to the audit log, against the person who did it. The entry records the filters used and how many entries were returned, never the entries themselves.

​
What an entry shows, and what it leaves out

  • Who. A member of your organization is named. An action Parlé itself carried out is shown as Parlé. A person who is not a member of your organization, including Parlé staff acting on a support request, is described rather than named, and their user id and IP address are withheld.
  • What changed. Where a setting changed, the entry lists the before and after values of a fixed set of safe fields. It never shows raw stored values, and never shows a credential.
  • Retention. Entries are kept indefinitely; there is no automatic deletion.

​
What the Audit Log Captures

Every message (inbound and outbound), configuration change, member change, budget change, context file edit, tool call, and API key rotation is written to the audit log. Broadly:
  • Membership events — user added to or removed from the org; user added to or removed from a project; role changed
  • File events — project file written or deleted; project context file (agent.md) edited
  • Budget events — project budget set or changed; spending caps changed
  • Provider events — AI model provider connected, disconnected, or its key rotated
  • Tool events — an integration connected, enabled on a project, or called in a conversation
  • Conversation events — messages sent and received
  • Data export events — an organization data export requested or downloaded
  • Admin actions — org settings changed; storage provider connected or disconnected
The audit log is not a payload store. For a tool call it records the tool’s name and category, whether it succeeded, failed or was cancelled, how long it took, and the size of the request and response — but never the request and response themselves. A tool’s arguments routinely contain your own documents, and because audit rows resist deletion, storing payloads there would put a second copy of your content somewhere Parlé’s own deletion paths cannot reach.

​
Append-Only Enforcement

The guarantee comes from how the log is enforced, not just how it is described. Two independent layers apply:
  1. The application layer. The repositories that write audit records expose no update or delete operation at all. No screen in the product, including the audit log screen, edits or removes an entry.
  2. The database layer. An INSTEAD OF UPDATE, DELETE trigger on the audit tables rejects both statements regardless of which account issues them. A direct SQL UPDATE or DELETE against an audit row is rejected, even from a connection that holds write permission on the table.
In practice this means a compromised Org Admin account cannot scrub activity from the log: there is no feature that would let it, and the database rejects ordinary writes even if there were.
What this does and does not guarantee. The trigger rejects ordinary writes — UPDATE and DELETE — but it does not protect against schema changes. A principal holding ALTER or CONTROL on the database could disable the trigger, drop it, or TRUNCATE past it. That is an accepted, deliberately higher bar: altering the record requires a deliberate, privileged schema change rather than a routine write, and is not something that can happen through the product. We would rather state that precisely than claim the record can never be changed by anyone under any circumstances.
If a client or regulator asks for evidence of your AI usage controls, an Org Admin can export the relevant window from Org settings → Audit log. The view and export are available on the Business plan and above.