WEBVTT

00:00:01.300 --> 00:00:05.988
Protecting an account includes understanding where it is signed in. In Security,

00:00:05.988 --> 00:00:10.675
find Devices and sessions. A session is a signed-in connection between a

00:00:10.675 --> 00:00:15.362
device or browser and your TraderLobby account. The current one is marked

00:00:15.362 --> 00:00:16.925
This device and Current.

00:00:17.425 --> 00:00:21.666
Other entries can include browser or device information, a last-active time, and

00:00:21.666 --> 00:00:25.908
a network address. Use those details together. A network address can change,

00:00:25.908 --> 00:00:30.149
and a familiar device may be described by its browser software rather

00:00:30.149 --> 00:00:34.391
than the name you gave it. One unfamiliar-looking detail is a reason

00:00:34.391 --> 00:00:37.925
to inspect the entry, not automatic proof of what happened.

00:00:38.425 --> 00:00:42.593
For another listed session, Sign out device revokes that session's access. When

00:00:42.593 --> 00:00:46.762
multiple sessions exist, Sign out all other devices is also offered. Read

00:00:46.762 --> 00:00:50.930
the difference between one entry and all other entries. After an intentional

00:00:50.930 --> 00:00:55.099
sign-out, check the updated list and any result message. Do not use

00:00:55.099 --> 00:00:58.225
these controls as a practice click during the lesson.

00:00:58.725 --> 00:01:02.565
If you are worried about an unfamiliar session, consider the evidence and

00:01:02.565 --> 00:01:06.405
the account's protection together. Review recent security activity, your sign-in methods, and

00:01:06.405 --> 00:01:10.245
whether help is needed. If the session list has not loaded, do

00:01:10.245 --> 00:01:14.085
not interpret a blank list as a completed sign-out or a clean

00:01:14.085 --> 00:01:17.925
bill of health. Wait for a reliable result before drawing a conclusion.

00:01:18.425 --> 00:01:22.701
Now connect this to the dashboard lesson. Signing in to TraderLobby and

00:01:22.701 --> 00:01:26.978
connecting an exchange are different layers. TraderLobby sign-in determines access to this

00:01:26.978 --> 00:01:31.254
app. An exchange connection determines which exchange account is linked and which

00:01:31.254 --> 00:01:35.530
actions that connection permits. A password change in TraderLobby should not be

00:01:35.530 --> 00:01:39.450
treated as confirmation that exchange permissions or credentials were changed too.

00:01:39.950 --> 00:01:44.412
Use API Connections to inspect the exchange context available in your version.

00:01:44.412 --> 00:01:48.874
Check the provider, selected connection, and the status and permissions actually shown.

00:01:48.874 --> 00:01:53.335
Do not reveal API entries or private connection details in a shared

00:01:53.335 --> 00:01:57.797
screenshot. Reading an account and placing trades are different capabilities; a connection

00:01:57.797 --> 00:02:00.400
name alone does not explain its access.

00:02:00.900 --> 00:02:05.237
Device sign-out is also separate from trading control. Do not use it

00:02:05.237 --> 00:02:09.574
as a substitute for stopping enabled automation. Closing a browser, switching to

00:02:09.574 --> 00:02:13.911
Paper, removing a sign-in method, and disconnecting an exchange are not interchangeable

00:02:13.911 --> 00:02:18.247
actions. If you intend to stop a strategy or close a position,

00:02:18.247 --> 00:02:21.500
follow the relevant trading workflow and verify its outcome.

00:02:22.000 --> 00:02:26.534
For your check, locate the Current session without exposing its private details.

00:02:26.534 --> 00:02:31.068
Explain which control addresses another device's sign-in and which section addresses exchange

00:02:31.068 --> 00:02:35.602
connections. Then explain why a security change should not be used as

00:02:35.602 --> 00:02:40.136
evidence that trading stopped. You can complete all three parts by inspecting

00:02:40.136 --> 00:02:42.025
labels and describing their purpose.