---
title: "Audit log and analytics"
description: "Inspect per-changeset audit history in each app, revert mistakes cleanly, and monitor usage trends across your organisation."
canonical: "https://grid82.com/docs/build/audit-and-analytics"
updated: "2026-11-20"
---

# Audit log and analytics

Grid82 tracks both **organisation-wide usage metrics** in the Studio and **record-by-record audit trails** inside every app.

## Organisation activity analytics

Open **Activity** in the Studio navigation to track activity across every suite and app over time: rows written, machine calls (API, CLI, and MCP), active apps, and workflow step consumption.

![Studio Activity analytics dashboard showing rows written and calls by machine charts](/docs/images/app/studio-analytics.webp)

_Studio Activity dashboard showing rows written, machine calls, and 30-day organisation trends_

Retention depends on your plan:

| Plan             | Detailed activity events kept | Daily aggregate history kept |
| ---------------- | ----------------------------- | ---------------------------- |
| **Free**         | 2 days                        | 30 days                      |
| **Starter**      | 7 days                        | 365 days                     |
| **Pro / Custom** | 90 days                       | 730 days                     |

## App audit log and changeset undo

Every record create, update, delete, SQL bulk write, or workflow mutation inside an app writes a changeset entry to the app's **Log** page in the Studio.

![Studio app audit log showing actor, surface, action, and timestamp columns](/docs/images/app/studio-audit-log.webp)

_Per-app audit log recording who made each write, from which surface, and which fields changed_

- **Full attribution.** Each log entry captures the acting user (or workflow name), the origin surface (`grid`, `api`, `cli`, `mcp`, `assistant`, `workflow`), timestamp, and exact before/after field values.
- **One-click revert.** A batch import of 500 records or a bulk `sql.execute` update is stored as a single changeset, so reverting it rolls back the entire batch in one transaction.
- **Trash recovery.** Dropped tables, fields, and apps remain recoverable from **Trash** for 30 days with their original IDs and links intact.
