Admin Console

The admin console turns the existing Admin APIs into one operator workspace. It covers users, credits, access codes, announcements, feedback, payments, AI tasks, and dynamic business configuration. Cloudflare remains the place for infrastructure logs, queue backlog, database inspection, and object storage.

Access

1. Run prepare-cloudflare and retain the one-time administrator credentials printed after the first successful initialization.
2. Sign in, then replace the generated password under Settings.
3. Open /{locale}/admin. The route redirects to /{locale}/admin/dashboard.

An unauthenticated visitor is redirected to login. A signed-in account without the D1 admin role receives 403 Forbidden.

Programmatic clients use OAuth grants with explicit scopes. There is no static admin API token.

Run opc auth connect --name <project> --server <origin> --scopes <scope-list>. The CLI prints an authorization URL. After the signed-in user reviews and approves the requested scopes in the browser, the CLI receives tokens through PKCE and stores them under that connection name and server origin. opc api request uses the selected connection. Settings lists these grants directly; revoking one invalidates both access and refresh immediately.

Pages

The locale can be en or zh. Language switching keeps the current admin path and query state.

Manage system settings

Open System settings and use the horizontal business tabs. General, Authentication, Email, Credits, Affiliate, Payment, AI, and Monitoring each have one explicit form. Monitoring owns the model and credit cost used by every completed monitor analysis. Saving one tab immediately changes subsequent requests in that domain. Storage upload policy comes only from ENV and does not appear here. An operation already in progress keeps the snapshot it started with.

Changing a field marks only the current tab as unsaved. Switching tabs or leaving the page requires choosing Save, Discard, or Cancel. Save validates and persists the current domain before navigating. Discard restores the last saved values and navigates. Cancel stays on the current form. There is no draft, publish step, automatic save, or cross-domain Save All.

Feature switches express the business action they control. Dependent fields appear only when the parent action is enabled. Registration owns its domain allowlist, beta-code requirement, email verification, and cooldown settings. Turnstile exposes only its runtime switch because deployment provisions its keys. Missing required fields are shown beside the affected control and the old configuration remains active. Secret fields never display plaintext. Choose Keep current value, Replace value, or Remove value before saving. Provider callback URLs are derived from the application URL and are read-only with a copy action.

Payment routing can use only platforms whose API and webhook credentials are configured. Country overrides use a searchable country selector. AI routing provides Balanced, Reliability, Speed, and Cost presets; selecting Custom is the only way to edit raw weights. AI task retention is configured separately from routing.

Payment platform credentials stay in System settings. Payment products and AI Providers are separate workspaces because operators change those collections independently and more frequently. Each entity uses a dedicated create, edit, and delete flow. Internal IDs are generated by the server. AI Provider types use workload and implementation names; models are entered as tags. Base URL starts with the implementation's official address and remains editable for proxies or compatible endpoints. A successful save replaces only the target row. Deletion requires confirmation. A stale version returns CONFIG_CONFLICT and requires an explicit refresh before editing again. Secret values are never shown.

Find a user and grant credits

1. Open /{locale}/admin/users.
2. Search by user name or email. The list shows each user's remaining credits and active monitor rule count from the assigned tenant shard. Internal user IDs are shown only as secondary references.
3. Open the user details to inspect that user's monitor URLs, conditions, states, and latest check results, then select Grant credits when needed.
4. Enter the amount and note, then choose Never expires, One week, or One month.
5. Review the selected user and grant details, then confirm.

The console creates the idempotency source reference internally. Operators do not enter or see source_id.

Open Credit activity from the sidebar or a user detail sheet to review balance changes for that user. Open Invitations to search inviter and invited-user relationships and inspect whether each reward has completed.

Generate access codes

Beta codes

Open /{locale}/admin/beta-codes, choose the quantity and optional expiry date, review the request, then generate. Copy the returned codes before leaving the result view.

The list distinguishes unused and used codes and shows the user when a code has been consumed.

Credit codes

Open /{locale}/admin/credit-codes, choose the quantity, credit amount, and optional expiry date, review the request, then generate. A code moves from unused to claimed and then granted as the cross-database credit flow completes.

Publish an announcement

1. Open /{locale}/admin/notifications.
2. Choose the notification type and enter its title and content.
3. Keep the audience global or find a target user by name or email.
4. Review the audience and content, then publish.

The history list supports type, audience, user, and date filters. Open an active notification to edit its audience, type, title, or content. Archiving removes it from every user's notification list while retaining the record in administrator history. Archived notifications cannot be edited or restored.

Investigate AI tasks

1. Open /{locale}/admin/ai-tasks.
2. Filter by task type, status, or user. Provider, model, task ID, and date filters are under advanced filters.
3. Open a task to inspect provider state, attempts, timestamps, stored output, and the last error.
4. Use the contextual Cloudflare links to continue in the related Queue, R2 bucket, or Worker dashboard.

The console is read-only for AI tasks. It does not retry, cancel, replay, or modify a task.

Review payments and feedback

Use /{locale}/admin/payments to filter transactions by user, provider, type, status, or date. Open a row to inspect the provider references and amounts. Payment actions such as refunding or resolving a dispute remain outside the console.

Use /{locale}/admin/feedback to filter by type, user, or date and open the full submission. The console does not add workflow states or edit user feedback.

Filters and shareable state

Common filters stay visible. Technical identifiers and date ranges are grouped under advanced filters. Active filters, page number, and the selected details are stored in the URL, so a filtered view can be refreshed or shared with another authorized operator. Use Reset filters to return to the default list.

Cloudflare handoff

Cloudflare links are placed beside the resource they represent:

A link is hidden when the required Cloudflare account or resource identifier is unavailable. Use the console for product state and Cloudflare for platform state such as logs, metrics, queue delivery, database queries, and objects.

Current scope

• Public assets remain API-only and have no admin page.
• Payments, feedback, and AI task operations are read-only.
• Codes cannot be revoked from the console.
• Active notifications can be edited or archived. Archived notifications remain in administrator history and cannot be restored.
• Fine-grained administrator permissions are not included. One D1 admin account owns browser access.

Troubleshooting

For API authentication details, see Authentication. For production resource setup, see Deployment.