Skip to content

Platform administration

Becoming a platform admin, curating models, approving payments and watching jobs.

On this page

Platform admins operate ikazebot itself: they enable models, set plans and credits, approve payments and watch the background jobs. It is a property of a person, not a workspace role. It lives in the platform_admins table, which the API can read but never write, so nobody can promote themselves through the app.

Platform pages appear under Platform in the sidebar for admins only. Everyone else gets a 404 there from the API, whatever the sidebar shows.

Become a platform admin

The person must already have signed up. Then, from your machine:

  1. In ikazebot-server/.env.migrate, list the addresses as PLATFORM_ADMIN_EMAILS, comma-separated.
  2. Run:
bash
pnpm admin:grant

It connects as the superuser through MIGRATION_DATABASE_URL, skips anyone already an admin, and never revokes. Or by hand, as the superuser:

sql
INSERT INTO platform_admins (user_id, reason)
SELECT id, 'maintainer' FROM users WHERE email = '<their email>';

Platform → Models (/admin/models)

The catalog is synced daily from OpenRouter. Only enabled models can be picked for an agent.

  • Enable the models customers may choose. A fresh catalog enables only a small starter set.
  • Credits per reply default to what the price implies. Override a model's number to price it differently.
  • A model agents still use cannot be disabled. Move those agents first.

Platform → Workspaces (/admin/workspaces)

Set a workspace's plan, including the admin-only Enterprise, and grant credits. A plan change gives the new allowance for the rest of the month. Granted credits never expire.

Platform → Billing (/admin/billing)

Customers pay for orders by bank transfer, quoting the order's reference.

  1. 1Customer ordersreference shown
  2. 2Customer transfersquoting the reference
  3. 3Match it on your bank statement
  4. 4Approveplan or credits apply now

Approve applies the plan, for the months paid, or the credits immediately. Renewing early extends the plan. Reject needs a note explaining why. The bank details customers see come from BILLING_PAYMENT_INSTRUCTIONS on the server.

Platform → Jobs (/admin/jobs)

Every background queue: counts, connected workers, how long the oldest job has waited, and each job with its error and stack trace. Retry or remove from here. A queue with waiting jobs and no worker is flagged at the top: the worker is down, and sources will sit at "Queued" until it is back. Bull Board is also available at the API's /admin/queues.

Get started free — 50 credits a month