2. Trading: Use Cases Use Case #1: Launching a New Trading Pair Ops adds a new instrument under Trading → Configurations . They pick the symbols group (e.g., Crypto), click + Add symbol , and set Active , Spread (pips) , Commission (pips) , Margin requirement (%) , Margin ratio (leverage) , Lot volume , Price precision , and Timezone . From that moment, margin checks, pricing, and calendar rules apply consistently to the pair, and it becomes available to Orders. Use Case #2: Scheduling Market Closures (Weekends/Holidays) Risk defines a recurring non-trading window under Weekends . They choose a base timestamp, set Repeat (week/month/year), and optional work hours. For instruments with their own Timezone , the closure is evaluated in that zone. During the window no ticks are published and no orders are accepted for the affected instruments. Use Case #3: Running a Controlled Price Simulation For a short demo or QA scenario, an admin opens Price deltas and clicks + Add . They select a symbol, set From/To , and enter a Pips offset (positive to push price up, negative to pull it down). While active, the venue shows and executes at the adjusted price. Chaining minute-long deltas produces stepwise ramps without touching fees or spreads. Use Case #4: Risk-Adjusting a Live Order A risk manager filters Orders to a client’s open market positions, opens Edit , and updates Stop loss and Take profit (and, if policy allows, Price/Quantity ). On save, validations enforce precision/step and re-check margin using the pair’s effective parameters (including any Trading Group overrides). The audit log records before/after values and the user. Use Case #5: VIP Segmentation with Trading Groups A client starts trading high notional daily. Ops goes to Trading groups to create a VIP group with Commission=0 and a higher Margin ratio , then assigns it to the client on Clients → Trading Groups . If the client later also needs a Watchlist group, ops adds it and drags the groups to set precedence. Resolution applies settings from the first group; missing fields cascade to the next group, then to the base pair configuration.