Glozr docs
/

Platform admin

Platform admin overview

The platform admin console at /admin is where operators manage plans, monitor workspace usage, retry failed jobs and support customers through impersonation. Access is gated by users.role = super_admin; everyone else gets a 404 — the route doesn't even exist as far as they're concerned.

Purpose

The admin is intentionally minimal. It's a operator console for the people running the Glozr installation, not a customer-facing surface. If a feature can live in the workspace UI, it does; only platform-wide concerns end up here.

Granting super admin access

Super admin is not assignable through any UI. Use Artisan tinker to flip the column directly:

php artisan tinker --execute 'User::where("email", "[email protected]")->update(["role" => "super_admin"]);'

Demoting works the same way — set role back to user.

Sidebar sections

The sidebar groups ten management areas:

  • Dashboard — top-line KPIs and system health.
  • Workspaces — every customer workspace, with usage and plan state.
  • Users — global user list, including super-admins and impersonation entry points.
  • Agents — every agent across every workspace (read-only).
  • Conversations — recent activity, filterable by workspace.
  • Leads — cross-workspace lead volume.
  • Plans — pricing tiers and Stripe sync. See Plans & Stripe sync.
  • Subscriptions — active subscriptions and renewal state.
  • Usage — aggregate workspace usage versus quotas.
  • Queue failures — failed background jobs. See Health & failed jobs.
  • Site health indicator. A color-coded pill in the header summarising job failures, integration config, and service availability.
  • Notifications. Split between critical health alerts and a 24-hour business feed (new signups, subscriptions, leads).
  • Global search. Cross-resource keyword lookup, opened with the / keyboard shortcut.

Customer support tools

Impersonation. Admins can assume a user's identity inside their workspace while preserving audit trails. A persistent banner reminds you you're impersonating, so destructive actions don't slip through.

Daily admin digest. An opt-in email (sent at 09:00 UTC) summarises new signups, new workspaces, new subscriptions, and active conversations for the previous 24 hours.

Audit trail

Every admin action writes to the audit_logs table for forensic review. There is no browsing UI for it in v1 — query the table directly when you need to look something up.

Note. Impersonation is logged with the original admin user's ID alongside the impersonated user's ID, so audit lookups always show who did the action, not just as whom.