Activity log

The dashboard's Activity page is an append-only record of every consequential change Flarelink has made in your Cloudflare account with your token — provisioning a project, deploying or redeploying an auth Worker, minting / rotating / clearing R2 credentials, attaching a custom domain, creating or deleting buckets, and config writes. Each entry shows the action, a short detail, and a timestamp. Nothing on the page can be edited or deleted.

It answers "what has Flarelink ever done in my account?" from inside the dashboard. It does not log routine reads (browsing tables, listing resources) — those don't change anything.

Why action-boundary logging instead of per-call? D1 queries are all POST under the hood, so reads and writes look identical at the API chokepoint — and the question you actually care about is "what changed." So Flarelink logs one row per consequential operation (matching how Cloudflare's own audit log records changes), and leans on the CF audit log for raw per-call detail. Related: What the token can do.