Now let’s build a simple map of the app. You do not need to remember the location of every button. Start by learning which section answers which kind of question. When you know what you’re trying to find, the menu becomes a useful guide instead of a list of unfamiliar names.

On desktop, use the navigation rail along the side of the workspace. If the rail is collapsed to icons, expand it to read the section labels. On the mobile layout, open the navigation menu to see the section names. The arrangement is more compact, and the trading area may be labeled Portfolio. Read the heading after opening a section so you can confirm where you arrived.

The Trading workspace is where you inspect markets, positions, and trading controls. Strategies is where you explore the strategy features available to you. API connections is the area for exchange connections. Here, API means the way one service allows another service to communicate with it. You do not need to write code to understand the purpose of the connection page.

Transactions and Reporting answer different questions. Transactions helps you follow individual account events, such as an execution or a movement recorded in the ledger. Reporting helps you review results across a selected period. If you want to investigate one specific event, start with Transactions. If you want to understand a broader pattern, Reporting may be the more useful starting point. You’ll learn how to check their account and time settings later.

Billing is for the plans, subscriptions, and charges available to your account. Settings contains preferences and account controls. Community is for discussions and interaction with other people. Learn is where you are now: the lesson library and app guide. You can visit these sections without treating every available control as something you need to activate.

Some sections open another view inside the section. For example, a lesson opens from a chapter card, and a discussion can open from a community list. Look for the back or close control belonging to that view. On mobile, the Learn screen has its own close button. Closing that screen returns you to the underlying app; it does not sign you out.

The browser’s Back button follows browser history. A control inside the app follows the action assigned to that particular view. Neither should be treated as an undo button for a submitted order or an account change. Leaving a screen does not prove that an action was canceled. For an action that changes something, check its confirmation or status in the relevant section.

Try a short navigation check. Identify where you would look for an exchange connection, a past account event, and an account preference. The answers are API connections, Transactions, and Settings. Then locate Learn again. If you are following along while listening, you can pause first and return to the lesson afterward. The aim is to find your way confidently, not to move through the menus quickly.