Ask before sending, double-click, and when an order is refused
Under the risk row sit two ticks that change how the desk asks before acting. Both are saved with your profile. Ask before sending shows a yes or no box before you close or cancel: closing a position, FLATTEN ALL, LIQUIDATE ALL, cancelling orders, and a double-click send.
In this video
The 30-second version
The same topic in thirty seconds, made for a phone screen.
Both videos use the desk in paper mode with made-up symbols and prices.
Read the transcript
Two safety ticks
Under the risk row sit two ticks that change how the desk asks before acting. Both are saved with your profile.
Ask before sending
Ask before sending shows a yes or no box before you close or cancel: closing a position, FLATTEN ALL, LIQUIDATE ALL, cancelling orders, and a double-click send. It does not ask on BUY, SHORT or their hotkeys, and automatic entries never ask: arming is their gate.
Double-click sends orders
Then a double-click on a scanner, watchlist or gapper row only arms that stock. Tick it, and the same double-click also sends a buy at your order size. With Ask before sending ticked, a double-click send asks first too.
When an order is refused
Orders bigger than your buying power are still sent, and the broker decides. If the broker refuses one for buying power, a window says what the order needed, your buying power as the desk last read it, and the most shares that would fit. The window also says how long ago the desk last read your buying power.
Refused for locates
If the broker refuses a short for locates or borrowing, a window shows the order, the borrow status, the locates you hold, and the broker's own message. It opens every time for a manual short, and once per stock per session for an automatic one. Read the broker's message before you try again. In paper, shorts need no locates at all.
Always in the log
And every refusal is written in the order log, with the broker's reply, so you can always see exactly what was asked, and exactly what came back. A refusal you miss on screen is still in the log.