Skip to content

Staying signed in: session management

Applies to: Owner and other school staff, Instructor, Student. Last reviewed: 2026-11-18.

This page explains how long you stay signed in, what Remember me does, how to sign out, and what happens when your password changes or your account is deactivated.

The short version

Situation What happens
You signed in with Remember me You stay signed in after closing the app, until the session runs out (days)
You signed in without Remember me You stay signed in until you close the app, or until the session runs out (hours), whichever comes first
You tap Sign out The session is removed from the phone and push notifications to it stop
Your password is changed or reset somewhere else This phone is signed out the next time it talks to DriveFlow
You change your password in the app You stay signed in on this phone; you are signed out everywhere else
Your account is deactivated This phone is signed out the next time it talks to DriveFlow
Your school's plan loses the app You are not signed out; you are moved to a plan screen. See Subscription eligibility

Where the session is kept

  • With Remember me: the session is saved in the phone's secure storage (on Android, storage that is encrypted with a key held by the Android Keystore). It is stored under one entry and contains the sign-in token, when it expires, your name and email address, and your school and branch identifiers. Your password is never stored.
  • Without Remember me: the session lives only in the app's memory. Closing the app, or Android closing it in the background, ends it. If an older remembered session was saved on the phone, signing in without Remember me removes it so that it cannot come back.

If the phone's secure storage fails (for example a damaged Keystore), the app does not stop. It logs the failure and keeps the session in memory only, so you will need to sign in again after the app closes.

How long a session lasts

The length is decided by the server when you sign in and is written into the session token:

  • A normal session lasts a number of minutes (a server setting).
  • A Remember me session lasts a number of days (a server setting).

The configuration used by the project's tests is 480 minutes (8 hours) and 30 days. The values on the live server are set by whoever runs it; contact DriveFlow support if you need the exact figures.

There is no silent refresh. When the session reaches its expiry time the app treats it as ended, even if you are in the middle of something, and you sign in again.

What happens when the app starts

  1. The app looks for a saved session.
  2. No saved session: the Sign in screen opens.
  3. A saved session that has already run out, cannot be read, or is not a mobile session: it is removed and the Sign in screen opens.
  4. A live saved session: it is used, and then checked with DriveFlow:
  5. the school's plan is checked (Subscription eligibility);
  6. your profile and your school's name and logo are loaded for the sidebar.
  7. If DriveFlow refuses the session during those checks (password changed, account deactivated), the session is removed and you see the Sign in screen with "Your session has ended. Please sign in again."
  8. If DriveFlow cannot be reached, the session is kept. You see We couldn't check your access with a Try again button. Nothing is lost; try again when you have a connection.

Note

Nothing is drawn on the screen until these checks have finished. That is deliberate: it stops a student briefly seeing a staff screen on the way to their own.

Signing out

You can sign out from three places:

  • The Sign out link at the top right of every screen.
  • Settings › Sign out (red button at the bottom).
  • The Sign out button on the plan screens, the No mobile access screen and the Choose your password screen.

What signing out does, in order:

  1. Tells DriveFlow to remove this phone from your push notification list, while the session can still prove whose phone it is.
  2. Removes the saved session from the phone's secure storage and from memory.
  3. Drops the phone's push token so nothing more is delivered to it.
  4. Cancels any lesson reminders scheduled on the phone (students).
  5. Shows the Sign in screen.

Changing your password ends every existing session.

Lending your phone

An instructor lends their phone to a colleague for the afternoon. They tap Sign out first. The colleague signs in with their own account and from then on the phone receives the colleague's notifications, not the owner of the phone's.

When your session ends without you signing out

The app ends the session and shows the Sign in screen with the blue message "Your session has ended. Please sign in again." when:

  • the session's expiry time has passed (checked before every request); or
  • DriveFlow answers a request with "not authorised". That happens when:
  • your password was changed or reset on another device or by your school;
  • your account was deactivated;
  • your account was moved to a different school;
  • the token was altered.

Inside a screen you may first see the same sentence in a red box ("Your session has ended. Please sign in again.") just before the app moves to Sign in.

If a newer sign-in has already replaced the session by the time an old request is refused, the newer session is left alone.

When your password changes

Every session token carries a stamp that is tied to your password. The server compares it on each request.

  • You change it in the app (Settings › Change password): the old session ends everywhere. The server returns a new session of the same kind (mobile, and with the same Remember me choice) and the app starts using it, so you stay signed in on this phone. The plan is checked again for the new session.
  • It is changed somewhere else (you reset it from an email link, you change it on the web, or your school sends you a new temporary password): this phone's session is refused on its next request and you are signed out.

When your account is deactivated

A deactivated account cannot sign in (it looks like a wrong password) and existing sessions stop working. When a school deactivates a user through DriveFlow's user screens the change takes effect straight away. The server keeps each session's state in a short cache (one minute), so in other cases a refusal can take up to about a minute to reach a phone that is in active use.

When a staff member deactivates a user from the app, the confirmation reads: "Deactivate <name>? They are signed out straight away and can't sign in until activated again."

When your role or permissions change

Your roles and permissions are written into the session token at sign-in. The menu in the app is built from the token, so a change to your role does not change your menu until you sign out and sign in again. The server uses the current state: its session check is refreshed when roles change, so an action you are no longer allowed to do is refused even if the button is still showing.

Using more than one device

  • You can be signed in on the website and on one or more phones at the same time. Each has its own session.
  • Each phone you sign in on is registered for push notifications separately. A notification goes to all of your phones.
  • If two people use the same phone one after the other, the phone belongs to whoever signed in last.

Limitations and notes

No automatic lock

The app does not ask for a PIN, fingerprint or password when it is reopened. Anyone holding an unlocked phone with a remembered session can use the app. Use your phone's own screen lock.

  • No "sign out everywhere" button. Changing your password is the way to end every session.
  • No list of signed-in devices in the app or anywhere in the mobile API.
  • No idle timeout. Sessions end by time since sign-in, not by inactivity.
  • Sign-out needs a connection to stop push cleanly. If the phone is offline when you sign out, the request to remove it from the push list fails silently. The phone's push token is still dropped locally, which stops delivery, and the server removes the stale entry the next time a push to it fails.