Admin Panel

The admin panel gives platform administrators full visibility and control over users, billing, AI configuration, and feature rollouts — all from a single, audited interface.

Admin overview

The admin panel is available at /admin. It is separate from the regular workspace experience and provides a platform-wide view across all users, workspaces, and subscriptions. The following routes are available:

User management

The user management screen at /admin/users provides a searchable table of all registered accounts. You can filter by plan, sign-up date, or ban status.

Searching users

Type any part of a name or email address into the search bar to filter the list in real time. Click a row to open the full user detail view.

Banning and unbanning

Banned users are immediately redirected to /banned on their next request and cannot access any workspace features. When banning, you must provide a reason — this is stored in the audit log and displayed on the ban screen if the user contacts support.

To unban a user, open their detail view and click Unban user. The restriction is lifted immediately.

Plan overrides

You can apply a plan override to any user. An override takes priority over the user's active Stripe subscription — useful for granting permanent access to team members, partners, or for support escalations. Overrides are clearly flagged in the user's detail view so they are not confused with paid subscriptions.

Granting trials

Trials give a user temporary access to a higher plan without payment. Set the plan level and expiry date from the user detail view. When the trial expires, the account reverts to its previous plan automatically.

AI configuration

The AI configuration screen at /admin/ai-config controls which AI provider and model power the WorkWiz Co-pilot across the entire platform. Changes apply to all users immediately — there is no gradual rollout at the provider level.

Supported AI providers:

• OpenAI — GPT-4o and other OpenAI models.
• Anthropic — Claude Sonnet and Haiku model family.
• Google Gemini — Gemini Pro and Flash variants.
• Zhipu AI — GLM model family for deployments requiring a China-region provider.

API keys are stored encrypted (AES-256-GCM) and are never returned in plain text after being saved. To rotate a key, simply paste the new key into the field and save — the old key is overwritten. Remove a key by clearing the field and saving.

Feature flags

Feature flags at /admin/feature-flags allow you to globally enable or disable any named feature without a code deployment. Each flag is identified by a string key that corresponds to a feature gate checked throughout the application.

Common use cases for feature flags include:

• Gradually rolling out a new feature by enabling it for a subset of users before enabling it globally.
• Emergency-disabling a feature that is causing errors or unexpected behaviour in production without deploying a hotfix.
• Hiding in-progress features from users while allowing internal testing on production data.

Toggling a flag takes effect on the next request that checks it — no restart or cache invalidation is required.

Admin audit log

The audit log is the authoritative record for accountability and compliance. Entries include:

• Actor (admin user who performed the action)
• Target (user, plan, feature flag, or configuration key affected)
• Action type (e.g., BAN_USER, GRANT_TRIAL, UPDATE_AI_CONFIG, TOGGLE_FLAG)
• Timestamp (UTC)
• Details (structured JSON payload with context-specific fields)

The log can be filtered by actor, action type, and date range. It is accessible from all admin pages via the Audit Log link in the admin sidebar.