Learn the basics, explore the controls and practise on a demo account. This public guide explains the documented reference tools and their limits; it is not a customer-package release.
MT4 reference / development tools · MT5 in development · No approved customer package yet
Sentinel is for people learning to plan and manage their own trades, as well as experienced traders who want configurable tools.
Before using trading controls, learn how orders, stop-loss levels, lot size, trading costs and margin work. You need to choose your own trade and understand that losses can exceed your planned risk. Start with Trading basics and a broker demo account.
See the five steps
A demo trade, in five deliberate steps.
This sequence describes the documented MT4 planning and management references. Order submission and management still need acceptance in the exact customer build; the current MT5 rebuild is not qualified for this complete walkthrough.
01
Choose your own trade
You choose the instrument and whether to buy or sell. Sentinel does not supply signals or make that decision for you.
Review the account, direction, volume and stop/target levels, then deliberately request submission in the supported build. Check the broker result; a click is not a fill.
Select the intended position and a supported breakeven, trailing-stop or partial-exit rule. Review what changed and keep the terminal running and connected for local automation.
Search words, control names or questions. Results include matching terms from the shared bilingual guide.
No matching topics. Try a shorter word or clear the search.
Quick start & practical controls
Before you beginQuick start
You need to understand buying and selling, order volume, planned exits, margin and trading costs. You should be able to find the broker’s contract specifications and tell a demo account from a live account. Trading experience can help, but neither experience nor software removes risk.
Use the public Trading basics and glossary first if these terms are unfamiliar. Product education explains how the tools work; it does not tell you which trades to take. Practise in a demo environment before considering a real-money action.
MT4 reference tools and separately tested development candidates are evidence for this guide. Their tested scope is not an approved customer release. MT5 is in development; the current partial rebuild has stability and connected-operation checks outstanding. It does not yet include every feature in the wider MT5 programme.
The fuller MT5 Risk Radar and Black Box capabilities described in this guide are outside the features restored in the current partial recovery build.
No approved customer desktop package has been designated. Do not treat historical screenshots, a higher version number or a menu label as availability. Android is coming soon and uses a separate connected architecture. cTrader is planned. Check the feature-specific status alongside each topic.
Installation: prepare, then follow the identified packageQuick start
The desktop EA runs in a MetaTrader terminal. Identify the intended platform, demo account, broker server and terminal data folder before any installation. “EA” means Expert Advisor: a program attached to a terminal chart. A manager indicator must match its controller; do not mix components from different packages.
Customer file names, download, installer steps, permission requirements and acceptance are awaiting owner confirmation. This guide supplies no installer or invitation to install a development build. When a package is approved, its exact installation and rollback instructions must be added and tested. Do not overwrite an existing setup or loosen security settings to resolve a warning.
Risk amount, percentage and fixed lotsControls & feature scope
The MT4 planning reference has three distinct sizing modes. Fixed lots use the volume you enter. Cash-risk mode uses your entered amount in account currency. Percentage-risk mode converts your chosen percentage of the configured balance/equity basis into a cash budget.
In risk modes, the calculation uses the planned entry-to-stop distance and the instrument’s tick value/size, then rounds volume down to the broker lot grid. If volume is below the minimum or the plan is invalid, review the reason instead of forcing a trade. Changing the stop distance with the same cash budget generally changes the calculated volume; rounding means it need not change by an exact proportion.
The reference calculation is a price-distance estimate, not a maximum-loss guarantee or an all-in cost promise. Spread, commissions, financing, changing values, gaps and execution can change the outcome. Customer input amounts and defaults are not yet confirmed.
Entry, stop-loss, take-profit and unitsControls & feature scope
Entry is the planned opening price. Stop-loss is your chosen exit instruction if price moves against the trade; take-profit is an exit instruction at a chosen target. Review the trade direction and that the prices sit on the appropriate sides of entry. Prices and distances are different inputs.
A broker point is the instrument’s smallest displayed price unit; it is not always a pip. Check digits, tick size, minimum lot, lot step and minimum stop distance in contract specifications. The MT4 reference normalises prices and validates direction/geometry. Unsupported levels can be blocked.
On-chart planning lines prepare a plan; dragging, deploying or staging them does not itself send an order. Some MT5 development placement tools offer Static/Relative targets and ATR/swing stop previews. Those placement controls are not automatic trailing of an open position. Stops do not guarantee an exact exit price.
Your first demo order: review before submissionQuick start
After an identified build is approved for demo execution, choose the instrument/direction yourself. Set entry, stop, target and cash-risk amount; inspect volume, estimated risk, margin and any warning. Review the current account and broker connection. Do not use this website to place trades.
Make the submission decision yourself in the supported terminal control. Market orders request execution now; limit/stop orders are instructions for specified future price conditions. The precise confirmation gesture and enabled order types depend on the build and need capture in the intended customer package.
Read the reported result and check the terminal’s order/position record. Acknowledgement, fill and open position are different. If the result is uncertain, inspect the broker record before repeating the action. Connected positive execution has not been established for the present MT5 rebuild.
Drafts, deployment, arming and saved plansControls & feature scope
A draft stores preparation. Deployment displays planning objects. In the MT4 planning candidate, arming is a deliberate one-shot state tied to the exact plan/context and expiry; it is invalidated by relevant edits and is not restored as armed after a restart. An armed local setup is not the same as a broker-held pending order.
Before any later action, inspect account, symbol, plan revision, stop/target and supported policy. Saved profiles and similarly named MT4/MT5 policies are not interchangeable. Which saved plan controls are exposed in the customer package remains to be confirmed.
Choose the position and action scope firstControls & feature scope
Select the intended position and verify its account, symbol, side and volume before applying a management rule. The MT4 management reference has selected-position controls and broader side/scope controls. If no tickets are selected, some side actions use their configured fallback scope; they are not necessarily limited to one trade.
Manual breakeven, partial close, close, delete, reverse and hedge controls can have materially different effects. Review the exact affected scope and requested volume. Do not experiment with batch actions on a real account. The matched MT5 manager must not be mixed with a different controller. Available controls vary by build.
In the inspected MT4 action reference, Close requests closing eligible open volume; Delete cancels eligible pending orders. Neither is a pause button. Reverse first closes eligible net volume, then requests an opposite order; the second request can fail after the close has happened.
Hedge requests an opposite order without first closing the original trades, where the account and broker permit it. X2 requests additional volume in the dominant direction, based on eligible net volume and the selected fraction; it does not simply double every position. These actions can add costs, margin use and risk. Check the selected scope and each broker result. Their exact customer screen labels and connected behaviour still need acceptance.
Breakeven: a stop request, not a guaranteed resultControls & feature scope
In the MT4 management reference, Standard automatic breakeven uses the recorded original entry-to-stop distance. Its reference trigger is 1.618 times that distance in a favourable move. This is a build-specific default, not a recommended target or a probability. One R refers to the recorded original planned risk.
The reference requests a stop near entry with an adjustment using current spread, available commission/swap and any extra points. It avoids worsening an existing better stop and checks broker constraints. “Breakeven now” is a separate manual action; strategy mode has its own configured trigger/lock pairs.
Confirm the selected mode and the stop accepted in the terminal. A rejected or unconfirmed request is not protection. Future costs, gaps, slippage and execution can still leave a loss. The present MT5 partial rebuild has not passed connected rule/adoption acceptance; do not transfer these MT4 defaults to it.
The MT4 management candidate includes fixed-distance, step and R-based trailing paths, with ATR and swing/structure paths also present and deterministically checked. These choices are different rules; use the selected build’s mode, distance, activation and timeframe rather than assuming a generic trailing function.
Fixed distance uses broker points from the current quote after activation. Step mode changes the candidate stop in configured steps. R mode uses the recorded original risk distance. ATR means Average True Range, a measure of recent price range; the ATR/swing paths depend on their reference timeframe and available bars.
Local trailing needs the EA and terminal running with current data and usable trading permission/connection. A new stop request can be rejected; inspect the accepted level. A trailing rule does not guarantee a fill, prevent every loss or act as a server-hosted strategy. MT5 mode names and defaults require their own validation.
Partial exits and what remainsControls & feature scope
A partial exit requests closing part of an open position. In the MT4 management reference, the close volume and remaining volume must fit the broker’s lot step/minimum. A small position may not support a partial close; the helper refuses an unintended full close.
In the inspected manual/Standard path, the 0.618 setting requests closing 61.8% before broker rounding. It does not mean 61.8% must remain. The reference input’s name is ambiguous, so the customer-facing label and default need confirmation. Standard and strategy partials use different trigger/step rules.
After a partial close, confirm actual remaining volume and the broker’s position/ticket record. The candidate conservatively reconciles a successor ticket; ambiguous identity is not treated as successful ownership. Actual customer broker behaviour still needs qualification.
Pause, resume and uncertain outcomesControls & feature scope
Pause/resume affects automation, not whether an open position exists. The MT4 management candidate’s pause/resume state requires revalidation on resume; an unresolved action after restart is held for reconciliation rather than silently repeated.
A pause is not a close order and does not remove the position’s market risk. Check broker-held levels separately. If the panel reports stale, failed or uncertain state, compare the broker record and retain evidence for support. Do not delete journals or repeatedly click to bypass a block.
Terminal, VPS and disconnectionAdvanced & limitations
The inspected MT4 automation is executed by EA callbacks in the running desktop terminal. If that terminal is stopped, it cannot calculate and send new management requests. If quotes or the broker connection are unavailable, do not assume a trigger has been evaluated or a stop change has been accepted. A VPS is a continuously running remote computer, not automatic broker-side protection.
MetaTrader distinguishes broker-held stop/target orders from local automation. Check that the broker has actually accepted the levels; a drawn or virtual/stealth level is not that evidence. Exact reconnect, stale-trigger handling, restart adoption and licence-expiry behaviour for a customer package are awaiting confirmation. No seamless catch-up promise is made.
The forthcoming Android app has separate backend, computer/VPS, MT4 terminal and App EA dependencies. It is not a phone replacement for the desktop EA. Connected availability, offline actions and background delivery must be checked separately.
When a control does not do what you expectQuick start
Size missing or too small: check entry/stop, tick value, lot step/minimum, quotes and account context. Stop rejected: check direction, current price and broker stop/freeze distances. No management change: check the intended position, mode, trigger, pause state, terminal connection and accepted broker level.
An uncertain submission needs broker-record review before another request. An unresponsive MT5 development panel or mismatched manager needs support, not continued clicking. Report the platform/build, action, visible message and an appropriately redacted screenshot. Never include broker passwords in an enquiry.
Customer error-code mapping, exact installation errors and reconnect troubleshooting still need the identified package. The guide names known conditions without inventing a universal fix.
Reference defaults and unitsAdvanced & limitations
These values are read from the frozen MT4 management candidate, not from an approved customer package and not from MT5. They explain the reference implementation, not settings we recommend. Saved state may differ; inspect the selected trade’s actual rule.
Source: MT4 development reference 260920-F05, dated 20 September 2026. The exact customer build must have its own verified values.
Control
Reference value / unit
Percentage-risk account basis
Equity by default; balance is configurable
Standard breakeven trigger
1.618 × recorded original risk distance
Extra breakeven offset
0 broker points (spread/cost adjustment is separate)
Standard partial trigger
1.618 × recorded original risk distance
Manual/Standard partial fraction
0.618 requested to CLOSE before broker rounding; customer label needs confirmation
ATR period / multiplier
14 bars / 1.0
Swing lookback
1500 bars; sufficient history is required
Fixed / step trailing distance
250 / 100 broker points
Fixed/step/R activation
1.0 × original risk distance where recorded
R trailing lock
0.5 × original risk distance
Trailing reference timeframe
0: no explicit timeframe override; reference resolves from trade/chart context
Quote freshness / plan-arm expiry
15 seconds / 300 seconds
Clearance / override expiry
15 seconds / 120 seconds; build-specific, not a universal permission
What the evidence establishes — and what it does notAdvanced & limitations
Development checks establish selected calculation and control paths. Historical screenshots show visible controls; neither is proof of an approved customer release or every broker response.
The exact customer package, installation acceptance, confirmation gestures, connected execution and management, supported account modes, restart/reconnect and privacy/licensing behaviour still need confirmation. MT5 stability work remains a separate project. No video is recorded from a known unstable build, and no empty player is published.
Essential learning stays public. The closed Academy/member routes are not opened by this guide; future member learning is not presented as available.
Whether you’re just starting to learn about trading or already have years of experience, Sentinel brings trade planning, supported trade-management tools and account information together beside your chart. The wider development programme also includes tools for reviewing your trades.
Stay close to the chart while working through the trade. Sentinel’s native panels bring planning, account context and supported trading controls into the terminal, with dedicated views for managing positions and reviewing their history. The broader MT5 workflow is being developed around a shared plan, so the intent behind an entry can remain connected to its management policy and later review.
The MT4 reference also includes chart-scoped settings export/import, chart hide/restore and organisation controls, and optional hotkeys that are off by default. Settings checks and hotkey support belong to that build; they do not grant trading authority or establish MT5 parity.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Augmented Trader web cockpitControls & feature scope
Web cockpit in development · Connected adapter required
Web Preflight is a preview of the displayed checks, not final execution clearance. Queuing or acknowledging a command does not confirm that the broker has executed it.
Work from a connected web cockpit.
Augmented Trader brings Trade, Manage, Setups and Preflight into a responsive browser workspace, using the capabilities exposed by its connected adapter.
Augmented Trader is Sentinel’s responsive web cockpit. Its chart-led Trade, Manage, Setups and Preflight views bring the core workflow into a remote workspace: inspect the market, prepare a setup, review the checks and use the controls supported by the connected system. It gives Sentinel another surface to work from, while execution remains dependent on the backend, trading terminal and the capabilities exposed by the relevant adapter.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Account identity and readinessControls & feature scope
Native and web development
Know which account your decision belongs to.
Account-bound plans and readiness information keep symbol, permissions and quote freshness attached to the intended destination.
Know which account and market you are working with before a draft becomes an action. Account-bound settings and plans help keep context attached to the intended destination, while readiness information surfaces issues such as stale quotes or unavailable trading permissions. This matters when you change charts, reconnect or work across accounts: the workspace should make the current context visible before you rely on it.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Broker-aware planning and sizingControls & feature scope
Start with lots, a cash amount or percentage risk. Review the resulting size, protection, reward and estimated margin against the broker’s instrument constraints.
Turn a risk decision into a plan you can inspect. Start from lots, a cash amount or a percentage of the account, then review the resulting size alongside entry, stop, targets, risk, reward and estimated margin. Broker constraints help shape the normalised plan, so its numbers can be checked before submission. That same planned intent provides the starting point for clearance, execution and comparison with the eventual result.
The reference inventory also includes R (one unit of the trade’s recorded original planned cash risk) and monetary previews. Those calculations depend on instrument specifications and available cost evidence; no approximate web calculation is presented as equivalent to a broker valuation. The MT4 reference also offers multi-target spacing and volume distribution. Per-target broker minimums and partial outcomes still matter; a target weight is not a success probability.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
On-chart entry and target planningControls & feature scope
Native tools · Build dependent
Put the plan where you can see it.
Place and adjust entry, stop and target levels on the chart. Supported builds keep their values aligned and allow independent locks and retraction.
Work with entry, stop loss and take profit levels where the decision happens: on the chart. Supported builds let you place, move, inspect, lock and retract planning levels, keeping the visual setup aligned with its numerical values. Independent locks help preserve a level you have already chosen while adjusting another part of the trade. These are planning controls; placing a line is a separate step from submitting an order.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Prepared setups and deliberate armingControls & feature scope
Setup slots separate saved drafts, prepared intent and armed setups. Broader MT5 development binds prepared intent to the account and symbol, with expiry.
Keep more than one idea ready without treating every draft as a live instruction. Setup slots preserve prepared intent, while preparing and arming separate an idea on the chart from a submission-ready setup. The MT5 development workflow binds saved setups to their account and symbol and gives armed intent an expiry. The visible prepared and armed states help keep preparation separate from commitment.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Profiles and Plan StudioControls & feature scope
Native development · Build dependent
Reuse the rules, with their meaning intact.
Named plans organise trailing, breakeven, partial exits and review. A visible policy revision distinguishes the selected rules from later edits.
Make a management approach repeatable without rebuilding it for every trade. Profiles and Plan Studio organise named, revisioned plans for trailing, breakeven, partial exits and review. Choose the policy, inspect its settings and identify the positions it should apply to. Keeping the policy revision visible helps distinguish the plan you meant to use from later edits, and provides a clearer handoff into position management.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Your manually chosen entries and deliberately armed setups feed the broader MT5 execution design through a common plan and clearance decision. Sentinel does not choose trades or supply trading signals.
Sentinel supports deliberate order placement from the trader’s own plan. The trader selects the instrument, direction, size, entry and stop/target levels. MT4 reference tools and broader MT5 development have different capabilities. In MT5 development, account context, plan review and checks precede a submission request; pending, partial, rejected and uncertain responses remain separate from confirmed broker execution. Sentinel does not select trades or supply trading signals.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Trade Clearance checks the plan and available account evidence, showing allowed, caution, reduced-size or blocked outcomes with reasons and expiry.
See the reasons behind an entry decision before adding exposure. Trade Clearance evaluates the available plan and account evidence and can return an allowed, caution, reduced-size or blocked outcome. It keeps the relevant reasons, plan revision and expiry alongside that decision, so a changed setup does not quietly reuse an old answer. A missing required input can block entry; clearance is a rule check, never a prediction that a trade will succeed.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Submission tracking and broker reconciliationControls & feature scope
Pending, partial, rejected and uncertain results remain distinct. Reconciliation and duplicate-prevention work check broker evidence before treating the request as complete.
An order request and a confirmed broker outcome are different events. Sentinel’s execution workflow tracks pending, partial, rejected and uncertain results, with recovery and duplicate-prevention controls designed to prevent a casual retry from becoming a second trade. Reconciliation checks what the broker actually reports before the workflow moves on. This makes uncertainty visible when connections or responses are interrupted, instead of presenting an unconfirmed request as completed.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Management that preserves the original policyControls & feature scope
Keep the position connected to the rules you chose.
Assign a management policy to the position instead of letting later chart defaults silently rewrite it. Broader MT5 development preserves the chosen policy through the trade.
Keep the position connected to the rules chosen for it. The MT5 management design preserves its assigned policy, so changing a chart default does not silently rewrite an existing trade’s management approach. Review the position and policy together, then make supported changes deliberately. This keeps the management approach understandable when several trades use different rules or a position remains open while you prepare the next setup.
Supported native reference/development policies include deliberate Pause/Resume. Pausing a management policy is separate from switching manual execution off, and does not close an existing position.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Breakeven and trailing choicesControls & feature scope
Native management · Choices vary by build
Express how the stop should respond.
Independent breakeven and fixed, step, original-risk, closed-bar Average True Range (ATR), a measure of recent price-range size, and candle-structure trailing provide different ways to describe the management approach in MT5 development.
Choose how the stop should respond as a trade develops. The MT5 development set includes independent breakeven rules and fixed, step, original-risk, closed-bar ATR and candle-structure trailing approaches. These give different ways to express the management idea, from a measured distance to a rule based on market structure. Select the method and parameters appropriate to the plan, then inspect how that policy is applied to the position.
A preserved MT5 reference uses a Standard stop-ratchet policy capped at entry, with its own partial-exit rules. Similarly named MT4 and MT5 modes must be checked against their specific build rather than assumed to behave identically.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Partial exits at chosen steps and runnersControls & feature scope
Native management · Build dependent
Plan the exits and what remains.
MT5 development partial exits at chosen steps refer to the original position volume and reserve a defined runner, keeping the intended exit distribution understandable.
Plan how much of a position to close at each stage and how much to leave running. Partial exits at chosen steps use the original position volume as their reference in the MT5 development workflow, with a reserve for the runner. This makes the intended distribution of exits easier to understand as the position changes. You can review the balance between taking profit along the way and keeping a defined portion exposed to the rest of the move.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Position and batch controlsControls & feature scope
Native and connected controls · Capability dependent
See the scope before requesting an action.
Supported ticket, symbol, strategy and account controls identify the affected positions and volume before applicable close, delete or other requests.
Act on a single position or a clearly defined group. Supported controls can work at ticket, symbol, strategy or account scope, with a preview of the affected positions and volume before applicable close, delete or other actions. Confirm the intended scope and check the reported result. Account-mode restrictions and uncertain outcomes remain relevant, especially when several positions are involved or an action is routed through a remote connection.
Some native reference/development variants include reverse and hedge actions. Account mode and the actually exposed controls determine their availability; the current chart captures do not demonstrate those operations. MT4-specific reference tools include manual-trade takeover, selected-trade level adjustment and pending-order workflows. They are separate from the compact MT5 control set.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Use the paired Trade Manager to select trades, inspect their state and request a policy change without losing the link to the underlying trading engine. The interface identifies the target, requests the selected policy and presents the acknowledgement and available review data. That visible request-and-result relationship helps you distinguish an intended change from one the EA has actually accepted, keeping management decisions traceable to the position.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
This fuller MT5 Risk Radar description belongs to the wider development programme. These capabilities are outside the features restored in the current partial recovery build.
See how the next idea fits the exposure already on the account. Risk Radar brings together account heat, unprotected exposure, concentration, correlation and margin pressure, with scenario views for considering a proposed trade. It is an observation tool: the useful question is what the account picture looks like under the stated assumptions. Missing data and unavailable measures stay visible so an incomplete picture does not become false precision.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Prop Guard and Challenge ModeControls & feature scope
Configured challenge rules bring targets, limits and remaining room into entry review. Reset time and calculation basis must match the actual programme terms.
Keep declared challenge rules beside the trading decisions they affect. Prop Guard and Challenge Mode track configured targets, limits and remaining room, helping you review whether another entry fits the selected programme rules. The reset time and calculation basis matter as much as the headline limit, so the account must be configured against the actual provider’s terms. Monitoring can support discipline; it cannot guarantee a challenge pass or provider compliance.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Personal account oversightControls & feature scope
Supported risk and analytics views put exposure, drawdown context, margin pressure and recorded performance beside your personal limits and goals.
Give a personal account the same attention you give a challenge account. Use the supported risk and analytics views to inspect exposure, drawdown context, margin pressure and recorded performance, then compare that picture with your own trading limits and goals. The value is a clearer view of what is already at stake before you add another position.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Alerts and connection awarenessControls & feature scope
Native alert tools · Delivery varies by platform
Know when the workspace needs attention.
Alert history separates acknowledgement, delivery failures, quote freshness and connection or recovery incidents. Routes and event types depend on the native build.
Keep operational changes within view while you trade. Sentinel’s alert and awareness work brings together acknowledgements, delivery failures, quote freshness and connection or recovery incidents, helping explain when a control or data point needs attention. Delivery options depend on the terminal and build. A terminal alert, email or push route has its own setup and limitations; the developing Android app has a separate local-notification mechanism.
Reference alert families include configured money, margin, session, news, custom-condition and trade events. Event support and delivery routes are build-specific; a local acknowledgement does not establish external delivery.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
News flags and chart contextControls & feature scope
Native development · Feed dependent
Keep event timing beside the setup.
Feed-dependent flags, cards and zones bring available news information into chart and planning context, with source and freshness remaining important.
Keep relevant event timing close to the market you are examining. News flags, cards and zones place available event information beside chart and planning context, so you can consider the timing and stated impact before committing to a setup. The usefulness of the view depends on its source, freshness and build support. Treat an unavailable or stale feed as missing context rather than evidence that the calendar is clear.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
The separate MT5 Advanced News Interpreter explains results against expectations, revisions, conditional scenarios and usable historical context. Sentinel integration is planned.
Understand more of the story around a release. The Advanced News Interpreter is designed to explain actual results against expectations, revisions, potential scenarios and usable historical context, helping you ask better questions about the event behind a price move. The interpreter is being developed as a separate MT5 tool; bringing that intelligence into Sentinel remains planned. Its analysis would add context to review, rather than a guaranteed market direction or an automatically executable signal.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Candle inspection and ObservatoryControls & feature scope
Candle selection, inspection of open, high, low and close (OHLC) prices and contextual metrics help you examine a move. Observatory gives that research a dedicated view. Integration with Sentinel is being developed in phases.
Look closely at the candle behind a decision. Candle selection, hover inspection, navigation, OHLC values and contextual metrics help you examine a move without reducing it to a single visual impression. Observatory brings that inspection into a dedicated chart-research view. Integration with Sentinel is being developed in phases. The available inspection views depend on the component and build.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Sessions and higher-timeframe contextControls & feature scope
Session windows and higher-timeframe lenses relate the current chart to a parent candle or a wider trading period.
Read a setup in its surrounding market context. Session views and higher-timeframe lenses help relate the current chart to a parent candle or a relevant trading window, making it easier to inspect where a move sits within a broader structure. Choose the context appropriate to the question you are researching and keep it alongside the chart. That wider view helps you examine the same setup through both its immediate movement and its surrounding session or candle.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Drawing tools and Scenario PathControls & feature scope
Chart Interaction tools · Integration in development
Make the reasoning visible on the chart.
Lines, rays, zones, channels, triangles and Scenario Path express levels and possible paths in the separate Chart Interaction work.
Map the idea before deciding what to do with it. Lines, rays, zones, channels, triangles and Scenario Path give different ways to express levels and possible price paths on the chart. You can inspect and adjust the visual reasoning rather than leaving it in a separate note. Integration is being developed in phases. An illustrative scenario remains separate from an armed trading setup, leaving you in control of when research becomes a trading decision.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Smart objects and Object ManagerControls & feature scope
The Chart Interaction component gives objects roles, revisions and lifecycle state, with Inspector and Object Manager for organisation and visibility.
Give chart work enough structure to remain useful after the first drawing. Smart objects add identity, role and revision to a chart object, while Inspector and Object Manager support inspection, grouping, visibility and lifecycle actions such as archiving. This helps organise a busy chart and retain the meaning of a level as it changes. Sentinel’s Object Manager integration is currently deferred. In the separate Chart Interaction component, that persistent identity provides a foundation for connecting chart context to later review.
The proposed object-to-plan reference can carry a level’s identity and revision toward planning. Its recorded contract is local preparation only; a working Panel transport, consumer and confirmed handoff are not established.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Object alerts and lifecycle eventsControls & feature scope
Chart Interaction component · Integration in development
Follow what happens to the level you marked.
Supported object conditions describe touches, breaks, closes beyond levels and time events, retaining the object’s identity and event record.
Follow what happens to an important level after you mark it. Object alerts can describe events such as a touch, break, close beyond a level or time condition, with rearming and persistent event records in the component design. The useful connection is between the specific object, its condition and the event that occurred.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Fib Volume ProfileControls & feature scope
Chart Interaction tools · Integration planned
Read the profile with its source in view.
Fib Volume Profile adds source-labelled activity levels to a Fibonacci study in the Chart Interaction tools. Sentinel integration is planned.
Add profile context to a Fibonacci-based chart study. Fib Volume Profile provides source-labelled levels that help you inspect where the underlying data places activity within the selected research view. Read those levels alongside the source and calculation basis rather than assuming every profile describes the same market information. Tick or estimated volume must be interpreted as that data type; it is not a substitute for verified exchange order-flow data.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Fair value gap toolsControls & feature scope
Chart Interaction tools · Integration planned
Give gap research a record you can revisit.
Smart FVG work discovers candidate gaps and promotes supported areas into managed objects, preserving the relationship between the finding and the chart object.
Keep gap research organised as the chart develops. The Smart FVG work covers discovery and promotion into managed gap objects, bringing a candidate area into the same object-based inspection and lifecycle approach. That helps you revisit which gap was identified and how it is represented, rather than relying on an anonymous box. You can keep the identified area connected to the object you inspect as the chart changes.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Native MT4 analysis and replayControls & feature scope
MT4 reference tools
Inspect a setup one bar at a time.
MT4 reference analysis includes bar-stepped review, spread-adjusted levels, partial markers and Fibonacci tools.
Explore how a setup unfolds one bar at a time. The native MT4 analysis tools include bar-stepped review, spread-adjusted levels, partial markers and Fibonacci analysis, giving you a structured way to inspect a scenario before comparing it with real trading records. Control the progression and examine the levels as the chart advances. Replay is a research aid, and its representation of a setup should remain distinct from live broker execution.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Named MT4 conditions combine operand sources, comparisons, joins and timeframe choices so the rule can be inspected and reused.
Express a chart condition in a form you can inspect and reuse. The MT4 condition creator supports named conditions assembled from operand sources, comparisons, joins and timeframe choices. It helps make an idea explicit: what is being compared, on which timeframe, and how the parts relate. The current creator work is focused on MT4. Its place in the wider workflow is to make the rules behind an idea explicit before you decide how they should be tested or used.
The native MT4 alert/condition family includes joined AND/OR conditions, timeframe choices and reusable presets. A condition or notification is separate from an explicitly armed action; no matching MT5 builder is implied.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Separate Pattern Radar development supports scheduled pattern checks, chart navigation and recorded alerts for investigating configured candlestick observations.
Find candlestick observations worth a closer look. Pattern Radar supports scheduled checks, chart navigation and recorded alerts, helping you find and revisit the observations that match the configured scan. It belongs to the research stage of the Sentinel ecosystem, where a finding can be investigated before a plan is formed. Pattern Radar studies chart patterns; account exposure is the separate role of Risk Radar.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Sentinel indicatorsControls & feature scope
Separate development projects
Add a focused research lens.
Separate indicator projects provide studies with their own purpose, settings and platform scope alongside the planning workflow.
Add focused research views to the chart with Sentinel’s indicator work. Each indicator has its own purpose, settings and platform scope, so the useful starting point is the specific study you want to inspect and the build that supports it. These tools complement the broader planning and review workflow by providing additional chart context. Platform scope and integration are specific to each indicator project.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
The MT5 visual builder combines profiles, closed-bar rules and chart visualisation to make a strategy idea inspectable.
Turn a strategy idea into visual rules you can examine on closed bars. Strategy Lab combines rule building, profiles and chart visualisation, helping you see how the configured logic is represented before you consider further testing or implementation. It is a visual research tool at its current stage. Its visual output gives you material to inspect and develop further; live order execution is outside its current scope.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Playbook BuilderControls & feature scope
Separate local design prototype
Write the response to each scenario.
This separate prototype helps you map different scenarios, decide what should happen when a condition is met, and test the sequence without placing live trades.
Branching paths mean alternative next steps according to your conditions. In first-trigger behaviour, the first matching route can be selected and the other routes in that same step cancelled. Other steps remain independent. The current chart shows a simple sequence, rather than a complete map of every branch.
The prototype saves your design locally as JavaScript Object Notation (JSON), a text-based format for saving structured data. It stores the steps, conditions, possible responses, routes, next-step targets, labels, chart placement and selected step or route. Temporary dry-run state and logs are not saved with the design.
A dry run previews the configured sequence and proposed actions locally without sending live trade commands. It is not a historical backtest or proof of profitability. This is a separate design prototype; it has no live execution connection to Sentinel or a broker.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Generator Lab exports MQL4 code for inspection, compilation and qualification. MT5 generation remains planned.
Move a configured idea into editable source for further development. Generator Lab generates and exports MQL4 code, giving you something concrete to inspect, compile and qualify against the intended behaviour. The generated output still needs testing and review; an export is not certification that a strategy is correct or suitable for live use. MT5 generation remains planned.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
TradingView PlaybookControls & feature scope
Separate tool in development
Keep a manually configured plan in view.
The separate TradingView-oriented development tool gives a chart plan and its intended interpretation a defined research surface.
Review a manually configured plan in a TradingView-oriented workflow. TradingView Playbook gives that chart plan a defined place in the wider Sentinel research story, helping you keep the setup and its intended interpretation in view. Its current scope is the manually configured plan itself. Broker execution and account synchronisation are outside this tool’s established scope.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
This fuller MT5 Black Box description belongs to the wider development programme. These capabilities are outside the features restored in the current partial recovery build.
Review the trade with its original context.
Broader MT5 Black Box development connects plan and actual outcome with timeline, notes, classifications, snapshots and exports.
Keep the reasoning and the result in the same record. Black Box brings together the original plan, actual outcome, timeline, notes, classifications, snapshots and exports, helping you reconstruct what happened without relying on memory alone. Review where execution or management differed from the plan and attach the context that matters. Its value grows from the shared trade lineage: the entry decision and management history can inform the same post-trade review.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Development analytics group partial exits into trade episodes, with filters and qualified measures that rely on the available original-risk and cost evidence.
Review results at the level of a complete trade, including the exits and costs that can otherwise be scattered across records. The analytics work groups partial exits into trade episodes and provides filters and qualified measures based on the evidence available. Recorded net results help make costs visible, while risk-based metrics need reliable original-risk data. Where that foundation is missing, the review should show the limitation instead of inventing a precise comparison.
Broader MT5 development includes symbol, session, direction and risk-band breakdowns, net costs, counts and other qualified statistics alongside sample size. Realised R (results expressed relative to the trade’s recorded original planned cash risk) and excursion measures need reliable original risk and price-path evidence.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
MT5 development analysis distinguishes recorded net economics from estimates about spread, slippage or other execution effects.
Separate the economics recorded on the account from estimates about how execution affected them. Execution Quality is designed to make that distinction visible, so you can inspect booked results and estimated execution drag without treating both as equally certain. Incomplete evidence remains part of the picture. This gives the review a clearer basis for asking where costs arose and how much of the explanation is supported by the record.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
The development Recovery Centre checks settings and evidence stores, retains damaged records and prepares redacted diagnostics for supported troubleshooting.
Preserve the information needed to understand a problem. Recovery Centre checks settings and evidence stores, keeps damaged records available for investigation and prepares redacted diagnostics for supported troubleshooting. It belongs beside review because a broken or incomplete record affects what you can conclude from the history. Its recovery work concerns settings and evidence, keeping troubleshooting separate from broker actions.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
AcademyControls & feature scope
Web learning in development · Member access not open
Learn the workflow through practice.
Future member learning work includes structured lessons, progress, resuming activities and offline-learning support.
Build familiarity with the workflow through structured lessons and practice. Academy work includes learning progression, resuming an activity and offline-learning support, so a concept can be revisited as you work through the product. It connects product concepts with the planning, management and review activities you are learning to use. Web development has its own scope, and shared progression across native surfaces is not yet established.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Progress records and evidence handoffControls & feature scope
Future connected review · Integration in development
Keep the meaning attached to a record.
Future connected review work preserves original risk, costs, consent and record lineage as evidence moves between surfaces.
Carry enough context forward for a result to remain meaningful later. Progress and evidence-handoff work is intended to preserve original risk, costs, consent and record lineage as trading evidence moves toward review surfaces. That continuity would help explain what a result represents and where it came from. The connected review workflow is still in development, including the production synchronisation needed to move records between surfaces.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Result cards and return on marginControls & feature scope
Future review tools · Account feed work unfinished
See the calculation behind the result.
Future result cards use net profit divided by recorded entrymargin for return on margin, when that evidence exists.
Present a recorded result with its calculation basis visible. Result-card work includes return on margin calculated from net profit divided by the recorded entry margin, expressed as a percentage. This gives a specific view of an outcome when that margin evidence exists. Where entry margin is missing, the result is unavailable. Historical margin capture in actual-account feeds remains unfinished.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Member PWA and Follow TerminalControls & feature scope
Separate future surface · Outside the current launch
Separate learning and evidence from execution.
Future member Progressive Web App (PWA), a website with supported app-like behaviour, and read-only Follow Terminal work provide learning and supported records with freshness states.
The member PWA work explores an installable evidence and learning surface, while Follow Terminal presents read-only terminal information with freshness states. Together, they offer a future place to inspect supported records and learning material without implying control of the trading terminal. This is separate from the native Android app and remains outside the current launch. Read the freshness labels alongside terminal information so you know what the view can support.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Product education and technical supportControls & feature scope
Product education · Technical support scope
Learn the controls. Keep the decisions yours.
Product education and technical support explain configuration, platform scope and software behaviour. They do not tell customers which trades to take.
Product education explains how to configure and use Sentinel’s tools, understand platform and development labels, and inspect the responses to the trader’s chosen instructions. Technical support helps describe setup or software problems without requesting broker credentials or telling customers which trades to take. Member learning and connected support services remain in development; use the public contact page for product questions.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
cTrader expansionControls & feature scope
Planned
Extend the workflow to another platform.
cTrader is a planned addition to Sentinel’s platform family, with scope dependent on its implementation and qualification.
cTrader is a planned extension of Sentinel’s platform family. The aim is to bring the product’s connected workflow to another trading environment while respecting that platform’s own capabilities and integration requirements. Scope and availability will depend on the implementation and its qualification.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
See the connected accountControls & feature scope
Native Android in development
Keep the connected account within view.
Native Android development brings chart, market, account and position context through the backend, including freshness or unavailable states.
Bring chart, market, account and position context into a native mobile view. The app’s role is to help you inspect the connected system while you are away from the main workspace, with attention to whether the information is fresh or unavailable. That lets you judge the current view before relying on it. The displayed state comes through the backend, so its usefulness depends on the connected terminal and the data reaching the app.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
The current Android MT4 bridge covers development entry, sizing, target and management requests according to backend and terminal capabilities.
Use native controls to prepare or request the actions supported by the connected backend and terminal. Development work covers entry and sizing parameters, targets and management requests such as breakeven, trailing, partials and closes, with other actions dependent on the system’s capabilities. The important moment is the returned acknowledgement or updated snapshot. A tap on the phone starts a request; confirmation must come back from the connected trading system.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
Keep relevant changes in viewControls & feature scope
Local notifications in development
Notice relevant changes while using the app.
Local notifications in development surface supported account or position changes alongside the native interface.
Local notifications are being developed to draw your attention to supported changes while you are using the app. They give the mobile view another way to surface something worth checking, alongside the relevant account or position information. Background delivery is still unverified, so alerts while the app is closed are not promised.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
One connected Sentinel workflowControls & feature scope
Put the interface in your pocket, not the terminal.
The phone presents the interface, the backend routes requests and state, and the connected MT4 terminal and App EA perform supported execution and automation.
The phone handles the native interface, session and local notification presentation. The backend supplies state and routes commands. The desktop or VPStrading terminal and EA perform supported execution and automation, then return acknowledgements and snapshots. This division makes the app a companion within Sentinel’s workflow, with the connected system doing the trading work. The current Android bridge is MT4-specific. The behaviour of automation after closing the app is still being verified and should not be assumed.
Customer package and exact screen labels await owner confirmation. These explanations do not grant access or establish a released feature.
About this guide
Verified against identified Sentinel source and product records on 9 October 2026. Reference-only defaults are separated from current customer availability. General platform explanations use the linked MetaQuotes documentation. Installation acceptance, connected execution, reconnect behaviour and customer defaults are still open where noted.
Learn by watching — once the demos are verified.
Two short demos are being prepared: planning with a fixed risk budget, and managing a demo position with a chosen rule. We will add genuine recordings, captions and Thai narration after an identified build passes the relevant checks.
