# Companies choose how their people sign in, and admins confirm it's them

18 October 2026. A company you sell to can now choose the ways its people sign in without single sign-on, down to passkeys only, and reset a lost passkey. Its admins confirm it's them, at their identity provider or with a passkey, before its security settings change in your app.

## Added

- **Authentication:** Sign-in methods for each company. In its access policy, the company's admins in your app, your team in the console, or a company API key with policy:write tick the ways its people may sign in when they do not use single sign-on: Password, Magic link, Passkey, Google, Microsoft, GitHub or LinkedIn, down to Passkey alone. Single sign-on is always allowed, and with nothing ticked every way your app offers stays open, as before. Every way in checks the list once the person's password, link, passkey or social account is proven, and refuses with a sentence naming the ways the company allows; break-glass people follow it too, and each refusal is in the company's trail. A way your app's sign-in does not offer cannot be saved on the list, and a company admin cannot save one that would leave them no way back in. Sessions already open stay open: the policy counts the ones that began a way the list no longer allows, and Sign them out ends them.
- **Authentication:** Passkeys the company asks for. Under a list, a passkey counts only when the device verified the person with a fingerprint, a face or its PIN. Someone who signs in a way the list leaves out, with Passkey on it and no passkey yet, is sent to set one up, once, and then signs in with it. Adding another later takes a passkey sign-in from the last ten minutes, so a stolen password cannot add one, and while the company asks for passkeys nobody can remove their last. Someone who loses theirs is reset by the company's admins in your app, by your team in the console, or by a company API key with the new passkeys:write scope: their passkeys for your app are removed, they are signed out and emailed that it happened, and their next sign-in sets up a new one.
- **Authentication:** Company admins confirm it's them before the company's security settings change in your app: its access policy, signing everyone out, its single sign-on setup, its admins, roles and the groups that carry a company role, a new API key or service account, its log streams and a passkey reset. Unless they did so in the last ten minutes, they sign in again at the company's identity provider, which is asked to sign them in afresh rather than reuse a session it already has, or with a passkey that verifies them, set up first if they have none. A password sign-in does not count, however recent. They come back to the same session, in the browser tab that asked, with their change waiting to be saved: the confirmation is bound to that tab, so an address copied from it confirms nothing. A session your team opens as one of the company's people, or an agent's, cannot confirm, and the console and company API keys are never asked. Each confirmation is in the company's trail.
- **SDK:** The Single sign-on screen gives your customer's admins the sign-in methods, with how many of their people hold a passkey and Sign them out, and Reset passkeys beside a person's sessions (from @buildbase/sdk 1.0.0). A change that needs a confirmation opens Confirm it's you and keeps the unsent change on the screen until they save it again. useSaaSAuth().requireReverification() and isReauthRequired() do the same for your own screens, and removing a passkey from the account settings asks for a passkey first.

Source: https://www.buildbase.app/changelog/company-sign-in-methods-and-step-up
