Personal settings
Choose your Console preferences and manage your RDC account.
Open the account menu and select Personal settings.
Language
Under Language, select English or 한국어. Console labels and messages change immediately. English is the default, even when your browser uses another language.
Your selection is saved in this browser and restored when you return. Other open Console tabs in the same browser also reflect the selection. Clearing browser storage resets the preference to English. The language preference does not sync between devices.
Theme and display currency
Use Theme to choose System, Dark, or Light. Use Display currency to show credit values in the billing account currency, KRW, or USD. Changing the language does not change the display currency or the billing account's payment currency. See Billing and automatic recharge for currency and payment details.
Your theme is saved in this browser and applies to Console. System follows your device's appearance. The account portal has its own appearance preference.
Account settings
Open the account menu and select Account settings to open the RDC account portal. You can also open it from Personal settings. Continue with your Console account if prompted, edit your name, and save. The name belongs to your RDC account; Console language, theme, and display currency remain in Personal settings.
Passkeys
The account portal at /user has General, Security, and Danger zone sections. Existing /user/profile links still open General.
Scroll to Security on your account page, enter a recognizable passkey name, and choose Add passkey. Your browser asks you to confirm with a device unlock method or security key. You can register one active passkey per account. To replace it, remove the current passkey first, confirming with that passkey, then register a new one. You can rename a passkey or choose Remove passkey and confirm with an existing passkey. Removing the last passkey leaves the account without a registered security method. Lost-passkey recovery is not available in this release.
Accounts with a registered passkey must complete Verify your sign-in after Firebase sign-in before accessing protected RDC APIs. Accounts without a passkey can continue using Firebase sign-in alone. Choose Verify with passkey on the account portal; canceling the prompt does not complete sign-in.
Verification belongs to the current session and lasts up to 12 hours. Moving to Console or Workbench does not extend it. When verification expires or your registered methods change, RDC asks you to verify again. Direct API requests with only a Firebase token are rejected for enrolled accounts. Existing CLI access tokens are managed separately. Resource deletion requires a verified session but does not request a separate passkey prompt for each deletion. Danger zone does not provide account deletion yet.
Console and Workbench can show Secure your account when a current API check confirms that you have no registered methods. Choose Skip for 3 days to hide it for 72 hours in the same browser across the production RDC domains. The preference is account-specific and stored in a shared cookie, not an authentication token. Different browsers, devices, and unrelated preview domains have separate preferences. Clearing cookies can make the reminder appear sooner. If the registration check fails, the app does not assume that you have no passkey.
New passkeys use your account email as the account label in the browser or password manager. Accounts without an email use their internal account ID as a fallback. Existing saved passkey labels are not automatically updated. The passkey name you enter in RDC labels the method in your account settings; it is separate from the account email shown by the password manager.
Passkeys are registered for the Auth portal hostname. Local development uses its configured localhost origin; changing the Auth hostname does not migrate existing credentials. If a ceremony expires, fails, or is canceled, start a new attempt. A passkey can remain in your authenticator after a server save fails; it is not active in RDC until server registration succeeds.
The status separates request preparation, browser confirmation, and saving. A preparation failure happens before the browser prompt starts. Use a supported browser over HTTPS; address configuration errors require the official Auth portal or a matching local Auth origin. If saving fails, check the refreshed passkey list before retrying.
API integration
Passkey management endpoints use /v1/auth/security/passkeys. They require a Firebase ID token for the active account. The collection supports listing; registration-options, register, authentication-options, verify, rename, and revoke are management actions under that path. Successful registration returns HTTP 201. Login status uses GET /v1/auth/security/session. After authentication-options and verify, exchange the one-use proof at POST /v1/auth/security/session/verify and immediately sign in with the returned Firebase custom token. Do not persist the proof or custom token. Status and these verification endpoints accept a first-factor Firebase token; other protected APIs require completed verification for enrolled accounts.
Sign out
Signing out of Console takes you to the account portal, where you can also sign out of the portal. If you keep the portal signed in, returning to Console can sign you in again without another password prompt. This does not revoke CLI access tokens or sign out other devices.
CLI device access
Open Access Token from the account menu to view CLI device logins and personal tokens. Each CLI login has its own token entry that you can revoke independently. See CLI login for browser approval and device access management.
Create a personal access token
Open Access Token from the account menu and select Create access token to open the panel on the right. Enter a token name, choose an expiry of 30, 90, or 365 days, and submit.
The panel stays open after creation so you can copy the secret. The secret is shown only during this session in the panel; closing the panel discards it. Store it securely before closing. If creation fails, your name and expiry selection remain available for retry.
The token table shows names, types, creation and expiry dates, and status. CLI entries also show their device information and last use when available. Use Revoke on an active token to invalidate it.