Console
⚡ 2 min readThe Member Console is the hosted page on Transcodes Auth where signed-in users add, view, and remove their own authentication methods. You do not build this UI — the SDK opens it with a redirect, same pattern as Signin.
What members can manage
| Method | Examples | Actions |
|---|---|---|
| Passkeys | Face ID, Touch ID, Windows Hello | Register, list, delete |
| Security keys | YubiKey, FIDO2, mobile QR authenticator | Register, list, delete |
| TOTP apps | Google Authenticator, Authy | Enroll, list, remove |
Email OTP and passcode are used during sign-in and step-up flows; credential self-service in Console covers passkeys, hardware keys, and TOTP.
Flow
Session creation uses the member’s existing SDK JWT (oid, pid, sub). If the user is not signed in, redirectToConsole logs an error and does nothing — Signin first.
SDK usage
// Settings / Security page — member must already be signed in
transcodes.redirectToConsole();
// Optional explicit callback (default: current page URL)
transcodes.redirectToConsole({
redirectUri: 'https://app.example.com/settings/security',
});No custom backend endpoints are required for self-service credential management.
Transcodes Console (app.transcodes.io) is different: that is where admins configure projects, RBAC, branding, and webhooks. This page is about the member-facing console on Transcodes Auth.