General settings: how settings are organised¶
Applies to: school Owners and staff with settings permissions; SuperAdmin. Last reviewed: 2026-11-18.
This is the entry page of the DriveFlow settings reference. It explains where settings live, who can change them, and the rules that apply to all of them. The pages that follow list every setting one by one.
This reference describes each setting: what it does, where to find it, who can change it, its default, and what a change affects. The step-by-step procedures for the features themselves are in the feature guides, which each page links to.
The pages of this reference¶
| Page | Covers |
|---|---|
| Company settings | The school's name, contact details, address, logo, terms and conditions |
| Branch settings | Branches, the main branch, enabling and disabling |
| Country and currency | Country, currency, time zone, language, date format, VAT |
| User and role settings | Users, branch access, roles, permissions |
| Training settings | Licence codes, training packages, package items, testing centres, documents |
| Scheduling settings | Lesson length, booking window, working hours, booking rules |
| Notification configuration | Channels, notification types, reminders, quiet hours, the school's email server, integrations, the notification log |
| Payment settings | Overdue rules, payment reminders, online payments |
| Security settings | Sign-in, sessions, "remember me", passwords, lockout, student portal access |
| Subscription settings | The school's plan, add-ons, billing; what the SuperAdmin sets |
| Settings not exposed in the UI (internal documentation) | Configuration and fixed values that have no screen |
The whole reference is also available as one document: DriveFlow settings reference.
Three places a setting can live¶
| Where | Examples | Who changes it | Takes effect |
|---|---|---|---|
| In the application, per school (stored in the database) | Working hours, notification switches, overdue rules, the school's SMTP server | The school, in Settings | At once, or on the next run of the job that uses it. No restart. |
| In the application, for the platform (stored in the database) | Built-in role permissions, gateway fee rates, a school's plan | The SuperAdmin | At once. No restart. |
| In the server configuration or in the code | Session length, password rules, platform email server, plan prices, trial length, job schedules | A developer or server administrator | After a restart of the API, or after a new version is deployed |
Most security and platform settings are in the third group. They are listed in Settings not exposed in the UI (internal documentation).
The Settings page¶
Menu: ADMINISTRATION > Settings (/settings). The menu item is shown to users with the Settings.View permission.
The page is headed Settings, with the line "Manage your driving school, users, email, billing and system preferences." It shows one card per settings area. A card is shown only if the user has the permission in the table.
| Card | Card text | Opens | Shown with permission | Reference page |
|---|---|---|---|---|
| Organisation | Manage company details, contact information and branches. | /settings/organisation |
Company.View | Company, Branch |
| Users & Access | Create users, assign roles and manage access to your organisation. | /settings/users |
Users.View | User and role |
| Roles | Create roles, assign permissions and manage access levels. | /settings/roles |
Roles.View | User and role |
| Driving School (chip "Core") | Configure courses, packages, licence codes and pricing. | /settings/driving-school |
Settings.View | Training |
| Scheduling | Configure availability, booking rules and working hours. | /settings/scheduling |
Scheduling.View | Scheduling |
| Payments | Overdue rules and payment reminder emails. | /settings/payments |
Settings.View | Payment |
| Notifications | Control email and system notifications for your organisation. | /settings/notifications |
Notifications.View | Notification |
| Security | Manage authentication, passwords and security settings. | /settings/security |
Always shown | Security |
| Documents | Configure student documents and document requirements. | /settings/documents |
Settings.View | Training |
| Configure SMTP settings and email communication. | /settings/email |
Email.View | Notification | |
| Integrations | Connect external services and platforms to DriveFlow. | /settings/integrations |
Settings.View | Notification |
| Subscription | Manage your DriveFlow subscription and selected plan. | /settings/subscription |
Subscription.View | Subscription |
| Billing | Manage DriveFlow billing, invoices and usage information. | /settings/billing |
Subscription.View | Subscription |
| System | Notification log: every email, SMS and WhatsApp message sent. | /settings/system |
Settings.Manage or Notifications.View | Notification |
Screenshot to be added
Screen: Settings page. Should show: all cards as seen by a school Owner.
For a SuperAdmin only four cards are shown: Users & Access, Roles, Security and Subscription. See the SuperAdmin guide.
Notes on the cards
- The Security card has no permission check, so every user who can open the Settings page sees it.
- The System card is shown to a user who has only Settings.Manage, but the page behind it needs Notifications.View. Such a user sees the card and then "You don't have access to this page".
- The Documents card opens a page that only says "This section is not available yet."
Who can change settings¶
Important
Access is by permission, not by job title. The table shows the defaults of the built-in roles. A SuperAdmin can change the built-in roles, and a school can create its own roles, so a live system may differ. Settings > Roles shows the current state.
| Permission | What it allows | Owner | Administrator | Manager | Instructor | Receptionist | Finance | Viewer |
|---|---|---|---|---|---|---|---|---|
| Settings.View | Open the Settings page; view Driving School, Payments, Integrations | Yes | Yes | No | No | No | No | No |
| Settings.Manage | Change licence codes, packages, testing centres, payment rules, online payments, integrations | Yes | Yes | No | No | No | No | No |
| Scheduling.View | View scheduling settings | Yes | Yes | Yes | Yes | Yes | No | Yes |
| Scheduling.Manage | Change scheduling settings | Yes | Yes | Yes | No | No | No | No |
| Notifications.View / .Manage | View / change notification settings; view the notification log | Yes | Yes | No | No | No | No | No |
| Email.View / .Manage | View / change the school's email server | Yes | Yes | No | No | No | No | No |
| Subscription.View | View the plan, billing and invoices | Yes | Yes | No | No | No | No | No |
| Subscription.Manage | Change plan, buy and cancel add-ons, enter a referral code | Yes | No | No | No | No | No | No |
| Users.View | View users | Yes | Yes | No | No | No | No | No |
The Owner role always has every permission and cannot be changed. Other permissions that matter for settings (Company.View, Company.Edit, Branches.View, Branches.Create, Branches.Edit, Users.Create, Users.Edit, Users.Disable, Users.Delete, Roles.View, Roles.Create, Roles.AssignPermissions, Roles.Delete) are held by the Owner and, by default, by the Administrator, except Roles.Delete.
When a user may view a settings page but not change it, the Scheduling, Notifications, Email and Payments pages show: "You can view these settings but not change them."
A user without the view permission who opens a settings address directly sees "You don't have access to this page".
Rules that apply to all settings¶
| Rule | Detail |
|---|---|
| Settings are per school | One school's settings never affect another school. Scheduling settings are per branch. |
| No restart | No setting on a Settings page needs a restart. |
| Permission changes sign users out | Changing a user's role or branch, or a role's permissions, ends that user's sessions. They sign in again and get the new access. |
| Subscription limits | Some settings only work when the plan includes the feature, or while an add-on is paid. The server then answers "{Feature} is not included in your {plan} plan. Upgrade your plan under Settings > Subscription to use it." or "{Feature} is a paid add-on. Activate or renew it under Settings > Billing to use it." |
| Ended subscription | When the subscription has ended, the menu shows only Renew Subscription and My Profile, and the server answers "Your subscription has ended. Renew it under Settings > Subscription to continue using DriveFlow." Subscription and Billing stay open. |
| No history | Changing a setting overwrites the old value. There is no change history and no audit log. |
| No import or export | Settings cannot be exported, copied to another branch or school, or reset to defaults with one click. |
Limitations and notes¶
SettingsNavigation.razor,Smtp.razorandSmtpSettingsForm.razorin the settings folder are empty placeholder components. They are not used.- The mobile app has its own booking settings page with the same fields as Settings > Scheduling. It was not examined for this reference.
No history
Changing a setting overwrites the old value. There is no change history, no audit log and no one-click reset to defaults.
Related articles¶
- Company settings - the school's identity
- User and role settings - users, roles and permissions
- Scheduling settings - booking rules and working hours
- Security settings - sign-in, sessions and passwords
- Subscription settings - plan, add-ons and billing
- Roles and permissions - the permission model in detail