Security & audit

Audit log & sharing

Read the org-wide audit log (Admin-only) with get_audit_log, and share a table link that respects roles.

The audit log answers "who changed what, when" across the organisation - from row-level edits up to org settings. It resolves each acting user's email so you can see who performed each action.

Read it

eddytor get audit-log
GET /v1/organisations/:id/audit
Authorization: Bearer edd_live_…
{ "tool": "get_audit_log", "arguments": {} }

Filter by table, action, and from/to timestamps.

Heads up

Reading the audit log is Admin-only across the CLI, REST, and MCP - a Builder can't read it. See access recap.

Audit log vs table history

Two complementary trails:

  • Table history - the Delta version log for one table (operations, metrics, timestamps).
  • Audit log - org-wide activity across tables, users, storage, and settings.

Leave good breadcrumbs

Add a comment to significant merge_rows writes - it lands on the table's version and makes both the history and an investigation far easier to read.

get_share_link returns a shareable link to a table - a quick way to point a teammate at it:

get_share_link(table="eddytor.cfg_xxx.<uuid>_products")

Good to know

A share link is a pointer to the table, not a bypass of permissions. Who can actually see or change the data is still governed by their role and any API-key scopes - sharing a link doesn't widen access.

On this page