User management¶
Applies to: Owner, Administrator (and any custom role with the Users permissions). Last reviewed: 2026-11-18.
A user is a person who can sign in to DriveFlow. This page covers creating staff users, editing them, re-issuing passwords, disabling, enabling and deleting them, and how a user is connected to an instructor profile or a student record.
Who can do this¶
| Action | Permission | Built-in roles that have it by default |
|---|---|---|
| Open Users & Access, open the Instructor sign-in check | View Users (Users.View) |
Owner, Administrator |
| Create a user | Create Users (Users.Create) |
Owner, Administrator |
| Edit a user, send a new password | Edit Users (Users.Edit) |
Owner, Administrator |
| Disable or enable a user | Disable Users (Users.Disable) |
Owner, Administrator |
| Delete a user | Delete Users (Users.Delete) |
Owner, Administrator |
To reach the page from the menu you also need View Settings (Settings.View), because that shows the Settings menu item. The role filter on the page is filled from the roles list, which needs View Roles (Roles.View); without it you see "Unable to load roles." but the rest of the page works.
Rules that apply to every user¶
- The email address is the sign-in name and must be unique across the whole DriveFlow platform, not only your school.
- A user has exactly one role.
- A user has one branch or All branches. See Branch management.
- Users do not choose their first password. DriveFlow generates a temporary password and emails it; the user must choose their own at first sign-in.
- Users belong to one school. A user cannot be shared between schools.
Open the user list¶
- In the left menu click Settings.
- Click the Users & Access card.
Screenshot to be added
Screen: Users & Access page. Should show: the filter row and the user table with the row menu open.
The table shows User, Email, Branch ("All branches" when the user has no single branch), Role and Status (Active or Disabled). It lists every account of your school, including student portal accounts (role Student) and the Owner.
Above the table:
| Control | Use |
|---|---|
| Search users... | Filters by name, email or branch name as you type. |
| All roles | Filter by one role. The list contains the roles you may assign and your custom roles; Owner and Student are not in it. |
| All statuses / Active / Disabled | Filter by status. |
| Refresh icon | Reload the list. |
Create a user¶
- On Users & Access click Create User.
-
Fill in the dialog:
Field Required Notes First name Yes Last name Yes Email Yes The person's sign-in name. The temporary password is sent here, so it must be an address they can read. Phone number No Branch No Choose a branch to limit the user to it, or leave empty for All branches ("Leave empty to give the user access to all branches."). The main branch is marked (Main). Disabled branches are not listed. Role Yes The built-in roles Administrator, Finance, Instructor, Manager, Receptionist, Viewer, and your school's own roles, marked (custom). Owner, Student and SuperAdmin cannot be chosen. -
Click Create User.
- You see User created. A welcome email with their password has been sent.
What happens:
- The user is created Active.
- A welcome email with a temporary password is sent to the user.
- At first sign-in the user must choose their own password (see Login and authentication).
Example¶
The owner adds a front-desk employee: First name Lerato, Last name Nkosi, Email lerato@rosebankdriving.example, Branch Main Branch, Role Receptionist. Lerato receives the email, signs in, is asked for a new password, and then sees the menu for a Receptionist with only Main Branch's students and lessons.
If the welcome email does not arrive¶
The user is created even if the email could not be sent; the failure is only written to the server log and you are not told. Check the address, then open the user with Edit, tick Send a new password and save.
Edit a user¶
- In the user's row click ⋮ then Edit.
- Change First name, Last name, Email, Phone number, Branch or Role.
- Click Save Changes. You see User updated successfully.
Effects to be aware of:
- Changing the Role or the Branch signs the user out everywhere. Their next action sends them to the sign-in page, and they sign in again with the new access.
- Changing the Email changes the sign-in name. Tell the user.
- If the user is linked to an instructor profile, the profile's email and names are updated to match.
- For the Owner, a Student or a SuperAdmin the Role is greyed out: "This role comes from registration and can't be changed here." Their other fields, including Branch, can be edited.
Send a new password¶
Use this when someone cannot sign in and cannot use Forgot password?
- Open the user with ⋮ then Edit.
- Tick Send a new password.
- Click Save Changes. You see User updated. A new password has been emailed.
"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." The user is also signed out everywhere.
An administrator never sees or types a user's password.
Disable a user¶
Disabling stops a person signing in without removing them. Use it when someone leaves or is suspended.
- In the user's row click ⋮ then Disable.
- Confirm Disable (name)? They will no longer be able to use DriveFlow.
- You see User disabled. and the status becomes Disabled.
A disabled user:
- cannot sign in; they see the ordinary "Invalid email or password.";
- is signed out of any open session at their next action;
- does not receive password reset emails;
- keeps all their records and history.
You cannot disable yourself: "You can't deactivate your own account."
Enable a user¶
In the user's row click ⋮ then Enable. You see User enabled. There is no confirmation. The user signs in with their existing password.
Delete a user¶
Deleting is permanent
Prefer Disable unless the account was created by mistake.
- In the user's row click ⋮ then Delete.
- Confirm Are you sure you want to permanently delete (name)?
- You see User deleted.
Connecting a user to an instructor¶
An instructor has two things: an instructor profile (under Instructors) and, if they need to sign in, a user. The two are connected so that the instructor sees their own lessons.
There are three ways they become connected:
| Way | How |
|---|---|
| Invite from the profile | Instructors > ⋮ > Sign-in account, then invite. DriveFlow creates a user with the instructor's name, email, phone and branch, gives it the Instructor role, emails a temporary password and links it. If a staff user of your school already has that email, it is linked instead of creating a second one. The profile must have an email address ("Add the instructor's email address first; it is their sign-in."). |
| Link an existing user | Instructors > ⋮ > Sign-in account, then choose one of your school's staff users. The profile takes that user's email. Student accounts and users already linked to another profile are not offered. |
| Automatically by email | A user whose email is the same as exactly one instructor profile's email is linked the next time they sign in. |
The link can be removed from the same Sign-in account dialog.
Instructor sign-in check¶
This read-only page shows whether each instructor account is connected.
- Settings > Users & Access.
- Click Instructor sign-in check.
It lists every account that holds the Instructor role or matches an instructor profile, with Account, Roles, Instructor profile and Status:
| Status | Meaning |
|---|---|
| Linked | Connected to a profile. |
| Links on next sign-in | Exactly one profile has this email; it will connect at the next sign-in. |
| No instructor profile with this email | Needs fixing: the account would see no lessons of its own. |
| Several profiles share this email | Needs fixing: remove the duplicate profile or change an email. |
"Sees all lessons (manages lessons)" under a status means the account's role lets it see every lesson anyway, so it is not counted as a problem. A banner at the top says how many accounts cannot be linked, or "Every instructor account is linked or will link on its next sign-in."
To fix a problem: "Link them from Instructors → ⋮ → Sign-in account, or give the instructor profile the same email as the sign-in account (and remove any duplicate profile)."
Messages when linking:
| Message | Why |
|---|---|
| This instructor already has a sign-in account. | The profile is already linked. |
| This email address is used by an account at another school. | Emails are unique across the platform. |
| Student portal accounts can't be linked to an instructor profile. | |
| This account is already linked to (name). Unlink it there first. | One user, one profile. |
| Another instructor profile at your school already uses this account's email. | |
| This instructor's email is also their DriveFlow sign-in. Changing it needs permission to edit users. | Editing a linked instructor's email changes the user's sign-in name. |
For the instructor screens themselves, see the instructor documentation.
Connecting a user to a student¶
Students get a student portal account. It is never created on the Users & Access page.
- Go to Settings > Security. The Student Portal card lists every student with Student, Email and Portal status. (The same actions are on the student's profile.)
-
Use the row menu:
Portal status Meaning Actions No email The student record has no email address. None. Add an email to the student first. Not invited No account yet. Invite to portal Invited Account created; the student has not yet chosen their own password. Resend invitation, Deactivate Active The student has signed in and chosen a password. Resend invitation, Deactivate Deactivated The account is switched off. Resend invitation, Activate -
Invite to portal asks "Create a portal sign-in for (email) and email them a temporary password and the portal link?"
- Resend invitation asks "Email (email) a new temporary password and the portal link? Their current password stops working."
- Deactivate warns "(name) will be signed out and can't sign in to the student portal until you activate them again. Their records are kept."
Seeing the list needs View Students; using the actions needs Edit Students. The account is given the Student role automatically and is matched to the student record by email address within your school. Once created it appears in the Users & Access list with the role Student.
Full details are in Student management.
Messages you may see¶
| Message | Why |
|---|---|
| First name is required. / Last name is required. / Email is required. / Role is required. / Please select a role. | A required field is empty. |
| A user with this email already exists. | The email belongs to a DriveFlow user at your school or any other. |
| Another user already uses this email. | When changing a user's email. |
| The selected branch is not available. | The branch is disabled or not yours. |
| The selected role is not available. | The role does not exist for your school, or is Owner, Student or SuperAdmin. |
| Unable to assign the selected role. | The role could not be saved; the new user was removed again. |
| User not found. / User could not be found. | The user does not exist in your school. |
| You can't deactivate your own account. | |
| Unable to load users. / Unable to load roles. / Unable to load user information. | The data could not be read. |
| Unable to create user. / Unable to update user. / Unable to disable user. / Unable to enable user. / Unable to delete user. | The request failed. |
| No users found - Try changing your search or filters. | Nothing matches the filters. |
Workflow summary¶
flowchart TD
A["Create User (name, email, branch, role)"] --> B[Welcome email with temporary password]
B --> C[User signs in] --> D[Must choose own password] --> E[Dashboard]
E --> F["Later:<br/>Edit (role/branch change signs them out)<br/>Send a new password<br/>Disable / Enable<br/>Delete (permanent)"]
Limitations and notes¶
No protection against deleting or disabling the Owner, or deleting yourself
The only safeguard in the code is that you cannot disable your own account. Anyone with Delete Users can permanently delete any user of the school, including the Owner and themselves; anyone with Disable Users can disable the Owner. There is no screen to appoint a new Owner. Give these two permissions only to people you fully trust.
- No bulk import of users, no user groups, and no more than one role per user.
- No invitation link. "Inviting" a person means emailing a temporary password.
- No record on screen of whether the welcome email was delivered.
- The Users screen does not check a plan limit on the number of users. (Branches, instructors, students and vehicles do have plan limits.)
- The server has a separate "reset password" operation for a user (it emails a new temporary password and changes nothing else). The web application does not call it; the Send a new password tick box on the Edit dialog does the same thing as part of saving.
- Deleting a user who is linked to an instructor profile or who has activity recorded against them was not tested; if the database refuses, the page shows "Unable to delete user." or the server's reason.
- A SuperAdmin sees the users of every school on this page, with an extra Company column ("Platform (no company)" for platform accounts), but the server refuses create, edit, disable and delete for a SuperAdmin because those actions need a school. See the SuperAdmin documentation.
Related articles¶
- Roles and permissions - what each role allows.
- Branch management - one branch or All branches.
- Login and authentication - first sign-in with a temporary password.
- Instructor user accounts - instructor sign-ins in detail.
- Student portal - inviting students to the portal.