Skip to content

Platform settings

Applies to: SuperAdmin and the developer or administrator who deploys DriveFlow. Last reviewed: 2026-11-18.

This page explains where the platform-level settings of DriveFlow are kept. The short version: very few of them are in the application. Most are in the server's configuration or fixed in the code, and changing them needs access to the server, and often a restart or a new deployment.

No values of passwords, keys or connection strings are given in this documentation. Settings are described by purpose only; configuration details are covered in the internal technical documentation.

What the SuperAdmin can change in the application

Setting Where Guide
Permissions of the built-in roles Roles User management
Shared roles available to all schools Roles > Create Role User management
Gateway fee rates Sales Management > Gateway Fee Settings Gateway Fee Settings
Each salesperson's commission percentage and period Sales Management > Salespeople Salespeople
A school's plan, period, agreed amount, add-ons, SMS credits and referral code Subscriptions Subscription management
The SuperAdmin's own password and profile Settings > Security (/settings/security) and My Profile Security settings

That is the complete list. There is no "Platform settings" page.

What is in the server configuration

These are read from the API's server configuration when the API starts. None of them has a screen.

Important

A change takes effect only after the API is restarted.

Configuration area Purpose Who it affects
Database connection The SQL Server database, also used to store background job data Everything
Sign-in tokens How sign-in tokens are issued, including the length of a normal session and of a "remember me" session (30 days unless set) Every user
Platform email server The platform's own SMTP server. Used for all platform email and for every school that has not set up its own SMTP server. Every school on "DriveFlow default email"
Platform admin email Where DriveFlow's own alerts go, for example a new school registering The platform owner
Web app address The address of the web app, used for links and the logo in emails. Left empty, emails are sent without a sign-in link. Every email
Billing issuer The business printed on DriveFlow's subscription invoices: legal name, trading name, address, email, phone, website, registration number, VAT number, and the "VAT registered" switch and VAT rate Every subscription invoice issued from then on
DriveFlow's PayFast account DriveFlow's own PayFast merchant account, used for subscription and add-on payments Every school paying online
Other payment gateways Settings for Paystack, Flutterwave and Stripe. The gateways are registered in the code, but subscription payments use PayFast only. Not in use for subscriptions
SMS provider The platform's SMS provider account (Vodacom) Every school that sends SMS
WhatsApp The platform's WhatsApp Cloud API account Every school that sends WhatsApp messages
Meta (Facebook) app The Meta app used for Facebook and Instagram lead capture Every school using the Leads integration
Push notifications (Firebase) The Firebase credentials for push notifications. Push is off until this is set. Mobile app users

The full list, with every property and default, is in Settings not exposed in the UI (internal documentation).

Platform email

There is no page where the SuperAdmin sets the platform email server. It is part of the server configuration.

  • A school that chooses Use DriveFlow default email under Settings > Email sends through this server, with the platform's sender name and address.
  • A school that chooses Use my own SMTP server sends through its own server. If that school's stored SMTP password cannot be decrypted, DriveFlow falls back to the platform server and logs an error.
  • Welcome emails, password emails and DriveFlow's subscription invoices also use it.

The Email card on the Settings page is hidden for the SuperAdmin, because it holds one school's email settings.

What is fixed in the code

These need a developer and a new deployment to change.

Item Value today Where
Free trial length 14 days Registration code
Plans, prices, features See Subscription plans and add-ons Database seed data
Add-ons, setup fees, SMS bundles See the same page Database seed data
Leads and WhatsApp bundle discount 30% AddOnPricing
Maximum commission period 12 months Salesperson
Default commission for a new salesperson 20% for 12 months Salesperson
Maximum manual subscription duration 60 months SchoolSubscriptionAdminService
Password rules At least 8 characters with a digit, an upper-case letter, a lower-case letter and a symbol API start-up code
Password reset link lifetime 1 hour API start-up code
Account lockout ASP.NET Identity defaults (5 failed attempts, 5 minutes) Not configured, so the framework defaults apply
Background job schedules See below HangfireJobRegistration
The first SuperAdmin account Created at start-up Start-up code

Background jobs

DriveFlow runs its scheduled work with Hangfire, inside the API. The schedules are written in the code and cannot be changed in a setting.

Job Schedule What it does
lesson-reminders Every 15 minutes Sends lesson reminders that are due
driving-test-reminders Every 15 minutes Sends driving test reminders that are due
meta-lead-requeue Every 15 minutes Retries Facebook and Instagram leads that were not imported
subscription-expiry Every hour Marks subscriptions whose end date has passed as expired
document-expiry-reminders Daily at 07:00 Document expiry reminders
invoice-reminders Daily at 08:00 Marks student invoices overdue and sends payment reminder emails
report-generation Daily at 23:00 Report generation. What it produces was not examined for this guide.

Times are UTC

The daily times are those of the Hangfire scheduler. No time zone is passed when the jobs are registered, so Hangfire uses its default, UTC: 08:00 is 10:00 South African time.

Monitoring the background jobs is covered in the internal technical documentation.

Development tools

Development-only tools and the API documentation page are not available in production. They are covered in the internal technical documentation.

Start-up actions

Every time the API starts it:

  1. Applies pending database migrations. This is how new plans, prices and other seed data arrive.
  2. Creates any built-in role that is missing, and retires the old "Admin" role by moving its users to "Administrator".
  3. Creates the first SuperAdmin and the demonstration administrator accounts if they do not exist.
  4. Adds any permission that is new in this version.
  5. Gives default permissions to roles and permissions that were just created. Changes a SuperAdmin made to built-in roles are kept.
  6. Adds missing licence codes.
  7. Adds default scheduling settings to branches that have none.
  8. Registers the background jobs.

Audit logging

Warning

DriveFlow has no audit log.

  • The class AuditLog in the code is empty, and there is no audit table.
  • A permission named AuditLogs.View exists and is given to some roles by default. It appears in the role dialog under "Audit Logs". It unlocks nothing, because there is no audit log page.
  • What is recorded: every record stores who created it and who last changed it, and when (CreatedBy, CreatedOn, ModifiedBy, ModifiedOn). Only the latest change is kept, earlier values are not, and these fields are not shown on any page.
  • Some actions are written to the server log, for example manual subscription activations.
  • The Notification Log under a school's Settings > System lists messages sent. It is not an audit log.

If you need to know who changed what, the answer today is in the database columns and the server log files.

Limitations and notes

  • There is no maintenance mode, announcement banner or feature switch that the SuperAdmin can set.
  • Changing certain server secrets signs every user out, and losing the encryption keys makes stored SMTP passwords, PayFast keys, Facebook tokens and salespeople's bank account numbers unreadable. They must then be entered again. This is covered in the internal technical documentation.
  • The configuration of the web app project (for example the address of the API it calls) was not examined for this guide.

Every server-only setting is listed in Settings not exposed in the UI (internal documentation).