REM Auth
Your REM Auth account - one sign-in for every REM app - and the admin screens for organisations, teams, products, roles and access.
Your REM Auth account - one sign-in for every REM app - and the admin screens for organisations, teams, products, roles and access.
User guide
Getting started: Create your REM account, confirm your e-mail address, and sign in to your first REM app.
Signing in and out: Sign in on one screen, use your second factor, reset a forgotten password, what lock-out means, and signing out of every app.
Two-step verification: Add an authenticator app, a security key or passkey, and recovery codes to your REM account; remove one you no longer have.
Profile and password: Your one profile for every REM app - picture, name, e-mail and language - and changing your password.
Sessions and your access: My apps, which teams give you access, and signing out a device you do not recognise.
Organisations, teams and people: For super admins - add an organisation with its look and teams, manage teams, and find and change people.
Products, roles and access: For super admins - add a product in five steps, choose how people sign in, declare roles, and decide who may use it with which role.
Invitations: For super admins - invite one person by link, even when self sign-up is off, and what happens when they open it.
Connect tokens and service accounts: For super admins - connect tokens that let apps register themselves, the watch tower token, and service accounts for app-to-app calls and agents.
Sign-in settings, sessions and second factors: For super admins - sign-up, password reset, two-factor, password rules and lock-out for every REM app, plus everyone's sessions, second factors and the audit log.
Developer docs
OIDC endpoints and claims: The live OpenID Connect endpoints, grant types, scopes and the claims REM Auth puts in tokens - including the verified-email rule.
Connect an app: Register your app at every deploy with a connect token - the API call, the answer, the Python helper and the Django integration.
Auth SDK for React and Next.js: @rem/auth-react - sign-in, sign-up, recovery and second-factor forms inside your app, Next.js route handlers with PKCE and encrypted cookies, sessions and webhook verification.
User-change webhooks: The signed events REM Auth sends your app when a person changes, is switched off or deleted, or changes teams - with signature verification.
MCP server: REM Auth's MCP server for administrators' AI agents - the tools, the two-step writes, and why it answers only on REM's internal network.
Last updated 18 Nov 2026