Step 1: Create a project
⏱ 5 minConsole access
- Open app.transcodes.io and sign in (Console operator account).
- Select or create an organization.
- Create project — title, description, and Domain URL.
| Domain URL choice | When to use |
|---|---|
| Transcodes hosted (Transcodes Auth) | Fastest start; auth UI lives on Transcodes |
Your origin (https://app.example.com) | Custom domain / self-hosted auth surface |
The Domain URL drives WebAuthn RP ID and is edited later from the Project Setup node.
Authentication Kit Cluster
After the project opens on the ReactFlow canvas:
- Add or open the Authentication Kit Cluster (setup wizard on first use).
- Complete Basic config — branding colors, optional SDK Redirect Origins.
- Members — add at least one member in the wizard or RBAC → Users. Members must exist here before they can sign in via your app.
- Note your Project ID (Installation Guide panel or project header).
SDK Redirect Origins
Add origins in Configuration → Domains (or the setup wizard) only when your customer app loads the SDK and receives sign-in redirects back to your site.
Leave empty if you use MCP / transcodes-guard only or fully hosted auth with no SDK callback on your domain.
| Setting | Purpose |
|---|---|
| Domain URL | Primary auth / RP ID (Project Setup) |
| SDK Redirect Origins | Allowed callback origins for redirectToSignIn / handleSignInCallback |
Mismatch between registered origins and your app’s callback URL causes redirect failures after MFA.
Next: Step 2: Load the SDK
Last updated on