Platform overview for the SuperAdmin¶
Applies to: SuperAdmin only. Last reviewed: 2026-11-18.
The SuperAdmin is the platform administrator of DriveFlow: the person at the company that runs DriveFlow, not someone at a driving school. This page explains what a SuperAdmin is, what the SuperAdmin sees after signing in, and what the role can and cannot do.
What makes the SuperAdmin different¶
| School user | SuperAdmin | |
|---|---|---|
| Belongs to a driving school | Yes, exactly one | No. The account has no company and no branch. |
| Sees students, lessons, invoices | Those of their own school | None. School data is always filtered by school, and the SuperAdmin has no school. |
| Permissions | Those of their role | Every permission check on the server passes |
| Subscription | Limited by the school's plan and add-ons | Not limited by any plan |
| Menu | The school menu (MAIN, CRM, OPERATIONS, FINANCE, REPORTING, ADMINISTRATION) | One section: PLATFORM |
Two points are easy to misread
- Passing every permission check does not mean seeing every school's data. The SuperAdmin cannot open a school's students, calendar or invoices. Only the functions listed on this page work across schools.
- There is no "sign in as a school" function. The SuperAdmin cannot impersonate a school user.
Signing in¶
The SuperAdmin signs in on the same sign-in page as everyone else, with an email address and password.
After signing in, the SuperAdmin is sent to Users (/settings/users). The school dashboard at /dashboard redirects there, because a dashboard for no school would be empty.
The header shows DriveFlow Platform (all schools) where a school user sees their school's name.
Where the SuperAdmin account comes from¶
The first SuperAdmin account is created automatically when the API starts and no such account exists yet. It is only created when it is missing; later starts do not reset its password. How the account is set up on installation is covered in the internal technical documentation.
Important
Change the SuperAdmin password after the first sign-in. Use Settings > Security > Change Password (open /settings/security). See Security settings.
Adding another SuperAdmin¶
There is no screen for this. The Create User dialog always creates a user inside a school, and the SuperAdmin role is a locked role that cannot be chosen in the role list. A second SuperAdmin can only be added directly in the database (a user with no company, linked to the SuperAdmin role).
The PLATFORM menu¶
| Menu item | Opens | What it is for | Guide |
|---|---|---|---|
| Users | Users & Access (/settings/users) |
See every user of every school | User management |
| Roles | Roles & Permissions (/settings/roles) |
Change the built-in roles shared by all schools; see every school's custom roles | User management |
| Subscriptions | Subscription (/settings/subscription) |
Activate or upgrade a school's subscription by hand, mark manual payments as paid, manage add-ons and SMS bundles, apply a salesperson code | Subscription management |
| Sales Management | Seven pages under /sales |
Salespeople, referrals, commissions, gateway fees, reports and payouts | Sales Management |
| My Profile | /profile |
The SuperAdmin's own name and contact details | - |
Screenshot to be added
Screen: SuperAdmin home. Should show: the PLATFORM menu on the left and the header reading "DriveFlow Platform (all schools)".
The bottom of the sidebar shows "DriveFlow" as the organisation name, the text "Subscription" with "View subscription details" (a link to the Subscriptions page), the DriveFlow Help link and the application version.
The Settings page¶
The Settings page (/settings) is not in the SuperAdmin menu, but it opens if you type the address. For a SuperAdmin it shows four cards only:
| Card | Opens |
|---|---|
| Users & Access | The same page as the Users menu item |
| Roles | The same page as the Roles menu item |
| Security | Change your own password, links to Users and Roles, and the Student Portal list |
| Subscription | The same page as the Subscriptions menu item. For a SuperAdmin the card reads "Activate or upgrade a school's subscription." |
The other cards (Organisation, Driving School, Scheduling, Payments, Notifications, Documents, Email, Integrations, Billing, System) are hidden, because they are settings of one school.
What only the SuperAdmin can do¶
| Function | Where | Enforced by |
|---|---|---|
| Everything in Sales Management | Sales Management menu | [Authorize(Roles = "SuperAdmin")] on /api/admin/sales |
| Manage any school's subscription, manual payments, add-ons and referral code | Subscriptions | [Authorize(Roles = "SuperAdmin")] on /api/admin/subscriptions |
| Change the permissions of the built-in roles (Administrator, Manager, Instructor, Receptionist, Finance, Viewer) | Roles | Role service: built-in roles are editable by a SuperAdmin only |
| Create a role that is shared by every school | Roles > Create Role | Role service: a role created by a SuperAdmin has no school |
| See users, roles and instructor sign-in links of every school | Users, Roles, Instructor sign-in check | The controllers return all schools for a SuperAdmin |
| Add default scheduling settings to branches that have none | No screen. This also happens automatically each time the API starts; see Platform settings. | SuperAdmin role check |
| Bypass the cancellation notice when cancelling a lesson | Not usable in practice, as the SuperAdmin sees no lessons | Role check in the cancel-lesson handler |
Other server behaviour for the SuperAdmin role:
- Permission checks: any endpoint protected by a permission accepts a SuperAdmin.
- Subscription checks: the SuperAdmin is never blocked by an ended subscription or a missing plan feature.
- Mobile app: the SuperAdmin may sign in to the mobile app regardless of any plan. The mobile app has no platform screens, so this has no practical use.
- Background jobs: see Platform settings. Monitoring them is covered in the internal technical documentation.
What the SuperAdmin cannot do¶
These are stated plainly because a platform administrator would normally expect them:
| Not available | Detail |
|---|---|
| A list or directory of schools | There is no "Schools" page. Schools are found through the school box on the Subscriptions page. See Company management. |
| Activate or deactivate a school | A school has an Active flag, but nothing in the system changes it. |
| Edit a school's details | The Organisation page is hidden for the SuperAdmin and its API works only for the caller's own school. |
| Impersonate a school or view its data | Not built |
| Create, edit, disable or delete users | The buttons are shown, but the server refuses these actions for an account with no school. See User management. |
| Change plan prices, plan limits, features, add-ons or SMS bundle prices | These are fixed in the database seed and migrations. There is no screen and no API. See Subscription plans and add-ons. |
| Change platform email, payment gateway, SMS or WhatsApp credentials | These are in the server configuration files. See Platform settings. |
| View an audit log | There is none. See Platform settings. |
| Platform-wide reports on schools or revenue | Only the Sales Management dashboard and monthly report exist. See Platform reports. |
A typical week for the SuperAdmin¶
| Task | Where |
|---|---|
| A school paid by EFT: activate its plan | Subscriptions > choose the school > Upgrade Subscription |
| A pending EFT arrived | Subscriptions > choose the school > Payments pending > Mark as paid |
| A school wants the Leads add-on or an SMS bundle and pays by EFT | Subscriptions > choose the school > Add-ons |
| A new referral partner signs up | Sales Management > Salespeople > Add Salesperson |
| Check and approve new commissions | Sales Management > Sales Commissions |
| Pay salespeople at month end | Sales Management > Monthly Reports, then Commission Payments |
| A school was refunded | Sales Management > Sales Commissions > Refunded |
| A school asks why an instructor sees no lessons | Users > Instructor sign-in check |
The guide¶
| Page | Subject |
|---|---|
| Company management | Finding schools and what can be done with them |
| Subscription management | Manual activation, pending payments, add-ons, bundles |
| Subscription plans and add-ons | The plans and add-ons that exist and their prices |
| User management | Users, roles and permissions across schools |
| Platform settings | What is configured where, background jobs |
| Sales Management | Overview and dashboard |
| Salespeople, Customer Referrals, Commission management, Gateway Fee Settings, Monthly commission reports, Commission payments | The Sales Management pages |
| Platform reports | Reports available to the SuperAdmin |
| System settings reference | Every setting in DriveFlow |
Related articles¶
- Company management - finding schools and stopping access
- Subscription management - manual activation and pending payments
- User management - users and roles across schools
- Sales Management - salespeople and commissions
- Platform settings - what is configured where