# User management

User management makes OhAuthCat the whole sign-in system for your application's own users, next to the enterprise SSO and directory sync your customers configure. Everything is scoped to one environment: the same email address in two environments is two unrelated users, and a token from one environment is never accepted by another.

## What you get

- [Hosted login](/user-management/hosted-login/): sign-in, sign-up, password reset, invitation and account pages on `signin.<your domain>`, in six languages, with your branding. The API behind them, token revocation, logout and discovery are on `login.<your domain>`.
- Sign-in methods: [passwords](/user-management/passwords/), [passkeys](/user-management/passkeys/), [email codes](/user-management/magic-codes/) and [social sign-in](/user-management/social-sign-in/) with seven providers.
- [Multi-factor authentication](/user-management/mfa/): authenticator apps (TOTP), passkeys and one-time recovery codes, with environment and organization policies. SMS is not offered: NIST SP 800-63B lists it as a restricted authenticator.
- [Sessions and tokens](/user-management/sessions-and-tokens/): authorization code with PKCE, short-lived access tokens, rotating refresh tokens, listing and revocation.
- [Organizations, memberships and invitations](/user-management/organizations-and-invites/), with an organization switcher on the hosted pages.
- [Roles and permissions](/authorization/) in the tokens, [bot protection](/bot-protection/) on sign-in and sign-up, and [connected apps](/oauth-provider/) when other applications need access on your users' behalf.

## How it fits together

1. Your app redirects the browser to the hosted login with a PKCE challenge (`code_challenge_method=S256` is required).
2. The user signs in with any method the environment (and, when the app asks for one, the organization) allows.
3. The browser returns to your exact registered redirect URI with a single-use code that lasts 60 seconds.
4. Your app exchanges the code at `POST /user_management/token` for an ID token, an access token and a refresh token.

The management API under `/v1/users`, `/v1/invites`, `/v1/organizations/{org}/memberships` and `/v1/user_management/…` needs the `users:read` or `users:write` scope. See the [Management API reference](/reference/api/management/).

## Settings

`PUT /v1/user_management/settings` sets the environment's sign-in `methods`, `require_name` (ask for a name at sign-up) and `native_app_origins` (apps allowed to run [passkey](/user-management/passkeys/#native-apps) ceremonies). A method turned off for the environment, or for the organization the flow signs into, answers [`login_method_disabled`](/errors/login_method_disabled/).

## Events

User management emits `user.created`, `user.updated`, `user.deleted`, `user.invited`, `membership.created`, `membership.updated`, `membership.deleted`, `session.created` and `session.revoked`, plus `user.sign_in.challenged` and `user.sign_in.blocked` from [bot protection](/bot-protection/). See the [webhook event catalogue](/reference/webhook-events/).

## Monthly active users

Each sign-in counts the user once per calendar month (UTC). `GET /v1/user_management/usage` returns the current month's count and your plan's limit. Plan limits for user management are not final; the pricing page is the source for them.
