User and role settings¶
Applies to: users with the Users and Roles permissions; by default the Owner and Administrator. SuperAdmin for built-in roles. Last reviewed: 2026-11-18.
This page lists the settings of a user account and of a role. The procedures for adding users and building roles are in the user management guides. For the SuperAdmin's cross-school view see User management for the SuperAdmin.
Users¶
Menu: ADMINISTRATION > Settings > Users & Access (/settings/users)
| Action | Permission |
|---|---|
| View the user list | Users.View |
| Create a user | Users.Create |
| Edit a user, send a new password | Users.Edit |
| Disable or enable a user | Users.Disable |
| Delete a user | Users.Delete |
All of these work only inside the user's own school.
Settings of a user¶
| Setting (label) | Required | What it does | Default | When it changes |
|---|---|---|---|---|
| First name | Yes ("First name is required.") | Shown in lists, the header and emails | - | A linked instructor profile is updated to match |
| Last name | Yes ("Last name is required.") | As above | - | As above |
| Yes ("Email is required.") | The sign-in name. Must not be used by any other DriveFlow account, in any school ("A user with this email already exists." / "Another user already uses this email."). | - | The user signs in with the new address from then on. A linked instructor profile is updated to match. | |
| Phone number | No | Contact number | Empty | - |
| Branch | No | See Branch | All branches | The user is signed out and gets the new branch at the next sign-in |
| Role | Yes ("Role is required." / "Please select a role.") | See Role of a user | - | The user is signed out and gets the new permissions at the next sign-in |
| Send a new password (edit only) | No | See Passwords | Unticked | The current password stops working |
| Status (Active / Disabled) | - | See Status | Active | Takes effect at the user's next request |
No restart is needed for any of these.
Branch¶
| What it does | Ties the user to one branch. A user with a branch sees that branch's data. A user on All branches sees data across the whole school. |
| Helper text | "Leave empty to give the user access to all branches." |
| Options | "All branches", then each active branch. The main branch is marked "(Main)". |
| Rule | The branch must be an active branch of the same school ("The selected branch is not available.") |
| Existing records | Not changed. Only what the user can see changes. |
Role of a user¶
| What it does | Gives the user the permissions of that role |
| Options | The built-in roles Administrator, Manager, Instructor, Receptionist, Finance and Viewer, plus the school's own roles, marked "(custom)" |
| Not offered | Owner, Student and SuperAdmin. These come from registration, the student portal invitation and platform setup. A user who has one of them shows the role read-only: "This role comes from registration and can't be changed here." |
| Number of roles | The dialog sets one role per user |
| Rule | "The selected role is not available." when the role is locked or belongs to another school |
Passwords set by an administrator¶
| New user | A temporary password is generated and emailed with a welcome message: "A welcome email with a password to sign in with will be sent to the user. They'll choose their own password the first time they sign in." |
| Existing user | Tick Send a new password and save. "A new password will be generated and emailed to the user. Their current password stops working, and they'll be asked to choose their own when they next sign in." |
| Effect | The user must choose their own password at the next sign-in. All of the user's existing sessions end. |
| If the email fails | The user is still created or updated. The failure is only written to the server log. Send a new password again. |
| Who sees the password | Nobody in the application. It is only in the email. |
The password rules themselves are in Security settings.
Status¶
| Disable | Confirmation: "Disable {name}? They will no longer be able to use DriveFlow." The user cannot sign in, and open sessions stop at the next request. Message "User disabled." |
| Enable | No confirmation. Message "User enabled." |
| Own account | "You can't deactivate your own account." |
| Records | Kept |
Delete¶
Confirmation: "Are you sure you want to permanently delete {name}?" The account is removed. Message "User deleted." Records the user created keep the user's id as their creator.
Warning
Deleting a user cannot be undone. Disable the user instead if you may need the account again.
Roles¶
Menu: ADMINISTRATION > Settings > Roles (/settings/roles). The page is headed Roles & Permissions.
| Action | Permission |
|---|---|
| View roles | Roles.View |
| Create a role | Roles.Create |
| Change a role's permissions | Roles.AssignPermissions |
| Delete a role | Roles.Delete |
Kinds of role¶
| Kind | Roles | Shown to a school | Who can change it |
|---|---|---|---|
| Locked | Owner, Student, SuperAdmin | No | Nobody. Owner has every permission, Student has none. |
| Built-in | Administrator, Manager, Instructor, Receptionist, Finance, Viewer | Yes, read-only, with the chip Built-in | The SuperAdmin only. The change applies to every school. |
| Custom | Roles the school created | Yes, with the chip Custom | The school |
A school that opens a built-in role sees: "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."
Settings of a role¶
| Setting | What it does | Rules | When it changes |
|---|---|---|---|
| Role Name | Identifies the role | Required. Not one of the nine built-in names ("... is a built-in role name and cannot be used."). Unique among the built-in roles and the school's own roles ("A role with this name already exists."). | A role cannot be renamed after it is created |
| Permissions | What holders of the role may see and do | At least one ("Select at least one permission.") | Every user holding the role is signed out, and gets the new permissions at the next sign-in. Only if the set actually changed. |
Deleting a role has no confirmation step
Only custom roles can be deleted, and only when no user holds it ("This role is assigned to users and cannot be deleted."). There is no confirmation step.
No restart is needed.
Permission categories¶
Permissions are grouped in the role dialog by category: Dashboard, Students, Instructors, Vehicles, Courses, Lessons, Scheduling, Driving Tests, Calendar, Invoices, Quotes, Fleet, Instructor Earnings, Leads, Payments, Reports, Users, Roles, Company, Branches, Documents, Notifications, Email, Subscription, Settings and Audit Logs. There are 83 permissions in all.
Permissions that exist but unlock nothing today:
| Permission | Note |
|---|---|
| AuditLogs.View | There is no audit log |
| Branches.Delete | There is no function to delete a branch |
| Courses.View, Courses.Create, Courses.Edit, Courses.Delete | Nothing checks them. Course screens and endpoints check the Students permissions instead. |
| Roles.Edit | Nothing checks it. Changing a role's permissions needs Roles.AssignPermissions. |
| Lessons.OverrideCancellationNotice | The cancellation notice is bypassed by role name (SuperAdmin, Owner, Administrator, Manager), not by this permission |
Default permissions¶
Defaults are given when a role is first created by the system. Afterwards only the SuperAdmin's changes count, and they survive restarts. Administrator has every permission except Roles.Delete, Subscription.Manage and InstructorEarnings.ViewOwn (80 of 83). The other built-in roles have narrower sets. The table of settings-related defaults is in General settings.
Instructor sign-in check¶
Where: Settings > Users & Access > Instructor sign-in check (/settings/users/instructor-links). Permission: Users.View.
A read-only list of instructor accounts and whether each is linked to its instructor profile. It has no settings. Statuses: Linked, Links on next sign-in, No instructor profile with this email, Several profiles share this email.
Limitations and notes¶
- The SuperAdmin sees all users but cannot create or change them. See the SuperAdmin guide.
- There is no setting for the number of users a school may have on this page. Plan limits apply to students, instructors, vehicles and branches.
- There is no per-user permission. Access is always through the role.
- A user cannot have access to some branches but not others. It is one branch or all.
Related articles¶
- User management - adding and managing staff users
- Roles and permissions - building roles
- Security settings - passwords, sessions and lockout
- Branch settings - the branches a user can be tied to
- User management for the SuperAdmin - the cross-school user list