> ## Documentation Index > Fetch the complete documentation index at: https://docs.rails.wayex.com/llms.txt > Use this file to discover all available pages before exploring further. # Console overview > What the Wayex console is, who signs in, and a tour of every section. The **Wayex console** is the institutional UI for your team. It is a presentation layer over the same API you can call directly. Use it to onboard direct-route customers or operate a prefunded Treasury account without writing code. The sandbox console is an integration environment. Wayex may connect an explicitly enabled tenant to controlled live-provider rails. Treat displayed funding instructions as value-bearing and follow your agreed environment and test limits. ## Who signs in The console is for **your staff** — the people at your organisation who onboard end customers and set up payment routes or operate Treasury. Each person signs in with their own user, and what they can see and do is governed by their [role](/console/team-roles). Your end customers never sign in to the console. The login belongs to one tenant account. Staff use the login for the account they intend to operate. Every account's wallets, settings, webhooks, and history remain isolated. ## Signing in Sign in with your **email and password**. Each person on your team has their own account — there is no shared login and no separate identity provider to visit. You enter your credentials on the console's sign-in screen and are taken straight in. Navigate to your console URL. If you are not signed in, you land on the sign-in screen. Type the email and password for your account and select **Sign in**. Your role and capabilities load automatically and are reflected in the navigation and the actions available to you. ### First-time setup The first administrator at a new organisation receives an **invitation link** by email. Opening it lets them set a password and activate the organisation. Invitation links expire and can be used only once — if yours no longer works, ask your Wayex contact to send a fresh one. The first time you sign in from an invitation — or after an administrator resets your account — the console asks you to set a permanent password before you continue. On every sign-in after that, your email and password take you straight in. To sign out, open the account menu in the top-right and select **Sign out**. ## A tour of the console A compact navigation sits at the top-left, with a live **activity feed** below it that shows recent transfers across all of your customers in reverse-chronological order. Your dashboard for the products enabled on this tenant account, including work that needs attention. Fund an isolated wallet, manage beneficiaries, make AUD payouts, convert, withdraw stablecoin, and reconcile transaction history. Onboard end customers by email, track their verification status, and manage what each is entitled to do. **Payment routes live inside each customer** — they are where money moves. Where money moves. Create a standing route under a customer — off-ramp (stablecoin to AUD) or on-ramp (AUD to stablecoin) — and the customer funds it any time. Wayex converts automatically at the live rate the moment funds land. A live feed of every transfer across your customers, each opening a detail view with the full lifecycle timeline and linked references. The **live indicative rate right now** — what a customer would get if they converted this instant. It is the all-in rate Wayex quotes, indicative only, and never binds; the binding price is struck fresh when a route's funds land. Your developer-fee revenue over time — headline totals per asset, a by-asset breakdown, and a time series of the fees you charge your customers on each conversion. Read-only roles see the same screens but with create and edit actions hidden or disabled. Wherever an action is unavailable to your role, the console explains why. ## Reading money and status * **Money** is always shown with its currency (and network, for crypto) exactly as the API returns it — values are never rounded or recomputed in the browser. * **Status** is always shown explicitly. A held, failed, or returned transfer is never hidden or collapsed into "success"; it is surfaced with its reason so you know what to do next. * **Availability** is explicit. Pending and reserved money is not spendable, `accepted` is not external settlement, and stale or unknown data never appears as zero.