Let's turn what you have learned into a short review you can repeat. You can pause after each step. This is a check of your understanding and readiness, not a requirement to change a working setup.

First, confirm your account identity. Make sure you know which TraderLobby user is signed in before reviewing account details. If you are on a shared device, keep private information out of view and use the appropriate sign-out process when your work is finished.

Second, inspect Preferences. Choose a readable theme, check the interface language, and understand your Hide dust setting. Explain why hiding a small holding does not sell it or remove its value from the totals. You can leave every preference as it is if the current setup works for you.

Third, inspect sign-in protection. Find the authenticator status and the available passkey information. Know which sign-in methods you can actually use. A listed passkey, an enabled authenticator, and a password-change success message each describe a specific result. None of them is a reason to stop reading the rest of the account context.

Fourth, review verification and recovery readiness. Check the email status and whether you have a secure way to recover access if your usual device is unavailable. You do not need to display or test a recovery code during this check. Being able to retrieve it privately when needed is what matters.

Fifth, inspect Devices and sessions and the recent Security activity. Identify the current session and consider whether the other entries fit your own activity. If something needs attention, use the relevant account-protection or help workflow. Do not remove access methods or sign out devices simply to make the page look tidy.

Sixth, connect account protection to exchange context. Know where API Connections is and remember that its permissions are separate from TraderLobby sign-in. If you have no exchange connection, that is a valid state for following these lessons. You do not need to connect an exchange or enter Live mode to finish this chapter.

Finally, locate Support and understand the account-request controls. Know that a security-activity export has a specific scope and that deletion is a request for review. Neither is a substitute for managing a subscription, stopping automation, or reviewing a trading outcome.

If one of these steps reveals a gap, make a private note of the next appropriate action. Keep the note about the task, such as checking an unfamiliar session or organizing recovery storage, rather than writing secrets into it. Address one issue carefully and verify the result before moving to the next.

You now have a workspace you can understand and a clearer picture of how its account protections fit together. Next, we will look closely at exchange connections: which account is connected, what access it has, and how to recognize the result of a connection request. Bring the same habit with you: read the scope, take the intended action, and check what actually happened.