Appearance
Are you an LLM? You can read better optimized documentation at /channels/settings-inheritance.md for this page in Markdown format
Settings Inheritance
You do not configure every channel from scratch. TTMT resolves the settings for each trade from just two places: the config profile attached to the channel, if any, and your settings for the account that channel trades on. The profile sits on top — every field it leaves on "inherit" falls through to your account settings.
The two layers
Every setting resolves the same way: the config profile's value if it overrides that field, or else your account setting.
- Layer 1 (top): the config profile assigned to this channel for this account. Any field the profile leaves on "inherit" falls through to the layer below.
- Layer 2 (base): your trading settings for the account this channel is assigned to.
There is no third layer. One important exception lives entirely on the account: risk limits are account-only — the daily-loss cap, the halt behavior, and the account-wide close-all are set on your account and a config profile never touches them. See Risk Limits.
The signal's own values — direction and symbol — are the trade itself; they always come from the provider's message. The signal's entry, stop loss, and take profits are used too, unless you've turned on an override for that value. Overrides are settings like any other: they resolve through the profile-then-account chain above.
- Stop loss — the signal's SL is used unless Override Signal SL is on. When it's on, your default SL replaces the provider's.
- Take profits — the signal's TPs are used (subject to your TP behavior) unless Override Signal TP is on. When it's on, your default TPs replace the provider's.
- Entry zone — the signal's entry is used unless Override Signal Entry Zone is on.
- Missing or invalid values — if a signal arrives without an SL or TP, your defaults fill the gap; and TTMT's safety checks can still correct a value that's obviously wrong (a decimal-place typo, a stop on the wrong side of entry).
The signal is used unless you override it
The provider's SL and TP are what trade — that's the default. But an override you've enabled, or a missing/invalid value your defaults and safety checks fill in, can change them. There's no "the signal always wins" rule: there's always an override or a validator that can step in.
What lives in each layer
Layer 2 — account settings. Position sizing, entry layers, TP strategy, breakeven, trailing, override modes, and risk — everything on the /dashboard/settings/sizing, /entries, /management, /strategy, /risk, and /trading pages, set per account.
Layer 1 — config profile. A profile can override any of those same fields for one channel. Fields left on "inherit" use the account value instead.
The channel's own SL/TP-default pips (set on the channel SL/TP tab) feed in as the asset-class fallback when a signal omits its levels — they are not a separate layer (see Per-asset SL/TP defaults below).
Per-account settings: one set per account
Each MetaTrader account you connect gets its own copy of the trading settings. Your demo and your live account can run different lot sizes, risk, and defaults at the same time. A new account starts from your global defaults, and you tune it from there.
This is why the channel's Config Profile selector reads "for [account name]" when you have more than one account — the profile attaches to a channel-account pair, not the channel alone. For more on why settings are stored per account, see Multi-Account Management.
Profiles attach per account
With multiple accounts, the profile you pick on a channel's Execution tab applies to the account shown ("for Pepperstone-Live"). Set it separately on each account where you trade that channel.
Config profiles: inherit vs override
A config profile is a named bundle of overrides you attach to a channel. Every field in it is in one of two states:
- Inherit — uses your account value for that field.
- Override — uses the profile's own value.
That's the whole model — there is no third "disabled" state. The channel Execution tab shows a live count like "7 settings customized" so you can see at a glance how far a profile diverges from your account baseline. Rather than memorize a setting count, read that indicator.
Changing a channel's profile takes effect on that channel's new signals immediately. Trades already open are a more nuanced story: TTMT can't retroactively rebuild a position's entry sizing, layers, or order placement, but some ongoing management — breakeven, redistribution, modifications, closes — reads the channel's currently assigned profile as it runs, so parts of an open trade's behavior can shift. Per-trade P&L limits are the exception: they're snapshotted when the trade opens and stay fixed for that trade. To build and attach profiles, see Creating Profiles and Applying Profiles.
One profile, many channels
Assign the same profile to every channel that shares a style — all your gold scalpers, for instance — so you tune them in one place. Change the profile once and every channel using it updates.
Per-asset SL/TP defaults (a fallback, not a layer)
When a signal arrives without a stop loss or take profit, TTMT fills it from your default pip distances. Those defaults are stored per asset class — forex majors, forex minors, metals, indices, crypto — so gold can default to a wider stop than EURUSD.
This is which default value gets picked for that symbol. It is not an extra resolution layer, and it does not override your profile or the signal's own levels. A metals signal with no SL uses the metals default; a EURUSD signal with no SL uses the forex-major default — same account, different fallback, no layer involved.
See Per-Asset Overrides to set these, and the channel SL/TP tab to set them for a specific channel.
Don't confuse per-asset defaults with overrides
Per-asset pip defaults only decide the fallback SL/TP when a signal omits them. They do not override a config profile or a signal's own levels.
Blocked schedules resolve differently
Trading hours don't follow the two-layer inherit-or-override model. A schedule is a set of blocked windows — times TTMT will not trade — and TTMT decides whether a signal's arrival moment is blocked using these rules:
- Account and channel blocks combine by union. A signal is skipped if the moment it arrived falls inside a blocked window on the account schedule or the channel's Hours tab. Both add together — there's no "which one wins."
- A non-empty profile schedule takes over. If the config profile assigned to this channel has a schedule with at least one blocked window, that profile schedule is used exclusively for signals that use the profile — it replaces the account and channel blocks entirely.
- An empty profile schedule inherits. If the profile has no schedule windows, the account + channel union applies as normal.
- Each scope owns its own timezone. The account, channel, and profile schedules each carry their own timezone, so a "block the New York close" window means the same thing regardless of where you live.
- Blocked signals are skipped, not queued. A signal that lands in a blocked window is dropped — TTMT never holds it and replays it when the window ends.
A profile schedule replaces, it doesn't add
If you paint even one blocked window into a profile's schedule, that profile's schedule becomes the only schedule for channels using it — your account and channel blocked hours are ignored for those signals. Leave the profile schedule empty if you want it to inherit the account + channel blocks instead.
Working out why a trade used a setting
When a trade behaves unexpectedly, trace it in this order:
- Is this a signal value (SL, TP, entry) with an override enabled? If the provider gave a 25-pip SL and Override Signal SL is off, that 25-pip SL is used. If Override Signal SL is on, your default replaces it. Check the override before anything else.
- Does the channel have a config profile, and does it override the field? If yes, the profile value wins over your account setting for that field.
- Otherwise it's your account setting for the account this channel trades on.
- Risk limits and blocked hours are resolved separately — risk limits are account-only, and schedules follow the union/exclusive rules above.
To see when a setting last changed, open the channel History tab.
Ideal Settings & Trading Strategy
Scenario 1 — Capital-preservation trader, single account
Setup: New trader, one $5k live account, following two complete-signal forex channels.
Settings:
- Layers: 2 at account level (cautious fill; TTMT works out the order count per layer)
- Lot size: fixed 0.01 lots at account level
- TP strategy: Progressive (account level)
- Per-asset SL default: forex-major 25 pips, metals 300 pips
- Config profiles: none — both channels run pure account settings
- Breakeven: enabled at TP1 (account level)
Why: With one account and two similar channels, account settings alone are enough. No profiles means nothing to debug — every trade uses the same baseline.
Watch for: If one channel starts trading gold heavily, a single account-wide lot size may be too large for the wider gold stops.
Switch when: You want different sizing for one channel — that's the moment to create your first config profile (Scenario 2).
Scenario 2 — Moderate trader, per-channel profiles, single account
Setup: Experienced trader, one $50k live account, five channels of mixed styles (gold scalper, forex swing, indices).
Settings:
- Account baseline: 4 layers, Progressive TP, 0.05 lots, breakeven at TP1
- "Gold Tight" profile (on the gold scalper): override lot size to 0.02, override SL default to 200 pips, leave TP strategy on inherit
- "Indices Wide" profile (on the indices channel): override SL default to 500 pips, override layers to 2, leave everything else on inherit
- Forex swing channels: no profile (use the account baseline)
- Per-asset SL defaults still set at account level as the safety net
Why: The account is the sensible default; profiles touch only the one or two fields that differ per channel. Leaving most fields on inherit keeps the profiles small and readable (a low "settings customized" count).
Watch for: A profile that overrides too many fields drifts from your account baseline — when you later change the account default, that channel won't follow.
Switch when: You add a second account (demo or prop) and want a channel to behave differently there — move to Scenario 3.
Scenario 3 — Multi-account trader (demo + live + prop)
Setup: Trader running one channel across a demo account, a live account, and a prop-firm account.
Settings:
- Demo account settings: 0.10 lots, 6 layers, Extended TP — testing aggressively
- Live account settings: 0.02 lots, 2 layers, Progressive TP, breakeven at TP1
- Prop account settings: 0.01 lots, single layer, Progressive TP, tight breakeven
- Config profile: optional per account — e.g. a "Prop Safe" profile on the prop assignment that overrides lot size down further; demo and live run pure account settings
- Per-asset defaults tuned per account (the prop account uses the tightest fallbacks)
Why: Because settings are stored per account, the same channel automatically runs three different risk profiles — no need to clone the channel. Profiles are added only where a channel needs to diverge from that account's baseline.
Watch for: Forgetting that the Config Profile selector applies to the account currently shown — set the profile separately on each account where the channel runs.
Switch when: The prop account passes its challenge and converts to a funded live account — re-tune the prop account's baseline rather than touching the channel.
Related pages
- Channel Settings — assign a config profile, set channel SL/TP defaults, and paint blocked hours
- Creating Profiles — build a config profile of overrides
- Applying Profiles — attach a profile per channel-account
- Per-Asset Overrides — set the SL/TP fallback per asset class
- Risk Limits — the account-only daily-loss cap and halt behavior
- Multi-Account Management — why settings are stored per account

