PacketChatDocs

Administer PacketChat#

Administrators manage users, centrally held provider accounts, model discovery, usage, audit records, and failed background work. Use a dedicated administrator account and keep provider-side budgets independent from PacketChat reporting.

Before you start#

  • Sign in as an administrator through HTTPS.
  • Confirm database, Redis, and object-storage readiness.
  • Prepare a secure delivery channel for invitations or configure Resend.
  • Record the provider-side budget and owner for each API key.

Manage users#

Create a user directly when the administrator can deliver an initial password securely. Use an invitation when the recipient should choose the password. Use a password-reset link for recovery.

With manual email delivery, copy the generated link from the administrator response and send it through an approved channel. Links expire according to the configured invitation or reset lifetime.

After changing a user’s access, verify the result with a separate browser session. Retain or export required business records before removing access.

Manage providers and models#

  1. Open Admin → Providers.
  2. Register an account and test its credentials.
  3. Run discovery and review the returned model set.
  4. Send a controlled chat request.
  5. Record the account owner and provider-side spending limit outside the key.

Provider accounts are installation-wide. Enabled users can spend through the models made available by those accounts. Use separate provider accounts when teams require different budgets or revocation boundaries.

Re-running discovery reconciles enabled bindings with the provider’s current list. Review the result before and after key rotation.

Monitor the installation#

  • Usage shows recent token and cost records. Provider-reported usage is preferred; some totals are estimated and unknown models may have no cost.
  • Audit records security and administration events.
  • Operations shows background job failures.
  • Approvals shows action requests and decisions.

Use provider billing as the source of truth for spend. PacketChat’s usage view is an operational aid, not an invoice.

Verify#

  1. Invite a test user and complete the invitation.
  2. Confirm the test user sees only intended administration surfaces.
  3. Send one message and find its usage entry.
  4. Perform one reversible admin change and find its audit event.
  5. Confirm failed ingestion work appears in Operations.

If it does not work#

Symptom Check Recovery
A new user cannot sign in Whether the account was activated as well as created See Common failures
A model is configured but never offered Whether the provider is reachable and the model enabled Configuration alone does not make a model available
Monitoring shows nothing Whether the installation is actually serving traffic See Check readiness
A removed user retains access Whether their session was revoked as well as the account Sessions outlive account changes until revoked
  • First run — initialise the first administrator and account.
  • Troubleshooting — login, provider, and worker failures.