WEBVTT 00:00:01.300 --> 00:00:05.133 Let's turn what you have learned into a short review you can 00:00:05.133 --> 00:00:08.967 repeat. You can pause after each step. This is a check of 00:00:08.967 --> 00:00:12.800 your understanding and readiness, not a requirement to change a working setup. 00:00:13.300 --> 00:00:17.486 First, confirm your account identity. Make sure you know which TraderLobby user 00:00:17.486 --> 00:00:21.672 is signed in before reviewing account details. If you are on a 00:00:21.672 --> 00:00:25.858 shared device, keep private information out of view and use the appropriate 00:00:25.858 --> 00:00:28.300 sign-out process when your work is finished. 00:00:28.800 --> 00:00:32.927 Second, inspect Preferences. Choose a readable theme, check the interface language, and 00:00:32.927 --> 00:00:37.053 understand your Hide dust setting. Explain why hiding a small holding does 00:00:37.053 --> 00:00:41.180 not sell it or remove its value from the totals. You can 00:00:41.180 --> 00:00:45.306 leave every preference as it is if the current setup works for 00:00:45.306 --> 00:00:45.650 you. 00:00:46.150 --> 00:00:50.725 Third, inspect sign-in protection. Find the authenticator status and the available passkey 00:00:50.725 --> 00:00:55.300 information. Know which sign-in methods you can actually use. A listed passkey, 00:00:55.300 --> 00:00:59.875 an enabled authenticator, and a password-change success message each describe a specific 00:00:59.875 --> 00:01:04.450 result. None of them is a reason to stop reading the rest 00:01:04.450 --> 00:01:05.975 of the account context. 00:01:06.475 --> 00:01:10.622 Fourth, review verification and recovery readiness. Check the email status and whether 00:01:10.622 --> 00:01:14.769 you have a secure way to recover access if your usual device 00:01:14.769 --> 00:01:18.916 is unavailable. You do not need to display or test a recovery 00:01:18.916 --> 00:01:23.063 code during this check. Being able to retrieve it privately when needed 00:01:23.063 --> 00:01:24.100 is what matters. 00:01:24.600 --> 00:01:29.112 Fifth, inspect Devices and sessions and the recent Security activity. Identify the 00:01:29.112 --> 00:01:33.624 current session and consider whether the other entries fit your own activity. 00:01:33.624 --> 00:01:38.135 If something needs attention, use the relevant account-protection or help workflow. Do 00:01:38.135 --> 00:01:42.647 not remove access methods or sign out devices simply to make the 00:01:42.647 --> 00:01:43.775 page look tidy. 00:01:44.275 --> 00:01:48.537 Sixth, connect account protection to exchange context. Know where API Connections is 00:01:48.537 --> 00:01:52.800 and remember that its permissions are separate from TraderLobby sign-in. If you 00:01:52.800 --> 00:01:57.062 have no exchange connection, that is a valid state for following these 00:01:57.062 --> 00:02:01.324 lessons. You do not need to connect an exchange or enter Live 00:02:01.324 --> 00:02:03.100 mode to finish this chapter. 00:02:03.600 --> 00:02:08.655 Finally, locate Support and understand the account-request controls. Know that a security-activity 00:02:08.655 --> 00:02:13.710 export has a specific scope and that deletion is a request for 00:02:13.710 --> 00:02:18.765 review. Neither is a substitute for managing a subscription, stopping automation, or 00:02:18.765 --> 00:02:20.450 reviewing a trading outcome. 00:02:20.950 --> 00:02:24.942 If one of these steps reveals a gap, make a private note 00:02:24.942 --> 00:02:28.935 of the next appropriate action. Keep the note about the task, such 00:02:28.935 --> 00:02:32.927 as checking an unfamiliar session or organizing recovery storage, rather than writing 00:02:32.927 --> 00:02:36.919 secrets into it. Address one issue carefully and verify the result before 00:02:36.919 --> 00:02:38.250 moving to the next. 00:02:38.750 --> 00:02:42.417 You now have a workspace you can understand and a clearer picture 00:02:42.417 --> 00:02:46.083 of how its account protections fit together. Next, we will look closely 00:02:46.083 --> 00:02:49.750 at exchange connections: which account is connected, what access it has, and 00:02:49.750 --> 00:02:53.417 how to recognize the result of a connection request. Bring the same 00:02:53.417 --> 00:02:57.083 habit with you: read the scope, take the intended action, and check 00:02:57.083 --> 00:02:58.000 what actually happened.