Settings: trading guards (max quantity, confirmation)

The Trading section of Settings holds two guards applied to every order the desktop sends: an optional per-order contract cap and a 1-click or 2-click confirmation mode. Both are stored on the backend and shared by every window.

Senzoukria · Documentation · Updated September 2026

Where to find it

Where
Settings → Trading, and the chart's ⚙ Footprint settings → Trading Settings (same values)
Default confirmation
1 click — send immediately
Default cap
Empty = no cap
Storage
Backend file (trading guards), not the chart store

What it does

Senzoukria checks every order against two global guards before it reaches the broker driver: the maximum order size and the confirmation mode. They are enforced at the command layer in the Rust backend, so an order placed from the order ticket, the quick ticket on the chart or the chart's right-click menu meets the same rule. The Settings page describes this as "Guards are stored on the backend and shared by every window".

The Trading section of the app-wide Settings page exposes both guards. The chart's own Footprint settings modal (⚙ → Trading Settings) shows the same two controls and writes to the same backend record, so changing one place changes the other.

A third guard cannot be turned off from here: per-connection trading enablement (`trading_enabled` on the connection profile, off by default on funded environments). Cancel and flatten deliberately bypass it because they only reduce risk.

Settings

Trading guards as shown in Settings → Trading
SettingDefaultWhat it changes
Mode (Order confirmation)1 click — send immediately"2 clicks — confirm first" shows a recap dialog (side, quantity, instrument, type and TIF, price, account) before every submit. The order ticket and the chart quick ticket show it before sending; in the chart right-click menu only Flatten asks, through a plain confirmation.
Maximum order size (Contracts per order)Empty — no limitA whole number of contracts. Orders above it are refused by the backend with an explicit error. Empty, 0 or a negative value all mean no cap.

How to use it

Open Settings from the navigation and scroll to Trading. Pick the confirmation mode in the select; the change is saved immediately. Type a contract count in the Maximum order size field and leave the field (blur) to save it; in the chart modal, Enter also commits. The hint under the field reads either "Orders above {n} contracts are refused." or "No cap — your size is your call."

When confirmation is on, the Confirm order dialog appears with a Cancel button and a "Send BUY" / "Send SELL" button, focused by default. While the order is being sent the buttons show "Sending…" and the backdrop cannot dismiss the dialog.

  • The cap is a safety net against a slip of the finger, not a risk rule: on micro contracts twenty lots is an ordinary size, which is why the product ships with no cap.
  • The guard rejects the order with the message "order quantity N exceeds the max order size guard (M) — raise it in Trading settings if intended".

Limits or pitfalls

  • The confirmation dialog is a frontend step; the backend stores the flag so every window agrees, but a quantity above the cap is refused even when confirmation is off.
  • A guards file written before the field existed carried a cap nobody had chosen; the app lifts it once on load (guards version 1) and logs the value it removed. Any cap you set afterwards is kept.
  • If saving fails, the error text is shown under the controls and the previous values remain in force.
  • Quantity must be greater than zero in all cases; a zero-quantity order is refused independently of the cap.

This page in other languages

Frequently asked questions

Is 2-click confirmation on by default?
No. The backend default is "1 click — send immediately". Choose "2 clicks — confirm first" in Settings → Trading or in the chart's Trading Settings tab to see the recap dialog before each order.
Does the maximum order size apply to the chart quick ticket?
Yes. The cap is checked by the backend before any order reaches the driver, so it covers the order ticket, the quick ticket pinned on the chart and the right-click menu alike.
What does an empty Maximum order size mean?
No cap. The field's placeholder reads "no limit"; entering 0 or clearing the field saves the same thing.

Keep reading

Strategy researchTest a trading strategy, from observation to challenge rulesDefine an observation, question it with the copilot, write a rule and explore costs, drawdown and fictional challenge limits in an interactive example.Quant · Start hereQuant trading for beginners: from idea to backtestDefine a testable rule, choose suitable data and evaluate later periods after costs.Order flow · HubOrder flow trading: the complete guideThe hub. What order flow is, what it shows — aggression, delta, imbalance, absorption, liquidity — and the tools that read it, each linked to a full guide.