Admin Console

Who can do what, how to manage your team, and how the activity log works.

Roles

Every teammate you invite is given one of five roles, each with a clear boundary:

RoleWhat they can do
AdminEverything, including cross-account operations in the separate platform admin tool used by our own staff.
Bot OwnerEverything within their own account, including billing and team management.
DeveloperFull access to developer tools: API keys, webhooks, ledger and usage, settlement, feature flags.
Integration PartnerThe same access as Developer. Meant for an outside team managing their own integration into your account.
Analyst / AuditorCan view everything above, but cannot change anything.

Read-only really means read-only. It is enforced twice: once in which buttons even appear on screen for that role, and again on the server when a request arrives. That second check matters, it means a read-only role cannot make a change by calling the API directly either, not just by clicking around the dashboard.

Managing your team

Invite a teammate and assign their role from the Team page in your dashboard. Each invitation is sent by real email and must be accepted before that person gets access. There are no nested sub-teams today, everyone you invite into your account sits on one flat team, distinguished only by their role.

The activity log

Every meaningful action inside your account is written to an activity log automatically: who did it, what they did, and when. Nothing in this log is auto-deleted.

An entry looks like this:

{
  "action": "api_key.revoked",
  "actorId": "user_8f2a1c",
  "outcome": "success",
  "resourceType": "api_key",
  "resourceId": "key_9d3e7b",
  "sourceIp": "203.0.113.42",
  "createdAt": "2026-07-29T18:04:31.000Z"
}

You can export your own account's activity log as CSV or JSON from the Logs page at any time, up to the most recent 10,000 entries.

Honest gap: the activity log is not tamper-proof the way the financial ledger is. The ledger uses a cryptographic chain, described in Settlement System, so an edited entry can be detected automatically. The activity log does not have that protection yet, entries are append-only by convention in the application code, but nothing at the database level stops a direct edit. Worth knowing if immutability of this specific log matters for your compliance needs.

Was this page helpful?