Skip to content

Roles and permissions

Applies to: Owner, Administrator (managing roles); all roles (reference); developers (how it is enforced). Last reviewed: 2026-11-18.

A permission is one right, such as "Register new students". A role is a named set of permissions. Every user has one role. This page lists the roles that exist, the complete default permission set of each, how a school creates its own roles, and how permissions are enforced.

The roles that exist

DriveFlow has nine built-in roles. They are created when the platform starts and are shared by every school.

Role Purpose Can a school assign it to a user? Can its permissions be changed?
SuperAdmin The DriveFlow platform operator. Belongs to no school. No No (locked): always everything
Owner The person who registered the school. No; given only by registration No (locked): always everything
Administrator Runs the school day to day. Yes Only by a SuperAdmin
Manager Runs operations: students, lessons, scheduling, leads. Yes Only by a SuperAdmin
Instructor Gives lessons. Yes Only by a SuperAdmin
Receptionist Front desk: registers students, books lessons, takes payments. Yes Only by a SuperAdmin
Finance Invoices, payments, refunds, financial reports. Yes Only by a SuperAdmin
Viewer Read-only. Yes Only by a SuperAdmin
Student Student portal access. No; given only by a portal invitation No (locked): always nothing

In addition, each school can create custom roles that only that school sees and manages.

Roles that do not exist

  • There is no "Admin" role. An older built-in role called "Admin" is removed automatically when the platform starts, and anyone who held it is moved to Administrator. (A school may create its own custom role named "Admin"; that is left alone.)
  • There is no "Branch Administrator" or "Branch Manager" role. To make someone the administrator of one branch, give them the Administrator role (or a custom role) and set their user's Branch to that branch. See User management.

Locked roles

SuperAdmin, Owner and Student are locked:

  • They are hidden from a school's Roles page and from the role list when creating or editing a user.
  • A user holding one of them keeps it; the Role field on the Edit User dialog is greyed out.
  • Their permissions never change. On every start the platform gives Owner and SuperAdmin every permission, including newly added ones, and strips every permission from Student.

A student's access to the portal comes from the Student role itself, not from permissions.

Default role-permission matrix

This is the complete default set, taken from the platform's seed data: all 83 permissions against every built-in role. Y means the role has the permission.

SuperAdmin is not shown as a column: it has every permission and, on the server, passes every permission check regardless. Student has none.

Category Permission (code) What it allows Owner Administrator Manager Instructor Receptionist Finance Viewer Student
Dashboard View Dashboard (Dashboard.View) View the dashboard. Y Y Y Y Y Y Y -
Students View Students (Students.View) View students. Y Y Y Y Y Y Y -
Students Create Students (Students.Create) Register new students. Y Y Y - Y - - -
Students Edit Students (Students.Edit) Edit student information. Y Y Y Y Y - - -
Students Delete Students (Students.Delete) Delete students. Y Y - - - - - -
Instructors View Instructors (Instructors.View) View instructors. Y Y Y Y Y Y Y -
Instructors Create Instructors (Instructors.Create) Create instructors. Y Y - - - - - -
Instructors Edit Instructors (Instructors.Edit) Edit instructor information. Y Y - - - - - -
Instructors Delete Instructors (Instructors.Delete) Delete instructors. Y Y - - - - - -
Vehicles View Vehicles (Vehicles.View) View vehicles. Y Y Y Y Y Y Y -
Vehicles Create Vehicles (Vehicles.Create) Add vehicles. Y Y - - - - - -
Vehicles Edit Vehicles (Vehicles.Edit) Edit vehicles. Y Y - - - - - -
Vehicles Delete Vehicles (Vehicles.Delete) Delete vehicles. Y Y - - - - - -
Courses View Courses (Courses.View) View student courses. Y Y Y Y Y - - -
Courses Create Courses (Courses.Create) Start new courses for students. Y Y Y - Y - - -
Courses Edit Courses (Courses.Edit) Edit student courses. Y Y Y - Y - - -
Courses Delete Courses (Courses.Delete) Delete student courses. Y Y Y - Y - - -
Lessons View Lessons (Lessons.View) View lessons. Y Y Y Y Y Y Y -
Lessons Create Lessons (Lessons.Create) Schedule lessons. Y Y Y Y Y - - -
Lessons Edit Lessons (Lessons.Edit) Edit lessons. Y Y Y Y Y - - -
Lessons Cancel Lessons (Lessons.Cancel) Cancel lessons. Y Y Y - Y - - -
Lessons Reschedule Lessons (Lessons.Reschedule) Move a lesson to a different time slot. Y Y Y Y Y - - -
Lessons Manage Lessons (Lessons.Manage) Full control over lesson scheduling. Y Y Y - - - - -
Lessons Override Cancellation Notice (Lessons.OverrideCancellationNotice) Cancel or reschedule a lesson inside the branch cancellation notice window. Y Y Y - - - - -
Scheduling View Scheduling Settings (Scheduling.View) View branch scheduling settings and availability. Y Y Y Y Y - Y -
Scheduling Manage Scheduling Settings (Scheduling.Manage) Edit branch scheduling settings and working hours. Y Y Y - - - - -
Driving Tests View Driving Tests (DrivingTests.View) View driving tests. Y Y Y Y Y Y Y -
Driving Tests Create Driving Tests (DrivingTests.Create) Create driving tests. Y Y Y - Y - - -
Driving Tests Edit Driving Tests (DrivingTests.Edit) Edit driving tests. Y Y Y Y Y - - -
Driving Tests Delete Driving Tests (DrivingTests.Delete) Delete driving tests. Y Y - - - - - -
Calendar View Calendar (Calendar.View) View calendar. Y Y Y Y Y - Y -
Calendar Manage Calendar (Calendar.Manage) Manage calendar events. Y Y Y - Y - - -
Invoices View Invoices (Invoices.View) View invoices. Y Y Y - Y Y Y -
Invoices Create Invoices (Invoices.Create) Create invoices. Y Y - - Y Y - -
Invoices Edit Invoices (Invoices.Edit) Edit invoices. Y Y - - - Y - -
Invoices Delete Invoices (Invoices.Delete) Delete invoices. Y Y - - - - - -
Quotes View Quotes (Quotes.View) View quotes. Y Y Y - Y Y - -
Quotes Create Quotes (Quotes.Create) Create quotes. Y Y Y - Y Y - -
Quotes Edit Quotes (Quotes.Edit) Edit, send, accept, reject and convert quotes. Y Y Y - Y Y - -
Quotes Delete Quotes (Quotes.Delete) Delete draft quotes. Y Y Y - - - - -
Fleet View Fleet (Fleet.View) See every vehicle's kilometre logs, costs, fuel consumption, alerts and the fleet report. Y Y Y - - Y Y -
Fleet Log Kilometres (Fleet.Log) Record a vehicle's daily kilometres (instructors only for their own vehicle). Y Y Y Y Y - - -
Fleet Record Vehicle Expenses (Fleet.Expenses) Record fuel and other vehicle expenses with receipts (instructors only for their own vehicle). Y Y Y Y - Y - -
Fleet Manage Fleet (Fleet.Manage) Edit or delete anyone's fleet entries and set vehicles' service intervals. Y Y Y - - - - -
Instructor Earnings View Instructor Earnings (InstructorEarnings.View) See every instructor's share of the lessons they complete. Y Y Y - - Y - -
Instructor Earnings View Own Earnings (InstructorEarnings.ViewOwn) An instructor sees their own share of the lessons they complete. Y - - Y - - - -
Instructor Earnings Manage Instructor Earnings (InstructorEarnings.Manage) Set instructors' shares and mark earnings as paid. Y Y Y - - Y - -
Leads View Leads (Leads.View) View leads and enquiries. Y Y Y - Y - Y -
Leads Create Leads (Leads.Create) Capture new leads. Y Y Y - Y - - -
Leads Edit Leads (Leads.Edit) Edit leads, update their status and convert them to students. Y Y Y - Y - - -
Leads Delete Leads (Leads.Delete) Delete leads. Y Y Y - - - - -
Payments View Payments (Payments.View) View payments. Y Y Y - - Y Y -
Payments Create Payments (Payments.Create) Record payments. Y Y - - Y Y - -
Payments Edit Payments (Payments.Edit) Edit payments. Y Y - - - Y - -
Payments Refund Payments (Payments.Refund) Refund payments. Y Y - - - Y - -
Reports View Reports (Reports.View) View reports. Y Y Y - - Y Y -
Users View Users (Users.View) View organisation users. Y Y - - - - - -
Users Create Users (Users.Create) Create users. Y Y - - - - - -
Users Edit Users (Users.Edit) Edit users. Y Y - - - - - -
Users Disable Users (Users.Disable) Enable or disable users. Y Y - - - - - -
Users Delete Users (Users.Delete) Delete users. Y Y - - - - - -
Roles View Roles (Roles.View) View roles. Y Y - - - - - -
Roles Create Roles (Roles.Create) Create roles. Y Y - - - - - -
Roles Edit Roles (Roles.Edit) Edit roles. Y Y - - - - - -
Roles Delete Roles (Roles.Delete) Delete roles. Y - - - - - - -
Roles Assign Permissions (Roles.AssignPermissions) Assign permissions to roles. Y Y - - - - - -
Company View Company (Company.View) View company information. Y Y - - - - - -
Company Edit Company (Company.Edit) Edit company information. Y Y - - - - - -
Branches View Branches (Branches.View) View branches. Y Y Y - - - - -
Branches Create Branches (Branches.Create) Create branches. Y Y - - - - - -
Branches Edit Branches (Branches.Edit) Edit branches. Y Y - - - - - -
Branches Delete Branches (Branches.Delete) Delete branches. Y Y - - - - - -
Documents View Documents (Documents.View) View documents. Y Y Y Y Y - Y -
Documents Manage Documents (Documents.Manage) Manage documents. Y Y - - Y - - -
Notifications View Notifications (Notifications.View) View notification settings. Y Y - - - - - -
Notifications Manage Notifications (Notifications.Manage) Manage notifications. Y Y - - - - - -
Email View Email Settings (Email.View) View email settings. Y Y - - - - - -
Email Manage Email Settings (Email.Manage) Manage email and SMTP settings. Y Y - - - - - -
Subscription View Subscription (Subscription.View) View subscription information. Y Y - - - - - -
Subscription Manage Subscription (Subscription.Manage) Manage subscription and billing. Y - - - - - - -
Settings View Settings (Settings.View) View settings. Y Y - - - - - -
Settings Manage Settings (Settings.Manage) Manage system settings. Y Y - - - - - -
Audit Logs View Audit Logs (AuditLogs.View) View the audit trail of user activity. Y Y Y - - - - -

Totals: Owner 83, Administrator 80, Manager 44, Instructor 18, Receptionist 33, Finance 21, Viewer 14, Student 0.

What the defaults mean in practice

  • Administrator has everything except three: Delete Roles, Manage Subscription and View Own Earnings. Only the Owner can delete a custom role or manage the subscription and billing.
  • Manager, Instructor, Receptionist, Finance and Viewer do not have View Settings, so they have no Settings menu item.
  • Receptionist has Create Payments but not View Payments: a receptionist sees only the payments they recorded themselves.
  • Finance has no Calendar and cannot create or edit lessons or students; it has view-only access to instructors, vehicles, lessons and driving tests so that it can open every report.
  • Instructor can create, edit and reschedule lessons but not cancel them.
  • Viewer can open the lists and reports but has no create, edit or delete permission at all.

The matrix can differ on a live system

Note

The table shows the defaults in the code. They are applied only when a built-in role is first created, and afterwards only for newly added permissions. If a SuperAdmin removes or adds a permission on a built-in role, that change stays and affects every school. The Roles page always shows the real, current set.

Who can manage roles

Action Permission Built-in roles that have it by default
Open the Roles page, view any role's permissions View Roles (Roles.View) Owner, Administrator
Create a custom role Create Roles (Roles.Create) Owner, Administrator
Change a custom role's permissions Assign Permissions (Roles.AssignPermissions) Owner, Administrator
Delete a custom role Delete Roles (Roles.Delete) Owner
Give a role to a user Create Users / Edit Users Owner, Administrator

View roles

  1. In the left menu click Settings.
  2. Click the Roles card. The page Roles & Permissions opens.

Screenshot to be added

Screen: Roles & Permissions page. Should show: role cards showing the Built-in and Custom chips and the Manage/View Permissions buttons.

A school sees one card for each of Administrator, Finance, Instructor, Manager, Receptionist and Viewer, followed by its own custom roles. Each card shows:

  • the role name and how many of your school's users hold it;
  • a Built-in chip or a Custom chip;
  • up to five permission categories the role covers, and "+N" for the rest, or "No permissions assigned.";
  • View Permissions (built-in roles) or Manage Permissions (your custom roles).

View Permissions opens the full list, read-only, with the note: "This built-in role is shared by all schools and can only be changed by the platform administrator. Create your own role if you need different permissions."

Create a custom role

  1. On Roles & Permissions click Create Role.
  2. Enter a Role Name, for example "Operations Manager".
  3. Tick the permissions the role should have. They are grouped by category; each shows its name, a description and its code.
    • Select all permissions (switch at the top) ticks or clears everything.
    • Select all (category) permissions ticks or clears one category.
    • The chip at the top shows how many are selected.
  4. Click Create Role. You see Role created successfully.
  5. Assign it: Settings > Users & Access, create or edit a user, and choose the role. Custom roles are marked (custom) in the list.

Rules:

  • The name is required and at least one permission must be ticked.
  • The name may not be one of the nine built-in names, and may not repeat another of your school's roles. Two different schools may each have a custom role with the same name; they are separate roles.
  • A custom role belongs to your school only. No other school sees it.

Example

A school wants its senior instructor to cancel lessons and see the reports, which the Instructor role cannot. The owner clicks Create Role, names it Senior Instructor, ticks everything the Instructor role has (use View Permissions on Instructor as a guide) plus Cancel Lessons and View Reports, and clicks Create Role. She then edits the instructor's user and changes the Role to Senior Instructor (custom). The instructor is signed out and gets the new access at the next sign-in.

Change a custom role's permissions

  1. On the role's card click Manage Permissions.
  2. Tick or clear permissions.
  3. Click Save Changes. You see "(Role) permissions updated successfully."

Note

Everyone who holds the role is signed out and must sign in again to get the new set. If nothing actually changed, nobody is signed out.

Delete a custom role

No confirmation

A custom role is deleted immediately when you click Delete. There is no confirmation step.

  1. On the role's card click ⋮ then Delete.
  2. The role is deleted immediately; there is no confirmation. You see Role deleted.

A role that is assigned to any user cannot be deleted; move those users to another role first. Built-in roles cannot be deleted.

Messages you may see

Message Why
Role name is required. The name is empty.
Select at least one permission. No permission is ticked.
"(name)" is a built-in role name and cannot be used. The name is one of the nine built-in names.
A role with this name already exists. Your school already has that role, or a shared role has that name.
Your account is not linked to a school. The signed-in account has no school.
Built-in roles are shared by all schools and can only be changed by the platform administrator. Create your own role instead. You tried to change a built-in role.
The Owner role always has full permissions. / The Student role only gives access to the student portal and has no permissions. / The SuperAdmin role always has full permissions. Locked roles cannot be changed by anyone.
This role is assigned to users and cannot be deleted.
Built-in roles cannot be deleted. / You cannot delete this role.
Role not found. The role does not exist or is not visible to you.
Unable to load roles. / Unable to load permissions. / Unable to create role. / Unable to update permissions. / Unable to delete role. The request failed.

How permissions are enforced

On the server (the real boundary)

  • When a user signs in, the server reads the permissions of the user's role and writes them into the sign-in token together with the role name, the school and the branch.
  • Every API operation that needs a right declares it (for example creating a user requires Users.Create). A request without that permission in its token is refused.
  • Some operations accept any one of several permissions, and a few operations shared with the student portal let a student through for their own record while requiring the permission from staff.
  • A SuperAdmin passes every permission check.
  • An automated test in the code base checks that API controllers declare permissions.
  • Separately from permissions, the server refuses requests when the school's subscription has ended or the plan lacks the feature.

In the web application (convenience)

  • The left menu, the Settings cards and the buttons on each page are shown or hidden according to the same permissions.
  • Settings pages are wrapped in an access check; without the permission you see You don't have access to this page and the page does not load its data.
  • Hiding a button is never the only protection: the server checks again.

When a change takes effect

Permissions are fixed in the sign-in token, so a change only applies after the affected person signs in again. DriveFlow forces this: changing a user's role or branch, or changing the permissions of a role, ends the sessions of everyone affected (within about a minute), and they are returned to the sign-in page.

flowchart TD
    A["Role (set of permissions)"] --> B[User signs in]
    B --> C[Token carries role, permissions, school, branch]
    C --> D[Menu and buttons shown from the token]
    C --> E[Server checks each request]
    D --> F[Role or permissions changed]
    F --> G[Sessions ended] --> H[Sign in again]

Limitations and notes

  • A school cannot change the built-in roles. If a built-in role almost fits, create a custom role.
  • Roles cannot be renamed and cannot be copied. To "rename", create a new role, move the users, and delete the old one. To base a role on a built-in one, tick the same permissions by hand.
  • Deleting a role has no confirmation step.
  • A role can include permissions for features the plan does not include. The permission then has no effect until the plan includes the feature.
  • Permissions that exist but are not used anywhere that could be found in the API or the web pages:
  • AuditLogs.View: there is no audit log at all: no database table, no API and no screen (AuditLog is an empty class).
  • Courses.View, Courses.Create, Courses.Edit, Courses.Delete: the course operations check the Students permissions instead.
  • Roles.Edit: changing a role uses Roles.AssignPermissions; there is no other role edit.
  • Branches.Delete: branches cannot be deleted.
  • Permissions used only to show or hide things in the web application, with no matching server check found: Dashboard.View (the Dashboard menu item) and Calendar.Manage (calendar actions, as an alternative to Lessons.Manage).
  • The permission descriptions in the matrix are the texts shown in the role dialog. What each permission unlocks on each screen is documented with that screen.
  • SuperAdmin behaviour (documented fully elsewhere): a SuperAdmin sees every role including the locked ones and every school's custom roles (the chip shows the school's name), can change the permissions of the six non-locked built-in roles for all schools at once (which signs out every holder in every school), and creates shared roles rather than school roles.