Learn how Operator turns manual decisions or authorized entry, stop, and exit signals into trader-defined actions, managed locally through NinjaTrader.
Operator is not a trading strategy or a signal provider. It is the software layer between the trade you want to take and the execution rules you want followed. Whether the entry starts with you or a connected source, Operator applies the selected plan and manages supported orders through NinjaTrader.
Trade execution is more than choosing buy or sell. Position size, target placement, stop behavior, timing, and risk limits all need to work together when a trade is active.
Operator lets a trader configure that structure ahead of time, then handles supported order and position-management actions while keeping manual oversight available.
Reusable profiles keep the chosen execution and management settings together rather than rebuilding the trade plan at every entry.
Targets, stops, breakeven and trailing are governed by the configured rules and verified broker state.
Traders choose their entry method, settings, permitted risk, and manual actions. Operator does not choose a strategy for them.
Traders can initiate positions from the dashboard or connect supported signal sources. Authorized sources may do more than open trades: independently permitted ENTRY, STOP and EXIT instructions can operate within Operator’s execution and risk policies.
See a setup you want to trade? Use Operator's dashboard to submit the trade intent with your selected account, instrument and execution profile. Operator handles the supported order workflow and subsequent management rules.
Connect a compatible, authorized signal source for entries, stop changes, and position exits. Each action requires the corresponding source permission and policy checks; Operator never treats a signal as proof an order was filled.
Open a permitted long or short position under the assigned execution profile.
Supply an initial stop or request an allowed protective-stop update.
Request an authorized exit independently of price-based target or stop orders.
ENTRY creates trade intent; STOP supplies or updates permitted protective-stop instructions; EXIT requests a position close or flatten action. Profit targets and automated management remain governed by Operator profiles. Compatible sources only.
A position can take partial profit without reaching every planned target. This example follows a long trade through a confirmed T1 exit, a configured breakeven stop adjustment, and a later stop exit on the remainder. Each action depends on actual NinjaTrader order state—not what a chart appears to show.
Validate account, instrument, sizing, source authorization and applicable session rules.
Route permitted orders through the Operator client and NinjaTrader AddOn.
Apply configured protective and profit-taking orders against verified execution state.
Adjust protection, manage targets or process a permitted manual or signal-driven EXIT as broker state changes.
Operator's capabilities work together through execution profiles and account policies. These are the categories traders configure—not simulated screenshots of the dashboard.
Specify where and how much to trade before a financial order is attempted.
Select the eligible NinjaTrader account and futures instrument for the session.
Define long or short trade intent and the configured position size.
Distribute contracts across T1, T2, T3 and a runner where configured.
Set the position's planned exits and downside protection as part of the execution profile.
Configure staged profit objectives with their assigned contract quantities.
Define the protective stop parameters applied to supported entry workflows.
Leave an allocated portion for continued management when the profile calls for it.
Choose how the management plan responds as a position progresses.
Move protection toward the entry reference when defined conditions are satisfied.
Update protective order levels under the configured trailing policy.
Monitor position status and submit permitted manual actions while the plan is active.
Set boundaries that constrain when and how Operator can act.
Apply configured session restrictions and permitted trading windows.
Use configured limits and auto-stop conditions to restrict supported actions.
When ownership, authorization or execution state cannot be established, Operator must not assume a trade is safe to execute.
Available controls and their exact behavior depend on the deployed Operator version and configuration. This illustration explains setting categories, not an active customer account or a verified production execution.
