The audit log

The audit log records who did what in your organization: sign-ins, members and licenses, API keys, saved views, exports, widgets, webhooks, scorecards and plan changes — and every time CapitolMath staff opened or changed the organization. It's there so an Owner, an Admin or your auditor can answer "who changed this, and when?" without asking anyone.

Owners and Admins read it from Organization → Audit log, under Activity, which shows the newest entries — changes to the organization's settings and its workflow among them; select Open the full log and export it → for all of them, with filters and the CSV download. Team members can't see it: it's a record of everyone's activity across the organization.

What's recorded#

Each entry says When, Who — a member, An API key, CapitolMath (automatic) or CapitolMath staff — What, what it was done To, and the network address it came From. Most actions succeed; one that failed or was refused is marked so. Select an entry to see its detail, including which fields changed.

Filter the log by kind of action, by who acted, by outcome (Succeeded, Failed, Refused) and by dates From and To.

What's deliberately not recorded#

• What anyone looked at. Nothing records which bills, legislators or hearings someone opened, or what they searched for. A log of every bill an organization read would be a record of its strategy — valuable to an attacker and discoverable in litigation — so it isn't kept at all. Exports are recorded, because they're data leaving CapitolMath.
• The values themselves. An entry says a saved view, a name or an email address changed, not what it now says — the detail shows "changed (the value isn't recorded)". Invitations are recorded by a fingerprint of the address, never the address.
• Secrets. No API key, webhook signing secret or password is ever written to the log.
• Who views your widgets. Embedded widgets don't track the people who see them, and the log doesn't either.

CapitolMath staff access#

When CapitolMath staff open your organization for support, change its details or status, or correct public data your organization relies on, it's written to your log, not only to ours. The CapitolMath staff access bar at the top of the log counts those entries; select Show only staff access to list them. If there have been any in the period your plan keeps, the Organization page says so too.

Entries can't be changed#

Neither you nor CapitolMath can edit or delete an entry. Each one is chained to the one before it, so a removed or altered entry would show. Once a day, a fingerprint of the log is also published in a public repository; once yours is included, the log page offers Download the proof and a standalone verifier to check it with, independently of CapitolMath.

How far back it goes#

Your plan decides how far back the log reaches — see Audit log kept for in Plans and what they include. The log page shows the window and the date it starts from. Moving to a plan with a longer window shows older entries again: they're never deleted while the organization is open.

Exporting it#

• Download CSV on the log page exports the entries matching your current filters. The file holds ids rather than names.
• GET /v1/audit-events delivers the log to a security tool by API, with ids rather than names. It needs an API key given the Read the audit log permission, which only an Owner or Admin can give a key, on a plan that includes the audit-log API (Developer and above). If the key's creator stops being an Owner or Admin, the key loses that permission. See Authentication and permissions and the API reference.