Passkeys for your workforce, managed by IT.
Apps are moving to passkeys one by one, and each passkey ends up on a personal phone or browser profile that IT can't see. My1Login creates and stores passkeys for your workforce's web apps, signs people in with them, and finds the ones saved elsewhere.
- Passkeys stored in My1Login, not on personal devices
- Find passkeys and passkey-ready apps
- Shared without being exported
| App | Passkey | Status |
|---|---|---|
| Code repository | In My1Login · 2 accounts | Managed |
| Banking portal | In My1Login · shared with Finance | Shared, never exported |
| Payroll portal | Supports passkeys, none set up | Ready to set up |
| Supplier portal | Saved outside My1Login | User prompted |
Trusted by organisations including
Passkeys are safer than passwords. Unmanaged, they're a new blind spot.
Passkeys can't be phished or reused. But when each person saves their own to a phone, a personal password manager or a browser profile, IT loses sight of who can sign in to what, and a leaver may still hold a passkey that works.
Passkeys, person by person
- Saved to personal phones and browser profiles
- IT can't see which apps use them, or who holds them
- Shared accounts fall back to shared passwords
- A leaver may keep a working passkey
With My1Login
- Created and stored in My1Login, under your policies
- A report of passkeys saved elsewhere, and apps ready for them
- Shared with colleagues, never exported
- Gone the moment the directory account is disabled
Passkeys under IT control, in three steps.
Your workforce keeps signing in the way it does now. My1Login brings the passkeys under one policy.
Discover
My1Login reports where people use passkeys saved outside it, and which apps support passkeys that aren't in My1Login yet.
Set up
People get a prompt to set up a My1Login passkey instead. It is created and stored in My1Login, not on their device.
Sign in
From then on, My1Login signs them in with the passkey. Every sign-in is logged, and the passkey goes when they leave.
Everything you need to manage passkeys at work.
Managed in the same admin console, with the same policies and audit trail, as everything else in My1Login.
Passkeys stored in My1Login
My1Login creates the passkey when people set one up and keeps it, so it never sits on a personal phone or browser profile.
Passkey discovery
An admin report shows where passkeys saved outside My1Login are in use, and which apps support passkeys but have none set up.
A prompt to switch
When someone uses a passkey saved elsewhere, My1Login offers to set up a My1Login passkey instead.
Several passkeys per app
People with more than one account for an app keep a passkey for each, and pick the right one at sign-in.
Shared, never exported
With the enterprise password manager, share a passkey with a person or team. Nobody can export it or copy it to a personal device.
Leavers lose access at once
Passkeys are tied to the directory sign-in. Disable someone in Entra ID or Active Directory and their passkeys stop working.
Every sign-in logged
Passkey sign-ins appear in the same audit trail as passwords, SAML and one-time codes.
Alongside everything else
Passkeys, SAML, OpenID Connect and hidden passwords, all from one single sign-on and one policy.
The products behind it.
Passkeys come with single sign-on for web. Combine it with our enterprise password manager to share them as well.
Passkey questions
What is a passkey?
A passkey replaces a password with a pair of cryptographic keys. The app keeps only the public key, so there is no password to steal, phish or reuse. Read more about passkeys
Which browsers and apps does it work with?
Passkeys in My1Login work for web apps in Chrome and Microsoft Edge. Mobile apps and Windows desktop apps aren't covered yet.
Which subscription includes passkeys?
Storing passkeys, discovery and several passkeys per app all come with single sign-on for web. Combine it with our enterprise password manager to share them as well. See pricing
What does discovery find?
Two things: apps where people sign in with a passkey saved outside My1Login, and apps that support passkeys but don't have one in My1Login yet. Both appear in an admin report, and people using a passkey saved elsewhere are offered a My1Login passkey instead.
Can people copy or export a passkey?
Not if you choose to stop them. Passkeys can be hidden from users and blocked from being exported, so a work passkey can't move to a personal device or account.
What happens when someone leaves?
Their passkeys are tied to their directory sign-in. Disable them in Microsoft Entra ID or Active Directory and they lose access to every passkey in My1Login straight away.
Can people still use a hardware security key?
Yes. Passkeys created in My1Login are stored in My1Login. If someone wants to use a hardware security key for an app instead, they choose to sign in another way and follow the security key option in Windows Hello.
See passkeys managed in a 5-minute demo.
We'll find the passkeys already in use, set up a My1Login passkey for an app, and share it with a colleague without anyone exporting it.
- 5 minutes, on your own apps
- A specialist replies within one working day
- No obligation





