Platform administrator guide

Platform admin

Platform administrators (super admins) run the SaaS itself—not a single customer workspace. You manage all organizations, subscriptions, the public website, and deploy/maintenance tools. Customer owners use the workspace ERP; you use Platform admin under /admin.
Super admin only. These screens require the super_admin role. Regular organization owners and members never see Platform admin in the sidebar.

Sign in

  1. Open /admin/login or sign in at the main login with your super-admin email.
  2. After login you land on /dashboard (platform home) or go to /admin/organizations.
  3. The left sidebar shows Platform admin and Growth & Plan groups.

What you control

Organizations & tenants

Approve, activate, attach MySQL DB per workspace, run tenant migrations, open any org workspace.

Users & access

View all users; grant or revoke super admin.

Commercial

Packages, subscriptions, payment provider settings.

Marketing & support

Website content, contact inbox, platform-wide tickets, referrals.

Deploy

HTTP /system/* routes for migrations and seeds on production.

Admin guide map

All platform admin screens

Platform admin

Organizations

/admin/organizations

Tenants, DB credentials, activate, open workspace.

Users

/admin/users

All accounts; assign super admin.

Growth & Plan

Packages

/admin/packages

Subscription plans and limits.

Subscriptions

/admin/subscriptions

Active org subscriptions and checkout.

Plan & billing

/admin/billing

Payment gateway, currency, SaaS billing options.

Referrals

/admin/referrals

Referral rewards and attribution.

Referral codes

/admin/referral-codes

Create and manage promo codes.

Platform tickets

/admin/tickets

Support from all workspaces.

Contact messages

/admin/contact-messages

Inbound from marketing contact form.

Settings

/admin/website-settings

Logo, homepage, footer, WhatsApp, themes.

Daily checklist

  1. Review new organizations (pending approval if enabled).
  2. Check platform tickets and contact messages.
  3. Confirm subscriptions and failed payments in Subscriptions / Billing.
  4. After code deploy: run central + tenant migrations (see Deploy guide).