WEBVTT

00:00:01.300 --> 00:00:05.721
A connection's permissions answer a direct question: what is this credential allowed

00:00:05.721 --> 00:00:10.142
to do? Start with three groups. Reading information lets software request supported

00:00:10.142 --> 00:00:14.562
account details. Trading access allows supported order requests. Moving assets, such as

00:00:14.562 --> 00:00:18.983
withdrawing them, is a different kind of access. One group does not

00:00:18.983 --> 00:00:20.825
automatically include every other group.

00:00:21.325 --> 00:00:25.771
For TraderLobby, follow the permissions required by the supported workflow. Do not

00:00:25.771 --> 00:00:30.217
grant withdrawal or unrelated account access to make an error disappear. Use

00:00:30.217 --> 00:00:34.663
the provider-specific guidance beside the form. The permission names can differ by

00:00:34.663 --> 00:00:39.109
exchange, so copying a list from a different provider is not a

00:00:39.109 --> 00:00:39.850
reliable shortcut.

00:00:40.350 --> 00:00:44.450
The current Kraken guidance names access for funds, open and closed orders,

00:00:44.450 --> 00:00:48.550
creating or modifying orders, and canceling or closing orders. The Gemini guidance

00:00:48.550 --> 00:00:52.650
calls for a dedicated account-level key with the Trader role, rather than

00:00:52.650 --> 00:00:56.750
a master key or Fund Manager role. These are examples of why

00:00:56.750 --> 00:01:00.850
the full instructions matter more than a vague instruction to enable everything.

00:01:01.350 --> 00:01:05.596
The Binance U.S. guidance distinguishes account reading and Spot trading. The Binance

00:01:05.596 --> 00:01:09.842
dot com guidance uses a provider permission label that includes the words

00:01:09.842 --> 00:01:14.087
Spot and Margin Trading, while explaining that TraderLobby uses Spot only. Read

00:01:14.087 --> 00:01:18.333
both the label and the explanation. That combined label is not an

00:01:18.333 --> 00:01:22.225
instruction to borrow money or begin margin trading. Keep withdrawals disabled.

00:01:22.725 --> 00:01:26.385
After a connection is saved, the desktop card includes Validate order permissions,

00:01:26.385 --> 00:01:30.045
with a button that explicitly says no order placed. This is a

00:01:30.045 --> 00:01:33.705
separate check from saving the connection. The app asks for a provider-specific

00:01:33.705 --> 00:01:37.365
validation result; it does not use this button to make a small

00:01:37.365 --> 00:01:41.025
purchase as a demonstration. You do not need to press Buy to

00:01:41.025 --> 00:01:42.550
prove that you understood it.

00:01:43.050 --> 00:01:47.001
The checks also differ in what they can establish. Coinbase checks View

00:01:47.001 --> 00:01:50.951
and Trade permissions. Kraken and the Binance choices use their supported validation

00:01:50.951 --> 00:01:54.902
or test routes. Robinhood requests a signed price estimate. Gemini's explanation says

00:01:54.902 --> 00:01:58.853
it checks the product, a protected execution price, and authenticated access, while

00:01:58.853 --> 00:02:02.804
the exchange confirms the Trader role on the first customer-authorized order. Read

00:02:02.804 --> 00:02:06.425
that limitation; do not treat every successful check as identical evidence.

00:02:06.925 --> 00:02:11.005
Look for the returned message and Last validated time when a check

00:02:11.005 --> 00:02:15.085
completes. A validation result describes the check performed at that time. It

00:02:15.085 --> 00:02:19.165
does not promise that every later order will succeed. Permissions, available cash,

00:02:19.165 --> 00:02:23.245
product support, and other requirements can still affect a later request. If

00:02:23.245 --> 00:02:27.325
the check fails, resolve the stated problem instead of widening access blindly.

00:02:27.825 --> 00:02:32.139
The current phone view offers Check connection, but does not present the

00:02:32.139 --> 00:02:36.453
desktop order-permission button. Those are not interchangeable checks. If you need the

00:02:36.453 --> 00:02:40.767
desktop workflow, use that view and follow its explanation. A mobile connection

00:02:40.767 --> 00:02:45.081
status alone should not be described as proof that the separate order

00:02:45.081 --> 00:02:45.800
check passed.

00:02:46.300 --> 00:02:50.914
For your check, name the difference between reading, trading, and withdrawing. Then

00:02:50.914 --> 00:02:55.529
explain what the no-order validation button does and one thing it cannot

00:02:55.529 --> 00:03:00.143
promise. You can answer without changing permissions or submitting any request. Understanding

00:03:00.143 --> 00:03:02.450
the scope is the useful result.