Skip to content

Security settings

Applies to: every user (own password); school Owners and Administrators (user access, student portal); SuperAdmin; developers and server administrators (everything that is not in the application). Last reviewed: 2026-11-18.

This page describes how sign-in, sessions and passwords work in DriveFlow, and which of those can be set.

The honest summary

The Security page in the application has no security settings. It holds a button to change your own password, two links, and the list of student portal accounts. Session length, password rules, lockout and everything else are in the server configuration or fixed in the code. No secret values are given in this documentation.

The Security page

Menu: ADMINISTRATION > Settings > Security (/settings/security)

The page is headed Security, "Manage authentication, user access and student portal security." Any signed-in user can open it. It has no switches or input fields.

Card Content What it does
Account Security: "Manage your own account security." Change password: "Change the password for your DriveFlow account." Button Change Password Opens the change password page
User Access: "Manage organisation users and access." Organisation users: "Manage staff accounts and access." and Roles & permissions: "Control what users can access." Links to Settings > Users & Access and Settings > Roles. Those pages apply their own permission checks.
Student Portal: "Manage student access to the DriveFlow portal." The list of students and their portal status See Student portal access. Shown with Students.View. Otherwise: "You need permission to view students to manage their portal access."

At the bottom the page states: "Password rules are managed by the DriveFlow authentication system. This page focuses on account access, password management and student portal access."

Screenshot to be added

Screen: Security page. Should show: the three cards and the information note at the bottom.

Summary of security settings

Setting Value Where it is set Who can change it Restart needed
Length of a normal session 480 minutes (8 hours) in the supplied configuration Server configuration (API) Server administrator Yes
Length of a "remember me" session 30 days Server configuration (API) Server administrator Yes
Idle sign-out in the web app 30 minutes; 0 switches it off Server configuration (web app) Server administrator Not verified; new browser sessions may pick it up without one
Minimum password length 8 Code Developer New deployment
Password must contain a digit, an upper-case letter, a lower-case letter and a symbol Yes, all four Code Developer New deployment
Failed sign-ins before lockout 5 (framework default; not set in the code) Code Developer New deployment
Lockout time 5 minutes (framework default; not set in the code) Code Developer New deployment
Password reset link lifetime 1 hour Code Developer New deployment
Password reset emails per address 3 per 15 minutes Code Developer New deployment
Two-factor sign-in Does not exist - - -
Email address confirmation Does not exist - - -
Refresh tokens Do not exist - - -
Limit on simultaneous sessions None - - -
Audit log Does not exist - - -

Other server-side security configuration is covered in the internal technical documentation.

Signing in

What is needed Email address and password
Wrong email or password, or a disabled account "Invalid email or password." The same message in each case.
Too many wrong passwords "Too many failed sign-in attempts. Please try again in N minute(s)."
After signing in Students go to the portal, staff to the dashboard, the SuperAdmin to Users
Temporary password The user is sent to the change password page and cannot use anything else until they choose their own password: "You signed in with a temporary password. Choose your own password to continue."

Remember me

The sign-in page has a Remember me box.

Not ticked Ticked
Session length 8 hours 30 days
Where the session is kept in the browser For this browser tab only. It is gone when the tab closes. In the browser, and survives closing it
Signed out when idle Yes, after 30 minutes without activity No
Mobile app Kept in memory only Kept in the device's secure storage

Warning

Do not tick Remember me on a shared computer.

Sessions

DriveFlow uses one signed token per session. It carries the user's roles and permissions as they were at sign-in.

Behaviour Detail
When a session ends by itself When the token expires (8 hours or 30 days), or, without "remember me", after 30 minutes with no mouse, keyboard, touch or scroll activity in any open tab
Message after an idle sign-out "You were signed out because you weren't active for a while. Please sign in again."
Message after expiry "Your session has ended. Please sign in again."
Renewal A session is not extended while you work. When it expires you sign in again.
Signing out Removes the session from the browser.
Several devices A user may be signed in on any number of devices at once. There is no list of devices and no "sign out everywhere" button. Changing your password has that effect.

What ends a user's sessions early

On every request the server checks that the account is still active, that its security stamp is unchanged, and that it still belongs to the same school.

Event Sessions end How quickly
The user changes their own password All other sessions. The session used for the change continues. Within 1 minute
A password is reset through the emailed link All sessions Within 1 minute
An administrator sends the user a new password All sessions Within 1 minute
An administrator changes the user's role or branch All sessions At once
A role's permissions are changed All sessions of every user holding that role. For a built-in role this means in every school. At once
The user is disabled All sessions At once
A student's portal access is deactivated All sessions Within 1 minute
The school's subscription ends Sessions stay, but every request is answered with "Your subscription has ended..." Within 1 minute

"Within 1 minute" is because the server remembers each account's state for one minute. Where more than one API server runs, "at once" applies to the server that made the change and the others follow within the minute.

Passwords

Password rules

Rule Value
Minimum length 8 characters
Must contain A digit, an upper-case letter, a lower-case letter and a symbol
Expiry Passwords do not expire
History A previous password may be used again

Important

The rules cannot be changed in the application. The change password page does not list them in advance. A password that breaks a rule is refused with the rule's message.

Changing your own password

Where: Settings > Security > Change Password, or /account/change-password. Any signed-in user.

  1. Fill in Current Password (labelled Temporary Password after signing in with one).
  2. Fill in New Password and Confirm New Password.
  3. Save the change.

Messages: "The new passwords do not match.", "Your password has been changed successfully.", "Unable to change password."

Forgotten password

On the sign-in page use Forgot password?. The website always answers "If an account exists for (the email), we've sent a link to reset its password. The link expires in an hour."; the mobile app shows the server's message "If an account exists for that email, a reset link has been sent." followed by its own instruction. Both appear whether or not the account exists.

Link lifetime 1 hour. It works once.
Limit 3 emails per address per 15 minutes
After resetting "Your password has been reset. You can now sign in." A lockout is lifted and all sessions end.
An old or used link "This reset link is invalid or has expired. Please request a new one."
Requirement The platform's application address must be configured on the server. Without it no reset link can be sent.

Passwords set by an administrator

See User and role settings. The temporary password is emailed and must be changed at the first sign-in.

Account lockout

Rule After 5 wrong passwords in a row the account is locked for 5 minutes
Who it applies to Every account, including the SuperAdmin
Unlocking early Reset the password through Forgot password?. There is no "unlock" button for an administrator.
Can it be changed Only in the code. The values are the framework's defaults, and are not written in DriveFlow's own code.

Student portal access

Where: the Student Portal card on the Security page.

There are no portal-wide settings. The list has one row per student, with the portal status: No email, Not invited, Invited, Active or Deactivated.

Action Who What it does
Invite to portal Students.Edit Creates a sign-in for the student's email address and emails a temporary password. Needs the Student Portal feature in the plan.
Resend invitation Students.Edit Emails a new temporary password. The old one stops working.
Deactivate Students.Edit Signs the student out. They cannot sign in until activated again. Their records are kept.
Activate Students.Edit Lets the student sign in again

Important

A student's email address is their sign-in name and must not be used by any other DriveFlow account.

The procedures are in the student portal guides.

Protection of stored data

User passwords are hashed and cannot be read back. Sensitive values a school enters, such as its SMTP password, PayFast merchant key and passphrase, its Facebook Page access token and a salesperson's bank account number, are stored encrypted.

If the encryption keys are lost, for example when a database is rebuilt without them, the encrypted values can no longer be read and must be entered again. How and where secrets are stored is covered in the internal technical documentation.

Production installation

Guidance for securing a production installation (starting accounts, server secrets and environment) is covered in the internal technical documentation. Contact DriveFlow support if you run your own installation.

What does not exist

Not available Note
Two-factor authentication Not built
Single sign-on (Google, Microsoft) Not built
Email confirmation for new accounts Not built. A new account can sign in at once.
Password expiry or history Not built
IP restrictions Not built
Session list, "sign out all devices" Not built
Audit log of sign-ins or changes Not built. The permission AuditLogs.View exists but unlocks nothing.

Settings that exist only on the server are listed in Settings not exposed in the UI (internal documentation).