Administrator operations

Administrators support users and inspect redacted operational state. They do not inherit a user’s provider credentials, API keys, payment secrets, or raw provider responses.

Administrator UI

Open Admin → Operations to review counts, delivery failures, support requests, billing entitlements, and announcements. User ban/role changes, entitlement overrides, support transitions, and announcements require a human-readable reason and create an audit record.

Create temporary provider-test users only from Admin → New test user. Those accounts can use the separate temporary login; public email/password registration remains unavailable.

Administrator API and CLI

Create a named administrator API key in Admin → API keys. It uses the separate ata_ prefix. Configure the CLI without placing the raw value in source control:

export ADMIN_API_URL="https://threads-admin-api.ankk.app"
export ADMIN_API_KEY="<administrator-api-key>"

ankk-threads-admin dashboard
ankk-threads-admin user-ban <user-id> true \
  --reason "Confirmed provider support request"

Every mutation requires --reason; provide --idempotency-key when an external workflow must safely retry the same operation. The API records the actor, target, reason, before/after state, and idempotency key.