Make It Yours—and Keep It Secure

Your workspace should be comfortable to use, and your account should be protected in a way you understand. This chapter brings those two goals together. We will adjust how you think about Settings before asking you to change anything. By the end, you should know where to find a preference, how to recognize your sign-in protections, and where to look when access needs attention.

Start by confirming the TraderLobby account shown in the account menu. Then open Settings from the main navigation. On a phone, use the mobile navigation to find Settings. Follow the section name rather than a particular position on the screen. A narrow display may stack controls that appear side by side on desktop.

Settings has five sections. You can open Preferences, Support, Security, Recovery, or the Advanced section. Preferences contains appearance and portfolio display choices. Support provides a route for asking for help. Security contains account-protection controls and account information. Recovery is for saved requests to sell assets, not for recovering your sign-in. The Advanced section contains controls for accounts with particular access. You do not need those controls to complete this lesson.

Opening a section lets you inspect it. Pressing a button inside that section can do something more. Choosing a theme changes presentation. Sending an email code starts a verification request. Signing out another device changes that device's access. These actions have different purposes, even though they all begin on the Settings page.

Some accounts may show restricted administrator controls. Those are for authorized platform operations, not routine customer customization. You do not need to press them to complete this lesson or unlock your learning progress. If a control belongs to a role you do not have, recognize that boundary and continue with the customer settings available to you.

Read the result after any setting change you intentionally make. A message, a changed status, or an updated list tells you more than the fact that you pressed a button. If the page is loading or reports an error, do not treat the unfinished display as confirmation that a security change succeeded.

For this first check, locate Preferences, Support, and Security. Explain which one you would use to make the screen easier to read, which one helps with an account question, and which one contains sign-in protection. Leave all account actions untouched. Knowing where to go is the first useful skill.

Let's begin with changes that make the workspace easier to read. Open Preferences and find Appearance. The theme control offers choices for the screen's appearance. Auto follows the device's appearance setting. Light and Dark let you choose the look directly. Pick the option that helps you read labels and values comfortably; a theme does not change the account's trading activity.

Next, find Language. The current interface offers English and Spanish. Choosing a language updates supported customer-facing text, including navigation. It does not change the exchange account, switch Paper to Live, or convert a balance into another currency. A trading pair still needs to be read on its own terms.

Some content can remain in its original language. A captured screenshot may contain English labels, and an English recording remains English unless a translated recording is provided. If the interface and lesson content use different languages, check the available labels and transcript rather than assuming the selection has failed.

Now find Portfolio display. The Hide dust preference controls whether very small holdings appear in the table. Here, dust means a holding whose current U.S. dollar value is below the selected threshold. It does not mean the holding is unwanted, worthless, or no longer yours.

Imagine an example holding worth forty cents. With Hide dust on and a threshold of less than one dollar, that holding can be hidden from the table. Your ownership and portfolio totals do not disappear. With a threshold of less than ten cents, that same forty-cent holding is above the threshold and would not be hidden by this particular rule.

The available thresholds include less than one cent, ten cents, one dollar, and five dollars. The threshold control is disabled when Hide dust is off, because the hiding rule is not being applied. Market prices can also change whether a holding falls below a chosen threshold. Read the current value and setting together.

If a small holding seems to be missing, inspect Hide dust and the table's other filters before concluding that it was sold. Turning off a display filter can help you find it again. Showing or hiding a row does not place a buy or sell order, and it does not promise that a tiny amount meets an exchange's minimum order size.

On mobile, return to Settings and locate the same preference by its label. Do not assume another device has already adopted your preferred layout; check what that device actually shows. For practice, you may choose one theme and then restore your preferred choice. You can also leave everything unchanged and explain what Hide dust does. Your answer should include the distinction between hiding a row and changing what the account owns.

Open Security. The controls here protect access to your TraderLobby identity. We will look at three sign-in tools: a password, an authenticator app, and a passkey. They have different jobs. You do not need to change any of them just to follow the explanation.

Start with Change Password. The form asks for the current password, the new password, and confirmation of the new password. Confirmation means entering the new value again so the app can check that the two entries agree. Apply submits the request. A successful result displays Password updated. If the form reports an error, read it and resolve that issue instead of assuming the change was saved.

Choose a unique password that you do not use for other accounts. A password manager can help you create and keep it. Follow the requirements shown by the actual password flow; changing a password while signed in and resetting a forgotten password are different routes. If you cannot provide the current password, the forgotten-password route is the relevant one to inspect. Do not guess repeatedly in the change form.

Next, find Multi-factor authentication and Authenticator app. Multi-factor authentication, often shortened to MFA, adds another check to the sign-in process. In this flow, an authenticator app generates a short code that changes over time. That code is separate from your password and separate from an email verification code.

If setup is available and you intentionally choose to enable it later, Set up MFA begins the process. Add the displayed account to your authenticator by scanning its setup code, or use the setup-key option if scanning is not possible. Then enter the authenticator's current six-digit code in TraderLobby and choose Confirm and enable. Opening the setup screen alone does not complete enrollment. Look for Enabled and the successful completion message.

Treat the setup image and setup key as private. They are not decorative pictures to share in a support post. After successful setup, the app displays recovery codes. Those deserve their own careful step, which we will cover on the next page. Do not disable MFA simply to repeat the demonstration.

Finally, find Passkeys. When this feature is configured for the environment and supported by your device, Add a passkey starts a device sign-in setup. Your device may ask for its PIN, a biometric check, or a security key. Approve only the setup you intentionally started. Look for Passkey added and the updated list before considering it complete.

If passkeys are unavailable, read the explanation and keep using the supported sign-in route. If a device prompt is canceled or fails, that is not proof a passkey was saved. Removing a listed passkey changes an access method, so keep another working method available before considering removal.

Your check is to locate the password form, authenticator status, and passkey area. Explain what confirms each successful setup. You do not need to enter a password, scan a setup image, or remove any protection to complete this page.

Verification and account recovery answer different questions. Verification checks something about access or identity. Account recovery helps you regain access when a normal sign-in step is unavailable. The Recovery tab in Settings is for saved requests to sell assets; it is separate from the sign-in recovery methods described on this page. Keeping those jobs separate makes the screens much easier to understand.

In Security, find Identity verification. The email entry shows a partially hidden address and its status. Check that the address looks like the one you expect. When verification is required, Send email code requests a message. Enter the received code in the verification field and choose Verify. Look for the verified status afterward. A message saying that a code was sent is not the same as a message saying the email is verified.

If the code does not arrive, check the destination and your mailbox, including its spam folder. Read any delivery or error message in the app. If delivery is blocked, use the supported help route rather than repeatedly requesting more messages. Never share the code in a community post or a screenshot for this lesson.

Email verification is one account check. It does not by itself prove that every Live requirement has been met, that an exchange is connected, or that Creator payout verification is complete. Those are separate processes with their own status. Follow the requirements actually shown for your account and the feature you intend to use.

Now return to the recovery codes displayed after authenticator setup. These are one-time backup codes. Each works once, and the Settings screen says they will not be displayed again. Save them privately before dismissing that display. The I saved them button dismisses the visible codes; it does not create a backup for you.

Keep the backup somewhere secure that you can reach if the device containing your authenticator is unavailable. A protected password manager or another secure recovery arrangement can help. Do not leave the only copy inside a device you would be unable to unlock or access. The useful question is whether you can retrieve the backup when you actually need it.

When MFA is enabled, Settings shows how many unused recovery codes remain. That count is not a way to reveal the codes again. If you no longer have a usable recovery method, review the supported recovery options while you still have access. Do not disable protection just to see whether the lesson's example can be repeated.

At sign-in, the authenticator challenge offers a recovery-code field for that situation. Use a saved MFA recovery code only in the appropriate sign-in flow. It is different from the code emailed by the forgotten-password process. In that process, you identify the account email, request the recovery message, and use the offered code and new-password fields. Read the instructions for the current code before submitting.

For your check, explain four things: what an email verification code verifies, what an authenticator code does, why an MFA recovery code needs secure storage, and where a forgotten password is handled. Keep every real code private. The goal is a recovery plan you understand, not a screen full of secrets.

Protecting an account includes understanding where it is signed in. In Security, find Devices and sessions. A session is a signed-in connection between a device or browser and your TraderLobby account. The current one is marked This device and Current.

Other entries can include browser or device information, a last-active time, and a network address. Use those details together. A network address can change, and a familiar device may be described by its browser software rather than the name you gave it. One unfamiliar-looking detail is a reason to inspect the entry, not automatic proof of what happened.

For another listed session, Sign out device revokes that session's access. When multiple sessions exist, Sign out all other devices is also offered. Read the difference between one entry and all other entries. After an intentional sign-out, check the updated list and any result message. Do not use these controls as a practice click during the lesson.

If you are worried about an unfamiliar session, consider the evidence and the account's protection together. Review recent security activity, your sign-in methods, and whether help is needed. If the session list has not loaded, do not interpret a blank list as a completed sign-out or a clean bill of health. Wait for a reliable result before drawing a conclusion.

Now connect this to the dashboard lesson. Signing in to TraderLobby and connecting an exchange are different layers. TraderLobby sign-in determines access to this app. An exchange connection determines which exchange account is linked and which actions that connection permits. A password change in TraderLobby should not be treated as confirmation that exchange permissions or credentials were changed too.

Use API Connections to inspect the exchange context available in your version. Check the provider, selected connection, and the status and permissions actually shown. Do not reveal API entries or private connection details in a shared screenshot. Reading an account and placing trades are different capabilities; a connection name alone does not explain its access.

Device sign-out is also separate from trading control. Do not use it as a substitute for stopping enabled automation. Closing a browser, switching to Paper, removing a sign-in method, and disconnecting an exchange are not interchangeable actions. If you intend to stop a strategy or close a position, follow the relevant trading workflow and verify its outcome.

For your check, locate the Current session without exposing its private details. Explain which control addresses another device's sign-in and which section addresses exchange connections. Then explain why a security change should not be used as evidence that trading stopped. You can complete all three parts by inspecting labels and describing their purpose.

Privacy is partly about understanding what information you are viewing and where you send it. Settings contains useful account records, but different records have different purposes. Let's start with a concrete example.

In Security, find Security activity. This section shows recent identity and account-protection events. Export CSV downloads a copy of that security activity. A CSV is a simple table file that can be opened by spreadsheet software. This particular export is not a complete download of every account record, every message, or every trade.

If you intentionally export it, check that the download completed and store the file privately. Account activity can contain details you would not want to post publicly. An error means you do not yet have a confirmed export. For this lesson, locating the button and explaining its scope is enough; you do not need to download anything.

For a privacy or account question that is not answered by the available controls, open Support and use the help route shown there. Describe the issue and the result you need. Do not include passwords, authenticator setup keys, recovery codes, API secrets, or unneeded personal details. A public community channel is not the place to share sensitive account evidence.

The current Settings page also includes Account deletion. Read its explanation before touching the confirmation field. This control submits a request for review. It does not immediately erase the account's data, cancel subscriptions, close exchange connections, or stop trading. A request and a completed deletion are different stages.

The page requires an explicit confirmation word before submission. We are not going to enter it during this lesson. Knowing where the control is and what it means does not require creating a real request. If you genuinely decide to request deletion later, review the consequences and the current instructions first, including any separate actions needed for trading or billing.

After a request is submitted, the page can show a request identifier, a submitted time, and its status. Those details help you follow the review. An open request is not a completion notice, and a failed submission should not be described as a successful deletion. Do not promise yourself a completion date that the app has not confirmed.

Creators also need to read the additional explanation about strategies with paying subscribers. Account departure and ongoing subscriber access can require separate handling. The Creator lifecycle lessons cover that branch in more detail. Do not assume requesting deletion immediately removes every subscribed strategy or settles every account obligation.

Your check is to find Security activity, explain what its export contains, and locate the deletion-request explanation without submitting it. Then name the separate areas you would inspect for subscriptions, exchange access, and trading state. Understanding those boundaries is the main lesson here.

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.