OdyCust/ GUIDE
УКР

Getting started

Choose an organization and find the work you need.

Step by step

  1. In the header, use the flag to change language. The theme button cycles light → dark → automatic; A marks automatic mode and the sun/moon shows the effective appearance. Your choice is saved in this browser. The profile menu contains organizations, settings and sign out. Another organization requires its ordinary login. The OdyCust mark opens the full organization list.
  2. 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.
  3. Open your organization’s link (/app/UUID/login). If you do not have it, enter the organization ID supplied by its administrator on the sign-in page.
  4. 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.
  5. Choose an organization. If the list is empty, accept your invitation and refresh it. Signing in alone does not create a membership.
  6. Reloading a saved workspace link opens that same page when the server confirms the active organization membership and current access. If that check cannot confirm access, choose Open workspace explicitly. Sign-in, authentication return and organization switching retain their own steps; no business operation is repeated.
  7. The sidebar prioritizes daily work and directories. Less-used entries disappear when space is limited and return as the window grows; the active branch stays visible. All sections and Ctrl/⌘ K reach every permitted destination. Open user and organization settings from the profile menu, and Help from the header question mark. Navigation does not scroll or cut rows.
  8. Sources contains Wallets and Addresses; Transactions groups the available transfer sections. Hover or focus a whole parent row to see its children. Clicking its label opens the section. The current branch also shows its children inline, and direct child links preserve the active branch. Each destination requires its own permissions.
  9. Daily screens show the main information and contextual actions. Open Advanced tools explicitly where available for detailed configuration. There is no global presentation selector; old saved views no longer change the interface. Organization settings contains permitted management sections; Blockchains configures exact enabled networks.
  10. Use Add public address to track an existing crypto address: select the correct network, paste the public address and give it a label. Availability depends on access; this does not create keys or spending authority.
  11. The workspace fills the window; long lists scroll in the main area. All sections is also pinned in the mobile drawer. Language, theme and account controls stay in the header. The desktop footer shows the CRM version, the last nine characters of its commit and a modified marker when local changes exist.
  12. Section content adapts to the window: centered on wide screens and filling the available width on mobile. Overview uses the entire workspace for charts. Wide tables scroll inside their own region.
  13. Demo population adds only non-blockchain records such as Customers and Tags. Wallet addresses, transactions, balances and history must come from real connected networks and verified operations. Empty blockchain sections are normal until real activity; restarting the application preserves current data.
  14. The header refresh icon reloads visible data. The path beside it links to prior sections; its final item is the current page. From a wallet’s address list, Wallet returns to that exact wallet. Narrow screens retain the nearest parent. Navigation never repeats a business command.

Interface

Getting started — Illustration from an earlier CRM version with fictional training data. Layout may differ; the text describes current actions. This is not payment evidence.
Illustration from an earlier CRM version with fictional training data. Layout may differ; the text describes current actions. This is not payment evidence.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

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