OdyCust/ GUIDE
УКР

Sign-in and security

Manage your own access from account security.

Step by step

  1. Use your organization sign-in link. Enter the password in CRM. With a configured dedicated auth host, choose Continue to authentication: the same tab opens key confirmation. API and documentation addresses are not sign-in pages.
  2. On the authentication page, choose Browser choice — all keys, This device — Touch ID / Windows Hello, or USB security key (FIDO2). Browser choice may also offer a phone or YubiKey; choose This device for the built-in authenticator. Connect the key through USB, enter its PIN only in the system prompt and touch it when requested. NFC depends on the device and browser. For adding a key, choose Confirm with an existing key and Save the new key separately: you can use a computer passkey first and enroll a USB key next. A cancelled or unsupported request never switches methods automatically.
  3. Sign in with your organization email and password. Current organization policy decides whether ordinary sign-in can use only a password or requires a key. An existing key does not automatically upgrade a password session. First-key enrollment requires its own email and device proof; setup alone does not sign you in.
  4. To sign in through your phone, choose Sign in with the app on your organization login page. In the already signed-in Android/iOS app, select the same organization and choose Scan QR to sign in. Compare the website, organization and six digits, select The website and code match, then Confirm sign-in with MFA and finish the security-key ceremony.
  5. The QR expires after two minutes. Cancel QR sign-in on the computer retires the request. Reject on the phone clears its local review and cannot undo an approval already sent. If the result is unconfirmed, use Check sign-in on the computer; do not keep approving. The browser receives its own session and still completes ordinary consent/organization selection. A scan or screen unlock alone grants no login or transfer. Matching backend/app versions and verified app-domain associations are required.
  6. After password-only sign-in with no registered key, Set up the first authenticator first asks you to explicitly end the current sign-in. Choose End current sign-in and set up key, then enter your email and password again and use the new email code. If sign-out or preparation fails, the form stays blocked: reload the page to check sign-in state. Sign-out is never automatic. After setup, save recovery codes and sign in with the new key.
  7. For first setup, enter the exact proof from the new email and choose Continue to create a passkey on your device. Setup alone does not sign you in, create a membership or grant administrator rights.
  8. When setup completes, choose Download codes and keep the recovery file privately. Choose Return to sign-in, enter your password again and confirm with the new passkey. Recovery codes are available only on this completion screen; save them before leaving.
  9. If verification start is rejected with AUTH_FLOW_INVALID before the key page opens, choose Start verification again and request a new email. A failure after returning has a separate explanation. If the completion response is lost, do not register again: check sign-in because the key may already be saved. Unfinished setup is not restored from browser storage.
  10. Use Account setup and recovery for password enrollment, manual first-authenticator setup, lost factors and credential repair. Follow the proof and device-verification instructions for the selected procedure.
  11. An active session exposes actions for your own authenticators. Adding a key on the auth host needs two confirmations: the existing key, then the new key. Choose Return to CRM, retrieve the original response and explicitly finish the action. Re-enter any required password or recovery code only in CRM. A role cannot waive the proof requirements.
  12. If the organization list is empty, Accept an invitation opens that action directly. Enter your own invitation token after ordinary password-and-device login. Acceptance creates membership, while assigned permissions determine its menus.
  13. After an administrator reset, choose Replace a temporary password. Enter your email, the single-use password and a new password. Then set up the first authenticator with email proof, save recovery codes and sign in again.
  14. If Create an organization is available on the general sign-in page (/app/login), use it to create a new workspace. An organization-specific sign-in page never registers accounts into that existing organization.
  15. Enter your new organization name and email, then choose Send verification code. No organization is created yet. Check your mailbox, enter Verification code, choose and confirm a password of at least 12 characters, then choose Verify and create. Organizations have no global Mainnet/Testnet mode; an authorized administrator enables each exact network separately after setup.
  16. If you already have the email code, choose I already have a code on the registration page. The original code works for 15 minutes. After a lost response, Retry the same confirmation reuses the original code and password; it does not create another organization. A resumed code returns the same organization if creation already succeeded, without changing its original password.
  17. When Organization created appears, choose Continue to sign-in and security and bookmark the resulting organization sign-in page. Re-enter your email and password there; no password or verification code is passed in the URL or stored by the application.
  18. After passkey setup, recovery-code download and a fresh signed login, Finish setting up your organization shows the remaining server-confirmed steps. Choose Accept membership, Open organization, Verify with passkey, and finally Activate owner access. Each action is separate; only the final confirmed step grants first-owner access.
  19. If setup is interrupted, sign in again through that organization’s link and continue its current step. Check current step reads the server state without repeating an action. A failed or unknown response does not justify registering a replacement organization. If the original code has expired after an unknown creation result and you have no sign-in link, contact support.
  20. The initial membership invitation lasts seven days. If it expires or is revoked before acceptance, setup shows Organization setup invitation expired. Contact the service operator; this interface cannot renew it.
  21. Native login opens a separate Sign in to the app page in the system browser. Check organization, application ID and return address, choose Continue confirmation, Confirm with security key, then Return to app. Only confirm your own request. Passwords and cookies never enter the app. Desktop keeps its session in memory; Android/iOS protect the refresh credential in OS secure storage. Matching backend/CRM, a registered client and mobile verified HTTPS domain are required. Physical devices and financial screens remain unqualified.
  22. After returning from confirmation of a sensitive action, finish confirmation and open the original review. Transfers, publication and deletion never replay automatically: review current data and confirm the intended action separately. Unsaved form fields may need to be entered again.
  23. An API outage shows maintenance. Checking connectivity never repeats a signature or write. The response on returning from the auth host can be retrieved only once: if it is lost, start a fresh confirmation. If sign-in or step-up completion may already have succeeded, check its state without resending the proof.
  24. Your registered security keys appear as separate cards with their registration dates. Technical details show each exact identifier; the API does not provide device names or last-used times. Remove selects that exact key for review. Required password/current-key proof and typed DELETE still apply; choosing a card does not revoke it.
  25. Account security reads your actual registered keys. With an existing key, use Confirm current session; first-key setup and its logout step are not offered. Having a key does not by itself confirm this session. The password reminder appears only after a successful read confirms no keys. Return to workspace stays in the current organization.
  26. If a protected setting requires a signed login, choose Sign in with a key again, then explicitly End current session and continue. Enter your password and confirm with an existing key. This path requests strict key verification, without password-only fallback. Choose Open workspace to return to the original section and review the change again. Adding another key is unnecessary. A failed sign-out blocks preparation until you reload and check the session.
  27. If the API accepted key confirmation but its current validity cannot be read, use Check current confirmation. The original proof is never resent. A rejected completion and a lost completion response have different messages; an unknown response permits only checking the original state.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.