Audit to Sheets — Setup & Usage

Vincent Jay

27 Jan 2026 — 1 min read

Release Note:
All write operations now generate human-readable audit rows in a Google Sheet, making audit data quickly accessible to Ops without requiring a backend.

Context

Auditing changes to licenses and configurations required digging through logs or building a dedicated backend. With this feature, all writes are appended directly to a Google Sheet in a readable format. Ops teams can now view and analyze audit trails immediately.

How It Works

Google Sheet Setup
- A sheet is prepared with the following headers:
  timestamp | actorEmail | licenseId | action | beforeSummary | afterSummary | correlationId
- This structure ensures each action is captured comprehensively and consistently.

Writer Endpoint

A Google Apps Script Web App (or internal sheet relay) accepts POST requests and appends new rows.
Security is enforced by limiting access to our domain or service account.

GoLive - Reporting - Report Configuration

GoLive - Reporting - Taxlines Integration

How to complete a customer data erasure request

We can get customer data erasure requests from a couple different ways, such as an email from a customer, or from Shopify when a vendor requests a customer data erasure on their storefront. This guide will work for both scenarios. When a Shopify vendor selects "Erase Personal Data"

Approach: Improve Bot Discoverability with Search and Team Scoping

1. Global Bot Search Bar What: * Add a persistent search input at the top of the bot directory. * Search should match: * Bot name * Short description * Tags / keywords * Owner or team (optional enhancement) 2. Role-Based Bot Filtering What: * Automatically filter bots based on the user’s authenticated role, team, or department.