Signing in
A password, a passkey, or a Google or GitHub account. A second factor when the organization asks for one.
Register the app, set the callback your framework already uses, install the SDK. That is the whole integration.
A password, a passkey, or a Google or GitHub account. A second factor when the organization asks for one.
Who signed in, which organizations they belong to, and the role they hold where they asked to act.
Sign in once and the session is good across every app in the organization, including ours.
Standards, not a proprietary protocol. If your framework can read an OpenID Connect discovery document, it can already talk to this.
An authenticator app, a code by SMS or email, or a passkey. Enrolment sends the material and then demands it back before it writes anything, and the destination is never taken from the request — an enrolment that let the caller name the phone would enrol the attacker's.
Create people, put them in an organization, give them a role there. SCIM 2.0 does the same thing from a directory you already run, so joiners and leavers arrive without a script of your own.
Every application registers under its own client id and redirects to the same authorize endpoint, so a person who is already signed in comes straight back with a code and never sees a form twice.
A role is granted at a place — an organization, a workspace under it, a single project. The token carries the one that applies to the request, so your service decides without asking us anything.
A WebAuthn credential registered to the account, unlocked by whatever the device already uses — a fingerprint, a face, a PIN. Nothing that can be phished, because there is nothing to type.
Actions are written once to an append-only log scoped to the organization they happened in. The write path exists; there is no edit path for normal operation, which is the point of keeping one.
The same service, wearing your name, on hardware you choose.
An organization is a tenancy boundary, and the boundary is enforced by the code that reads the token rather than by a column somebody has to remember to filter on.
Point Identity at your own issuer and it becomes the entry point without becoming the record.
An organization can hold its own customers as sub-organizations, so a business you serve manages its people without any of it reaching yours.
Almost nothing. Nobody should be hand-rolling OAuth in 2026, and with this you do not.