24Flow Customer Documentation
Breadcrumbs

Shopfloor Login

Operators log in to 24Flow on shared workstations with their own personal account. This article explains why, which login routes exist, what an operator does at a shift change in each route, and what your administrator sets up.

Why every operator has their own login

Each operator logs in to 24Flow with a personal account, also on a shared workstation. One login per workstation, shared by a team, is not possible:

  • 24Flow runs on the Salesforce platform. A platform login belongs to one named person and may not be shared between people. A license can be reassigned when someone leaves.

  • Your data stays reliable. Time bookings, quality checks, checklists and incident reports are recorded under the person who did the work. Without a person behind the login, these functions have no value.

  • MFA protects the person, not the PC. Salesforce requires multi-factor authentication for every user. A shared login lets anyone at that workstation in.

The workstation is chosen inside 24Flow: at the start of a shift the operator logs in and selects the workstation they work on that day.

What matters at a shift change

The question that decides which route fits your plant is not how the first login works, but what operator B does when operator A walks away from the same PC. The routes below differ in the number of steps and in which secrets the operator types: a personal one (only the operator knows it) or a shared one (everyone at the PC knows it). Fewer steps and no shared secret is better.

Route

Steps at a shift change

Secrets the operator types

Hardware or phone

Operators need an Entra account

Effort sits with

A. Windows login is the 24Flow login (Entra SSO + Windows Hello)

5

1 personal

none

yes

IT, once

B. Browser profile per operator (Edge or Chrome)

5 to 6

1 personal, plus 1 shared in Edge

none

yes (or a Google account)

operator and IT

C. Password manager on the workstation (Bitwarden)

7

1 personal

none

no (an e-mail address per operator)

operator, daily

D. Security key (USB or NFC)

5

1 personal

key per operator

no

operator, daily

Our recommendation for plants on the Microsoft stack is route A: one personal PIN per shift change, no hardware, no phone, and the setup effort sits with IT once instead of with operators every day. Routes B and C work without changes to the workstations' Windows setup. Route D works everywhere but puts a physical object in every operator's hands.

Step counts assume the operator selects the workstation after login.

Route A: Windows login is the 24Flow login

For plants where the workstations are joined to Microsoft Entra ID and every operator has an Entra account.

How it works: Salesforce is configured for single sign-on through Entra. Each operator has their own Windows account on the shared workstation and signs in with a Windows Hello PIN. Whoever is signed in to Windows is signed in to 24Flow; no second password, no app, no key.

At a shift change:

  1. Operator A locks the PC (Windows key + L).

  2. Operator B picks their own name on the lock screen.

  3. Operator B enters their Windows Hello PIN.

  4. Operator B opens the browser; 24Flow is already logged in.

  5. Operator B selects the workstation.

What your administrator sets up, once: an Entra account for every operator (no Microsoft 365 license is needed for an identity), the workstations joined to Entra with shared PC mode so old profiles are cleaned up, single sign-on from Entra to Salesforce, and MFA reported from Entra to Salesforce so Salesforce does not ask for its own second factor. For the first sign-in of an operator without a phone, the administrator issues a Temporary Access Pass; the operator then sets their PIN.

Licensing: Entra ID Free covers single sign-on, MFA and Windows Hello for Business. Restricting logins to the plant's IP range requires Conditional Access, which is part of Entra ID P1 (included in Microsoft 365 Business Premium and E3). That restriction is optional.

Route B: a browser profile per operator

For plants that do not want to join the workstations to Entra, but can give operators an Entra or Google account.

How it works: each operator opens their own browser profile in Edge or Chrome, signed in with their own account. Their 24Flow passkey is stored in that profile and follows them to every workstation.

At a shift change:

  1. Operator A closes their browser profile.

  2. Operator B picks their own profile.

  3. Operator B enters their account password.

  4. Operator B chooses their passkey on the 24Flow login page.

  5. In Edge, Windows Hello asks for the PIN of the shared Windows account; in Chrome this prompt does not appear.

  6. Operator B selects the workstation.

Points to know: in Edge the Windows Hello PIN is a shared secret, because all operators use the same Windows account. Set the session timeout on the operator profile to the length of a shift so a profile left open closes on its own. Chrome profiles signed in with an Entra account require Google Workspace federation with Entra, set up by your IT team.

Route C: a password manager on the workstation

For plants that want neither Entra accounts for operators nor hardware.

How it works: a Bitwarden browser extension on the workstation holds a vault per operator with their 24Flow passkey. The operator unlocks their vault with their own code.

At a shift change:

  1. Operator A logs out of 24Flow.

  2. Operator A locks their vault.

  3. Operator B switches to their account in the extension.

  4. Operator B enters their vault code.

  5. Operator B starts the 24Flow login.

  6. Operator B chooses their passkey.

  7. Operator B selects the workstation.

Points to know: each operator needs a Bitwarden account, so an e-mail address. The extension keeps up to five accounts signed in at once, which limits how many operators can share one workstation without re-adding accounts. The passkey selector shows the passkeys of the last active account, so after switching accounts the login has to be started again. A vault left unlocked lets the next person in; set a short auto-lock.

Route D: a security key

For plants that prefer a physical token.

How it works: each operator carries a USB or NFC security key (for example a YubiKey) that holds their passkey. It works on every workstation and needs no phone.

At a shift change:

  1. Operator A logs out of 24Flow.

  2. Operator B enters their username.

  3. Operator B inserts or taps the key and touches it.

  4. Operator B enters the key PIN.

  5. Operator B selects the workstation.

Points to know: a USB key left in the PC lets the next person in; NFC avoids that but the workstation must have an NFC reader, which older PCs do not. Keys get lost and break; buying, registering, replacing and recovering keys is the customer's responsibility. 24Flow does not supply or support hardware.

Setting it up (for your administrator)

  1. Check operator permissions. Operator profiles and permission sets should not include the System Administrator profile, Modify All Data, View All Data, Customize Application or Author Apex. Users with those permissions need phishing-resistant MFA (a security key or a passkey on their own PC).

  2. Pick a route from the table above with your IT team. Route A needs the Entra work described there; routes B, C and D need the Salesforce settings below.

  3. Enable passkeys in Salesforce (routes B, C, D). In Setup, go to Identity Verification, enable Security Keys (U2F or WebAuthn) and Built-In Authenticators, and turn on Allow passwordless login with passkeys.

  4. Set a session timeout on the operator profile that fits a shift, so a forgotten login closes on its own.

  5. Register each operator, sitting together: the operator logs in once with a temporary verification code generated on their user record and registers their passkey or key.

  6. Measure a shift change on one workstation with two operators before rolling out: count the steps and time them. Compare with the table above; if your plant's numbers are higher, contact 24Flow support before going further.

Frequently asked questions

Can we use one login per workstation instead?
No. A platform login belongs to one person and cannot be shared, and time bookings and checklists without a person behind them have no value.

Do operators need a phone?
No. None of the four routes requires a phone. An authenticator app on a company or personal phone remains possible as an alternative second factor, but it depends on phone use on the shop floor and is not accepted for users with elevated permissions.

An operator forgot to log out. Can the next person keep working?
No. The next operator logs out and logs in as themselves, so their work is recorded under their name. The session timeout closes forgotten logins automatically.

An operator lost their key (route D) or forgot their PIN (route A)?
Your administrator issues a temporary access code and the operator re-registers. Until then they can log in with that code.

Does a planner with admin rights need something different?
Yes. Users with the System Administrator profile or elevated permissions must use phishing-resistant MFA: a security key or a passkey on their own PC. An authenticator app is not accepted for them.

More information