Organization
View the selected organization and manage its connected blockchains.
Step by step
- Check the selected organization in the sidebar. Business records belong to this context.
- Read the available organization information. An identifier in a form does not grant access to another organization.
- To switch, select the organization name and choose an available membership. Previously loaded data is cleared.
- After reloading the page, you may need to choose the organization again.
- Open Organization from administration or Find a section. Connected blockchains shows each exact network independently; mainnets and testnets can coexist.
- Use Connect or Disconnect only when offered. Review the exact network and confirm. A device confirmation may be required. Disabling a network preserves stored history and does not cancel already admitted financial operations.
- Choose Tokens to view the native asset and registered contracts. With management rights, choose the complete set that should remain enabled, then Review asset changes and Confirm change. Removing every selection disables every selectable asset, including the native asset.
- A version conflict or unknown result requires Check current state before another change. No request is repeated automatically. The operator owns RPC endpoints and secrets; connecting a network grants no transfer permission.
- The Tokens control on a network card shows up to three icons and +N when needed. Open it for the full list and permitted switches. The native fee coin is marked separately; token contract details can be expanded.
- Network availability reflects current platform and organization ceilings as well as saved activation. A saved connection can remain configured while the network is unavailable. Disabled administrative settings never turn into usable action buttons.
- On a supported testnet card, Get test tokens opens Faucet when current rights, token availability and server quota permit it. Select an exact token, full recipient address and a positive amount with up to six decimals. Review the shared limit: up to 10,000 nominal test units per organization and network every 12 hours, across members and tokens. These test units have no asserted fiat value.
- Submitting Faucet creates one queued request, not immediate funding. View Faucet request shows Queued, Submitted, Unknown, Confirmed or Failed. Check request status reads the original ID; a lost response, reload, unavailable worker or not-found lookup never automatically resends or creates a new request. Preserve the original journal until a matching terminal result, or an explicitly rejected admission. The server supplies the next available time; the browser does not unlock the quota with a local timer. Confirmation is not Invoice payment acceptance or Ledger credit.
- AUTH_STEP_UP_REQUIRED offers fresh session confirmation. AUTH_MFA_REQUIRED requires a new password-and-key login through the explicit sign-out path. Neither confirmation nor returning to this section replays a network change; review its current settings and submit again explicitly.