Sign in
One account, through Google. Then choose the laboratory.
LabFlow holds no password of its own. Your laboratory listed a Google account against your user record, and that account is your key — which also means your laboratory can withdraw it without waiting for anybody here.
Forgotten which account you used, or locked out of it? There is a page for that, and it is honest about what it can and cannot do.
Step 1 of 2 — your account
Continue with Google
You will be asked to pick a Google account and to confirm that LabFlow may see your name, your email address and your profile picture. Nothing else.
- There is no password field, and that is deliberateA password LabFlow never receives is a password LabFlow cannot lose. The argument, in four parts.
- Two-step verification is Google’s, and it applies hereIf your laboratory requires it, it is enforced on the account before LabFlow is ever reached.
A sign-in is an event, and this is the event.
In a clinical system, who looked at what and when is not telemetry — it is part of the record. Signing in writes one row, on the same path that performs the sign-in, so an action that skipped the row would also have skipped the sign-in.
The role is stamped on the row, not looked up later. A role that is read at query time answers “what can this person do now”, which is the wrong question about something that happened in March. The row has to stay interpretable against the permissions that applied when it was written — the same reason a result stores the reference range that applied when it was produced, rather than today’s.
Four reasons LabFlow never asks for a password.
This is an unusual choice and it deserves an argument rather than an assurance. Each of these is a thing that stops being possible, not a thing that gets better.
A password LabFlow never receives is one it cannot leak
There is no credential table, no reset token, no password-hash migration and no “we have detected unusual activity” email to fake. The most commonly breached asset in a clinical system is simply absent from it.
Revoking access is one action, in one place, and it is immediate
A technician leaves. Their laboratory removes them at /users and the door is shut — no waiting for a password rotation, no shared bench login to change, no account left alive because nobody remembered it existed. If the whole Google account is disabled by their employer, every laboratory they belonged to closes at once.
Two-step verification is enforced before LabFlow is reached
Whatever your organisation already requires of a Google account — a security key, a prompt on a managed phone, a hardware token — applies to LabFlow without LabFlow implementing any of it, and without a second enrolment nobody completes.
The honest cost, stated rather than buried
It is a single point of dependency. A laboratory whose staff have no Google accounts cannot use LabFlow today, and an outage at Google is an outage at the front door. That is a real trade and it is named here rather than discovered later — the FAQ takes the same question head-on.
Three ways this goes wrong, and where each one is actually fixed.
None of the three is fixed by trying again. Two of them are not fixed here at all, which is worth knowing before you spend twenty minutes on the wrong page.
You cannot get into the Google account
Locked out, lost the phone, forgotten the password on the account itself. Nothing on this site can help, and nothing on this site should be able to — the recovery is Google’s and it is the same one you would use for your mail.
You do not remember which account you used
Common, and fixable. The laboratory listed one specific address against you, and there are three reliable places to find out which — including one person who can simply read it off your user record.
Google works, LabFlow says you have no access
This is not an authentication problem at all. It means the account you signed in with is not on any laboratory’s user list — usually a personal address used instead of the work one, or a record that has not been created yet.
No account yet?
Only one of these three routes goes through a registration form. The other two end on this page, which is why it is worth thirty seconds to work out which one you are.
A sign-in screen is a promise about everything behind it.
This one asks for nothing it does not need, defaults nothing that would be dangerous to guess, and writes down that it happened. Those three habits are the same ones the rest of the product runs on, which is the only reason a sign-in page is worth reading about at all.
Not sure LabFlow is the right thing at all? The comparison pages say plainly where it is the weaker choice.