Does FTMO Ban Account Management?

Does FTMO ban account management? Start with the actual conduct

The safest short answer is that a trader should not let another person manage, access, or trade an FTMO account unless FTMO has clearly confirmed that the precise arrangement is permitted under the current rules for that account and stage. The phrase "account management" is too broad to answer by itself. It can refer to education, administrative help, software configuration, signal delivery, discretionary order entry, credential sharing, or full control by an outside operator. Those activities are materially different. What matters is who makes the trading decisions, who can cause an order to reach the account, who controls risk, and who holds the credentials.

FTMO publishes an official FAQ, Trading Objectives, and Terms and Conditions. Those three official sources are the factual starting point for this review. A visitor should read their current versions before acting because language, products, account stages, and linked documents can change after this page's verification date. This article does not claim that one isolated sentence settles every possible arrangement. It offers a method for matching the real activity to FTMO's current first-party wording and for asking support a useful question where the answer is not explicit.

Do not treat the word "ban" as an invitation to search for a technical workaround. If an outside service chooses trades, controls a remote session, enters orders, changes protective levels, or receives a password, the core concern is authorization and responsibility. Renaming that service as coaching, automation assistance, a challenge partner, or risk support does not change what it does. Conversely, ordinary education that leaves all account access and trading discretion with the named client is not factually identical to handing an account to a manager. The correct classification comes from conduct, not advertising language.

The compliance-first position is therefore simple. Keep credentials private, retain personal control, compare the proposed activity against the current FTMO documents, and request a written FTMO response before involving anybody whose role is uncertain. If FTMO does not approve the exact setup, do not proceed with it. If a vendor says approval is unnecessary, remember that the vendor cannot amend FTMO's agreement or speak for FTMO. A claimed history of successful accounts, screenshots, social posts, or informal community assurances would not establish permission even if genuine.

A useful first question

Before looking for a label, write one factual sentence: "The proposed third party will do the following actions." Include decision making, order entry, account viewing, remote access, software installation, and possession of recovery information. If the sentence reveals that another human can direct or operate the account, stop and obtain a first-party answer. If the role is limited to general instruction, still verify any uncertain feature rather than assuming that a broad category creates permission.

This distinction protects the quality of the support question. "Is account management allowed?" may produce a broad reply because the term is undefined in the question. A precise description gives FTMO the opportunity to address the actual workflow. The reader should identify the product, account stage, platform, tool, people involved, and the person who makes the final decision. Nothing should be concealed or softened to produce a preferred response.

How to read the FTMO sources without overclaiming

The official FAQ, Trading Objectives page, and Terms and Conditions serve different purposes. The FAQ may organize practical answers by topic. Trading Objectives describe measurable program requirements and should be consulted for the current account model. The Terms and Conditions set out contractual language and may refer to additional materials. A responsible review reads them together, follows relevant links, and checks the version applicable to the purchaser. No summary on this page replaces that reading.

Begin with the Terms and Conditions linked below. Confirm that the page applies to the service, region, and date in question. Search the document for provisions concerning client duties, access, third parties, prohibited conduct, account use, identity, credentials, trading activity, termination, and review. Those suggested search concepts are an organizational aid, not a claim that every current version uses each exact word. Read definitions and surrounding paragraphs rather than copying a fragment from search results.

Next, examine the current FAQ. Use its own navigation and search, because FTMO may move an answer or revise how subjects are grouped. Look for first-party explanations relevant to account operation, trading methods, platforms, verification, and support. An FAQ can clarify common situations, but a general answer about tools should not be stretched into approval for an outside human to exercise discretion. Similarly, an answer about technical access should not be detached from identity and client-responsibility provisions elsewhere.

Then read the current Trading Objectives for the selected product and stage. Account-management compliance does not replace objective compliance. The named trader remains responsible for understanding every applicable measure, including whichever loss, time, position, instrument, or trading restrictions the current official page specifies. This article intentionally does not restate numerical thresholds because they can vary or change. Verify all limits on FTMO's official page and in the purchased account materials before placing a trade.

Record the version you actually relied upon

Save a dated copy or PDF where permitted, note the URL, record the product name, and preserve the order confirmation or agreement supplied at purchase. A simple research note can identify which paragraphs seemed relevant and what remained unclear. This record is not a shield against a later rule or an individual determination. It is ordinary diligence that helps the client remember what was reviewed and formulate a direct question.

Pay attention to effective dates and amendment language. A web page checked today may not be the version associated with an earlier account, while an existing agreement may explain how updates are communicated or applied. Do not make a legal conclusion from that observation. If timing affects a real account, ask FTMO how the current rule applies and obtain qualified professional advice if a legal interpretation is needed. This page cannot interpret governing law or contractual enforceability.

Use first-party materials as a hierarchy of evidence over affiliate articles, videos, forums, cached snippets, and vendor sales pages. Third-party content can reveal a question worth asking, but it cannot authorize activity on FTMO's behalf. A search snippet may truncate a condition. A video may predate an update. A forum answer may concern another stage. A vendor may have a financial incentive to describe its service as acceptable. Those weaknesses make direct verification important even when many posts repeat the same claim.

Resolve apparent tension rather than choosing the convenient sentence

If one official page appears broad while another contains a qualification, do not select whichever passage supports the desired arrangement. Read the context, check whether the pages discuss different products or stages, and submit both links to FTMO support. Quote the relevant wording accurately, provide the date viewed, and ask how the provisions operate together for the proposed facts. A written, account-specific clarification is more useful than an interpretation assembled from disconnected phrases.

The verification date preserved in the sources for this article is August 28, 2026. That date communicates when the source list was set; it is not a promise that each page remains unchanged afterward. Readers arriving later must repeat the source review. Readers with an active account should also check notices inside their official dashboard and email because public pages may not reproduce every account-specific communication.

Separate education, assistance, software, and discretionary control

A sound account-management review separates roles before applying a rule. Start with education. A teacher can explain market concepts, demonstrate a general framework, discuss risk, or review historical examples without logging into the student's account or deciding the student's orders. That description alone does not establish that every educational relationship complies with FTMO, but it is meaningfully different from discretionary management. The student still needs to confirm that any connected activity follows current rules and remains personally controlled.

General market commentary is another category. A newsletter, public stream, or research service may present ideas to many readers. The account holder independently decides whether to act, selects the timing and size, and enters the order. Again, the label does not guarantee compliance. Current FTMO rules may address related conduct, coordinated trading, copying, or other methods in ways this general description cannot settle. The reader should compare the actual delivery and execution process with official wording rather than relying on the publisher's chosen name.

Administrative assistance can include calendar organization, bookkeeping, hardware support, or help locating a public document. Some tasks may occur without exposing platform access. Others can cross into sensitive territory if an assistant sees credentials, opens the trading environment, changes settings, or can influence execution. Define each permission narrowly. If a task would require account access, remote desktop control, identity material, or recovery credentials, pause and ask FTMO before allowing it.

Discretionary control exists in practical terms when another person determines whether, when, or how the account trades. Examples can include choosing an instrument, deciding direction, setting position size, approving entries, moving exits, or closing a position. This list explains the compliance question; it does not claim to quote FTMO's legal definition. A client proposing any such outside role should send the exact facts to FTMO and follow the current written answer.

Control can be shared even without a password handoff

A person does not need to know the permanent password to exercise practical control. A remote session, unattended connection, installed utility, linked execution service, delegated device, or active instruction channel might enable another person to cause account actions. This article will not discuss ways those arrangements are detected or obscured. The appropriate question is whether the arrangement is authorized, honestly described, secure, and consistent with the current rules. If another person can make the account act, disclose that capability in the support request.

Likewise, keeping the password while mechanically obeying a private operator's individualized commands may raise questions different from ordinary education. The exact treatment depends on FTMO's current language and the complete facts. Do not assume that clicking the final button personally settles who exercised trading discretion. Tell support who originates decisions, whether instructions are individualized, whether other clients receive the same activity, and whether execution occurs automatically or manually.

Use a role map

The map should reflect reality rather than a planned explanation. Do not omit a person's involvement because access is brief, unpaid, informal, or described as technical. A friend trading one session can still raise the same fundamental question of who operated the account. A commercial manager with polished contracts does not gain authority from professional presentation. Family relationships, employment relationships, and shared business ownership also do not automatically answer what FTMO permits for an individually identified account.

Where the role remains genuinely unclear, choose the conservative operational state: no third-party access and no outside discretion until FTMO responds. That approach avoids turning an unanswered question into an account event. It also gives the reader time to select a compliant alternative, such as general education, practice in a personally controlled environment, or a tool whose specific operation FTMO has confirmed for that account.

Credentials, identity, devices, IP questions, and truthful account control

Credential security is central because a login can expose more than a trading screen. Depending on the system and permissions, account access may reveal personal details, transaction history, platform settings, support communications, or pathways to further accounts. Never send a password, one-time code, recovery link, identity document, or mailbox access to an account-management seller. FTMO's current instructions should be checked for available security settings and the proper response to suspected compromise.

Use a unique password and protect the email account associated with the service. Enable security features offered through official channels where applicable. Keep recovery methods under the named client's control. Download software only from trusted official sources and review requested permissions. These are general security practices, not statements that a security measure changes FTMO's account-management rules. Strong authentication cannot make an unauthorized operator authorized.

If credentials have already been shared, do not attempt to disguise the event. End the outsider's access, secure associated accounts, preserve accurate records, and contact FTMO through an official channel for current instructions. Describe what happened, when it happened, which systems were involved, and what protective actions were taken. Do not delete or alter information in an effort to create a cleaner story. This article cannot predict how FTMO will evaluate a particular incident.

Identity remains distinct from technical connectivity

An IP address is a network fact, not a complete identity. Homes, offices, mobile carriers, hotels, and shared facilities can produce ordinary network patterns involving multiple people or changing addresses. At the same time, an ordinary explanation for connectivity does not grant permission for another person to trade an account. The compliance inquiry should remain focused on truthful identity, authorized operation, and any current FTMO requirements concerning locations, devices, or access.

Readers should never use network tools, remote systems, virtual machines, device changes, or hosting arrangements to make one operator appear to be another. This guide provides no instructions for concealment. If travel, relocation, shared premises, or infrastructure creates uncertainty, ask FTMO in advance where reasonably possible. State the legitimate reason, expected dates, account stage, and whether anyone else at the location has a relevant account. Follow the answer rather than trying to infer internal thresholds.

Expert advisers and automated tools deserve the same factual discipline. The fact that software is technically supported by a platform does not prove that every strategy, configuration, copying relationship, or deployment method satisfies FTMO's current rules. Read the official materials, describe the tool's function at a high level, and ask FTMO when necessary. Keep the explanation compliance-focused: who created decisions, where they are executed, whether activity is copied, and who can modify the system.

High-frequency trading is also an imprecise phrase. It can be used casually for active manual trading or technically for specialized automated behavior. Do not assume either a universal permission or a universal prohibition based on the label. Verify the current FTMO treatment of the actual strategy and all relevant prohibited practices. A support question should explain the intended behavior honestly without requesting detection thresholds, tolerated order counts, or methods for avoiding review.

Maintain an ordinary access record

A basic private record can include personally used devices, expected travel, authorized software, security changes, and dates of support contact. It should not be engineered to simulate legitimacy. Its purpose is to help the client notice unfamiliar access and answer a genuine inquiry accurately. Account statements, original emails, purchase receipts, and unedited support messages may also help establish a straightforward chronology if FTMO asks for information.

Do not collect excessive sensitive data merely to prepare for a hypothetical review. Store necessary records securely, observe applicable privacy duties, and avoid sending documents to unofficial contacts. Verify the destination before uploading identity information. If a supposed manager asks to take over the client's email account or identity-verification session, decline and consult FTMO. No commercial convenience justifies impersonation or misuse of another person's identity.

How to ask FTMO support for a decision you can follow

A useful support request is short, factual, and complete enough to classify. Begin by identifying the exact account product and stage. State whether the account is only being considered, is in an evaluation, or has moved to another stage, using the terminology shown in the current FTMO materials. Include the platform if it affects the proposed setup. Do not include passwords, identity files, or other secrets in an ordinary question unless an authenticated FTMO process specifically requests them.

Describe the proposed outside role in verbs. For example, explain whether the third party would view the screen, install software, supply general education, send individualized instructions, select positions, choose sizes, enter orders, change orders, or access the account remotely. Say who retains final discretion and who can technically cause execution. Mention whether the service will receive credentials, tokens, recovery access, email access, or device control. This detail is more informative than calling the provider an account manager or mentor.

Link the official page that created the question and quote only the relevant current passage. Ask whether the described arrangement complies with the rules for the identified account. If several activities are involved, separate them into numbered questions so an answer to one is not mistaken for approval of all. Request clarification where a response discusses only software but the proposal includes a human operator.

Sample wording for a legitimate clarification

I am considering the following arrangement for my identified FTMO product and stage. I will retain my credentials and make every final trading decision. An outside educator would provide general lessons but would not view, access, control, or trade the account. No remote session or automated execution would be used. Please confirm whether this exact arrangement is permitted under the current rules, and identify the applicable official provision.

That example is not a preapproval and should not be copied when the facts differ. If the provider will issue individualized directions, install a tool, access a screen, or influence execution, say so. A selectively incomplete request produces an answer to an imaginary setup, not the actual arrangement. Support correspondence is useful only when the question is truthful.

Questions that should raise concern

Do not ask how many access changes are tolerated, which technical indicators are reviewed, whether a small amount of managed trading will escape attention, or how to make a remote operator appear local. Those are bypass-oriented questions, not compliance questions. Ask whether the conduct is permitted. If the answer is no, change the conduct or do not use the service.

If the first response is ambiguous, reply in the same official thread. Restate the unanswered fact without arguing for the preferred result. A statement that a general tool category is supported may not answer whether a particular outside person can control that tool. A reference to personal responsibility may require further clarification about the exact role. Politely request a direct answer and retain the full exchange, including context and dates.

If separate support responses appear inconsistent, do not shop among agents for the most favorable sentence. Point out the difference, provide ticket references, and ask FTMO to clarify which instruction governs the account. Follow any formal escalation process FTMO currently provides. Do not publish a support worker's personal details or use public pressure as a substitute for the designated review route.

After the answer

Read the response narrowly. Approval of one described educational arrangement does not necessarily approve account access, copying, a different product, a later stage, or a modified service. Note assumptions and limitations. If the vendor changes its process, if new software is introduced, or if another person gains access, ask again. If FTMO refuses or conditions the activity, follow that result rather than looking for a semantic variation.

Keep the correspondence with the account records, but understand its limits. This article cannot say what contractual effect a support message has. The applicable agreement may contain provisions about official notices, amendments, and interpretation. Anyone needing a legal opinion about reliance, remedies, consumer rights, or a dispute should consult an appropriately qualified professional in the relevant jurisdiction. The practical value here is simpler: a written first-party answer is better evidence of current guidance than a vendor's promise.

Evaluate account managers, passing services, and vendors conservatively

An account-management provider is a separate business from FTMO unless FTMO expressly identifies it through a current official source. A brand mention, logo, affiliate link, review badge, or claim of familiarity does not establish authorization. Before considering price, performance, speed, or convenience, determine whether the actual service is permitted. If it is not clearly permissible, commercial due diligence cannot cure the account-compliance problem.

Start by requesting a plain description of the service without supplying account information. Who chooses trades? Who determines size? Who enters or modifies orders? Does a human connect remotely? Is software installed? Are signals shared among clients? What credentials are requested? Will the provider need email or identity-verification access? Does it subcontract work? A refusal to answer these basic questions is a reason not to proceed, but complete answers still do not substitute for FTMO's approval.

Do not rely on claims that a method is undetectable, has operated for years, uses a clean address, resembles the client's style, or has never caused a problem. Such assertions shift attention from permission to evasion and may be impossible to verify. This page does not investigate or repeat vendor success rates, customer outcomes, or pass rates. No performance claim demonstrates compliance with FTMO's current account terms.

Refund promises require separate analysis. A vendor's refund, replacement, warranty, retry, or guarantee cannot restore an account, reverse an FTMO decision, protect personal data, or create permission under FTMO rules. Read the vendor contract if the underlying activity has first been confirmed as allowed, and consider payment and consumer risks independently. Do not assume that a commercial remedy covers all possible consequences.

Marketing language is not an operational description

Words such as "hands-free," "assisted," "done for you," "challenge support," "automation," and "mentoring" can conceal important differences. Translate each promise into account actions. "We handle risk" could mean educational guidance, software settings, or discretionary position control. "No password needed" could still involve remote control or individualized execution instructions. Ask for the factual workflow and then present that workflow accurately to FTMO.

A provider may argue that the client remains responsible because the client bought the account or clicks a confirmation. Responsibility language does not by itself answer whether another party is allowed to direct activity. Another may claim that using an expert adviser makes outside management acceptable. Software permission, where it exists, should not be interpreted beyond the current official scope. Verify the actual strategy, copying relationship, operator, and deployment rather than reasoning from platform capability.

Do not provide data for a preliminary quote

A vendor generally does not need a trading password, identity document, mailbox login, recovery code, or live remote session merely to explain its service. Decline such requests. Share the minimum non-sensitive facts needed for due diligence, and stop if permission cannot be established. Once secrets or documents are copied, ending the commercial discussion may not eliminate the exposure.

If a service pressures the reader to act before asking FTMO, claims that support must not be told, or offers instructions for avoiding account linkage, the compliance answer is to disengage. Preserve relevant communications if needed for a truthful report, secure any information already disclosed, and use official channels. This guide deliberately excludes technical details that could facilitate circumvention.

There is no need to investigate how a questionable provider might avoid controls. The decision can be made at the authorization level. When another person would operate the account and no clear current FTMO permission exists, retain personal control and decline the arrangement. Education that does not touch the account may be a safer alternative, but its specific format still must follow the applicable rules.

EA, copy trading, HFT, signals, and remote tools need separate reviews

Account management is often bundled with technical terms that sound more precise than they are. An expert adviser, or EA, is software, but that fact alone says little about who designed its decisions, whether activity is copied, how it behaves, or whether its particular use is allowed. FTMO's current FAQ, Trading Objectives, Terms and Conditions, and any linked prohibited-practice materials should be checked for the exact deployment. Ask support when those sources do not clearly resolve it.

Describe an EA by function at a compliance level. Does it merely alert the client, calculate position size, place orders from the client's own rules, mirror an outside source, or receive decisions controlled by another party? Who can change its configuration? Is the same activity distributed to multiple accounts? Does a vendor retain remote access? These questions help classify the arrangement without exposing source code or seeking monitoring details.

Do not infer that a platform feature equals program permission. Trading platforms can technically support many functions that a particular service agreement may restrict. Likewise, a general statement about automated trading should not be extended to every execution pattern. Current official language and a truthful support description are the appropriate guides. If approval depends on stated conditions, preserve them and reassess after material changes.

Copy trading can describe several different relationships

A person may copy between personally controlled accounts, follow a public signal, mirror another trader, distribute trades to customers, or use software that produces similar activity. Those facts are not interchangeable. This article does not declare which version FTMO currently permits. Readers must consult the listed official sources and ask FTMO about their precise account model, account ownership, source of trades, and stage.

When submitting a copy-related question, identify every source and destination account by ownership category without posting credentials. Explain whether decisions originate from the named client, another human, a commercial service, or software. State whether execution is automatic and whether multiple clients receive the same instructions. Do not omit the source merely because the final order appears on the client's device.

HFT is not a dependable yes-or-no label

High-frequency trading may mean different things in casual marketing, platform communities, and professional market structure. Avoid asking only, "Is HFT allowed?" Explain the functional characteristics relevant to FTMO's current rules, such as automated order generation, expected holding approach, data dependency, and order behavior, without asking for tolerances or enforcement thresholds. FTMO must classify the proposal under its own current terminology.

This page makes no claim that a given speed, holding period, order count, or cancellation rate is permitted. It provides no boundary-testing method. If a strategy depends on finding the maximum behavior that escapes a control, that is not a sound compliance plan. Obtain a clear first-party answer about the intended method and comply with every current Trading Objective and prohibited-practice provision.

Signals do not eliminate the discretion question

A signal might be broad market commentary, a standardized alert, an individualized instruction, or an input that triggers automatic execution. The account holder's nominal ability to ignore a message does not necessarily settle how the complete arrangement is treated. Describe who creates the signal, who receives it, how execution occurs, and who controls size and exits. Ask FTMO instead of relying on the signal seller's interpretation.

Remote tools create an additional layer. Legitimate technical support may sometimes use screen-sharing or remote-assistance software, but an outside trader can use similar technology to control an account. The software name does not decide permission. Identify what the remote person can see and do, whether the client is continuously present, whether orders can be entered, and whether credentials become visible. Do not begin the session until FTMO has answered any material rule uncertainty.

Recheck after every material change

Software updates, strategy revisions, new signal sources, hosting changes, vendor acquisitions, and transition between account stages can alter the compliance facts. Approval for one version should not automatically be carried to another. Maintain a short versioned description of the approved setup and compare revisions against it. When a change affects order decisions, execution, copying, outside access, or risk controls, submit an updated question.

Risk controls remain necessary even if a tool or method is accepted. Verify all current Trading Objectives directly. Test software only in environments and ways allowed by the relevant terms, use conservative safeguards, and supervise its operation as required. This article does not promise that technical controls will prevent breaches, outages, slippage, or losses. Automation can fail, and account responsibility cannot be outsourced merely by installing software.

Legality, contracts, account reviews, and disputes

Whether an arrangement is legal is not the same question as whether FTMO permits it. A service might be lawful in one jurisdiction yet inconsistent with a private program agreement. Another arrangement might raise licensing, consumer, privacy, tax, employment, or financial-regulation questions beyond the scope of FTMO's platform rules. This article does not provide a legal conclusion about account management, passing services, signals, EAs, or prop trading.

Jurisdiction matters. The client, vendor, payment provider, data host, and contracting entity may be located in different places. Definitions and regulatory treatment can vary. Marketing claims such as "fully legal," "regulated method," or "not investment management" should not be accepted as legal advice. Ask the vendor to identify the contracting business and applicable terms, but consult a qualified local professional where the legal characterization matters.

FTMO's current Terms and Conditions should be read for the governing provisions applicable to the account. This page will not summarize their legal effect because the relevant version and facts matter. Pay attention to incorporated documents, client representations, termination or suspension terms, complaint processes, notices, dispute provisions, and amendment language. Those categories are reading prompts, not assertions about a particular current clause.

Do not confuse a completed objective with final approval

Meeting displayed trading metrics should not be assumed to waive identity, account-control, verification, or prohibited-practice requirements. Check the current official process for the applicable stage. A dashboard result, certificate, or automated message may not answer every eligibility issue. This article does not predict whether a particular review will occur or what outcome it will produce.

Similarly, a prior payout or transition does not necessarily authorize future conduct. Past processing may reflect different facts, terms, stages, or information. Never present an anecdote as a binding precedent. Continue to follow current rules and recheck changed arrangements. If FTMO asks for information, respond accurately through the designated channel and preserve what was submitted.

If an account is questioned

Stop any disputed outside access. Secure credentials and associated email. Read the notice fully and note deadlines. Gather original, relevant records without altering them. Answer questions directly and distinguish what is known from what is uncertain. If an outside person was involved, describe that involvement truthfully. Do not create backdated agreements, edit messages, coordinate a false account, or blame a technical system without evidence.

Use the appeal, complaint, or review process FTMO currently identifies. Keep communication professional and organized. One chronology with attached supporting records is generally easier to understand than many inconsistent messages. If the issue has material legal or financial consequences, obtain independent professional advice. An online article cannot assess evidence, rights, deadlines, or remedies for an individual dispute.

Beware of recovery services that promise to reverse an account decision for an advance fee or request identity and payment credentials. Verify any representative independently and understand the engagement. A self-described specialist cannot guarantee FTMO's response. Do not compound an account issue with another disclosure of sensitive data.

Truthful records are useful, but not a guarantee

Preserving support tickets, agreements, notices, access-security events, and platform statements can help explain facts. Records do not force a particular contractual interpretation or outcome. Their value lies in accuracy and chronology. Selective or manipulated evidence can damage credibility and may create additional concerns. Keep originals and disclose context when asked.

Do not threaten staff, impersonate counsel, publish personal information, or make accusations unsupported by evidence. A disagreement about account treatment should proceed through the available official routes. Public discussion should remain factual and respect privacy and applicable law. If the process does not resolve a serious concern, qualified advice is the appropriate next step, not a bypass attempt.

A compliance workflow before any outside involvement

A structured workflow prevents marketing urgency from replacing analysis. Step one is to define the objective. Is the client seeking education, operational convenience, automated execution, risk calculation, trade ideas, or full discretionary management? Write the desired outcome without naming a vendor. This makes it easier to find an alternative that does not require account access or outside control.

Step two is to map every person and system. Identify the named account holder, educator, developer, signal source, hosting provider, technical assistant, payment recipient, and anyone with remote permissions. For each participant, record what they can decide, view, change, and execute. Include access to email and recovery channels. If the map is difficult to obtain from a seller, do not provide credentials or money while facts remain hidden.

Step three is to identify the exact FTMO product and stage. Use current first-party terminology from the dashboard and agreement. Gather the applicable Terms and Conditions, FAQ entries, Trading Objectives, and linked rule materials. Note effective dates and any account notice. Avoid substituting a review of another product or a historical blog post.

Step four is to compare conduct with the sources. Highlight passages concerning account responsibility, third parties, trading methods, copying, automation, prohibited practices, identity, and security where those concepts appear. Read definitions and exceptions in context. Do not transform silence into permission. An unanswered factual scenario belongs in a support request.

Step five is to assess data exposure before contacting a provider further. List every credential or document requested and ask why it is necessary. Decline access to passwords, mailbox recovery, one-time codes, identity sessions, and remote control. Even if the business case appears attractive, wait until FTMO confirms the activity and the security review is satisfactory.

Step six is to send FTMO a precise written question. Describe the actual workflow, not the vendor's category. Identify who originates decisions and who can execute them. Mention software, copying, remote access, and credential custody. Link the relevant official wording. Ask for an answer applicable to the specified product and stage.

Step seven is to interpret the response conservatively. A narrow yes is not approval for adjacent features. A conditional answer requires every condition. An unclear response requires clarification. A refusal ends that proposed configuration. Silence, delay, or an automated acknowledgement is not permission. Keep personal control while awaiting a substantive answer.

Step eight is commercial due diligence, performed only if the rule question has been resolved positively. Verify the vendor's legal identity, contract, privacy practices, security controls, cancellation terms, conflicts, and representations. Do not infer quality from affiliates or testimonials. This article reports no tests, prices, performance statistics, or customer outcomes and should not be read as recommending a provider.

Step nine is to configure the approved arrangement no more broadly than necessary. Keep secrets private, restrict permissions, retain the ability to stop activity, and document the version reviewed. Verify all current Trading Objectives independently. If the arrangement cannot operate without broader control than FTMO considered, return to support before use.

Step ten is ongoing review. Revisit the documentation at account transitions, major software updates, changes of operator, new signal sources, travel or device changes that implicate a current rule, and before relying on old guidance. Monitor official notices. Stop and ask again when the factual basis for an earlier answer no longer matches.

Compact go or no-go checklist

• The proposed activity is described in concrete actions, not marketing terms.
• The named client keeps identity, email, recovery, and platform credentials secure.
• No outside person exercises undisclosed discretion or account control.
• The correct current product, stage, agreement, and objectives were reviewed.
• Any uncertainty was presented honestly to FTMO through an official channel.
• The written answer addresses software, copying, remote access, and human roles as applicable.
• The implementation matches the facts FTMO considered and every stated condition.
• Commercial claims were evaluated separately from account permission.
• Applicable legal questions were referred to qualified independent advice.
• A material change triggers a new review rather than assumed continued approval.

If any item fails, pause. The cost of waiting is usually easier to control than the consequences of exposing credentials or creating an eligibility dispute. A legitimate educator or software supplier should be able to explain its role without secrecy and allow time for first-party verification. Pressure to skip those steps is not evidence that the arrangement is safe.

Compliant alternatives when management is not approved

The reader can trade personally after studying the current objectives, use general educational material that does not control the account, practice risk procedures independently, or choose not to purchase the program. If considering software, select only a configuration whose actual function has been verified under current rules. If the intended business model requires outside discretionary management, seek a different lawful product explicitly designed for that relationship rather than misrepresenting control.

Common questions about FTMO account management

Can a friend trade my FTMO account?

Do not assume friendship, family status, payment status, or a brief duration creates permission. Another person's order entry or discretion presents the same core account-control question. Keep the account personally controlled and ask FTMO about the exact facts under the current agreement before allowing any involvement.

Can a professional manager pass an evaluation for me?

A professional title does not authorize access. A passing service or manager is separate from FTMO and cannot approve its own activity under FTMO's rules. This article does not endorse such services or verify their claims. Describe the proposed control and credentials to FTMO, and do not proceed without clear current authorization.

What if the provider never receives my password?

Password custody is only one fact. Remote control, persistent software access, individualized instructions, linked execution, or control of another authenticated device may still allow an outsider to influence or operate the account. Tell FTMO how decisions and execution actually work instead of treating password retention as decisive.

Does clicking the trade myself make management acceptable?

Not necessarily. The relevant facts can include who selected the trade, risk, timing, and exits, plus how individualized or automated the instruction is. FTMO's current rules and direct guidance should classify the real workflow. Do not use a nominal click to disguise another person's discretion.

Are EAs allowed?

Check the current official FTMO sources for the particular EA behavior, product, and stage. General automation language should not be taken as approval for all strategies or for human account management delivered through software. Explain decision origin, copying, execution, control, and vendor access to support when uncertain.

Is copy trading allowed?

The answer can depend on account ownership, trade source, execution method, distribution, and current FTMO wording. Do not rely on a universal statement from another firm or an old discussion. Review FTMO's current materials and request an account-specific written answer with all sources and destinations accurately described.

Is HFT allowed on FTMO?

HFT is too ambiguous for this page to answer without a defined strategy. Verify current prohibited-practice language and describe relevant automated behavior to FTMO. Do not request a detection threshold or attempt to operate just below an assumed limit. Technical feasibility is not contractual permission.

Can two people in one household have accounts?

A shared household and internet connection do not by themselves establish either authorization or wrongdoing. Current rules may address account ownership, identity, devices, locations, or related patterns. Each person should maintain truthful separate control and ask FTMO how the present policy applies before creating an uncertain setup.

Will using a VPN solve an IP concern?

A VPN is not a compliance solution and must not be used to disguise the operator or location. This guide gives no concealment advice. Ask FTMO about legitimate travel, privacy, work-network, or connectivity circumstances and follow its current answer. Keep identity and account-control facts truthful.

Is account management illegal?

This article makes no legal conclusion. Legality depends on jurisdiction, services, parties, representations, and potentially regulatory or licensing frameworks. Permission under FTMO's rules is a separate contractual question. Obtain appropriate legal advice if the arrangement's status matters.

Can a vendor guarantee that my account remains safe?

No outside vendor can bind FTMO or guarantee how FTMO will apply its current agreement to facts. A refund or replacement promise is a separate commercial claim. It does not secure data, preserve eligibility, or assure a payout. Verify permission directly and retain personal control.

What if many reviewers say the service works?

Reviews do not establish FTMO authorization or representative outcomes. They may be outdated, incomplete, incentivized, or connected to another product. This page reports no testimonials or performance testing. Use current official sources and a direct support answer rather than popularity as the compliance test.

Should I disclose a technical helper?

If a helper can view, access, change, or operate account-related systems, include that role in the support description. If the task is genuinely unrelated, avoid unnecessary data sharing. When uncertain, explain the exact permissions to FTMO before a session begins.

What should I do after accidental credential sharing?

Secure the account and associated email, terminate outside access, preserve truthful records, and contact FTMO through an official route for current instructions. Do not conceal or alter the event. Consider independent security or legal help where the exposure warrants it.

Does passing change the account-management rules?

Do not assume so. A transition may involve a different agreement, stage, or set of instructions, and ongoing conditions may remain relevant. Read every new document and ask FTMO whether an earlier answer still applies. Passing displayed objectives is not general permission for outside control.

How often should I recheck the rules?

Review them before purchase, at stage transitions, after material setup changes, and whenever FTMO issues an official notice relevant to the account. The source verification date on this article cannot keep a reader's account current. Save the version relied upon and follow later applicable instructions.

What if support does not answer clearly?

Keep the account personally controlled. Reply with one precise factual question, identify the unresolved activity, and ask which official provision applies. Use any current escalation path. Do not interpret uncertainty as permission and do not ask successive agents to endorse a concealed variation.

Can an affiliate authorize a provider?

No affiliate statement should be assumed to amend FTMO's rules. Verify whether FTMO itself currently identifies an arrangement as permitted and whether that identification covers the exact service. Commercial relationships and permission for account operation are distinct issues.

What evidence should I keep?

Keep the applicable agreement, dated official pages, purchase materials, complete support correspondence, original notices, and ordinary security records relevant to the question. Avoid unnecessary sensitive collections. Records support an accurate chronology but cannot guarantee an outcome or replace compliance.

Conclusion: keep control unless FTMO clearly confirms otherwise

The practical answer to "does FTMO ban account management" begins with a cautious rule: do not let another person manage, access, or trade the account unless FTMO has clearly approved the exact arrangement under the current materials for that account and stage. "Account management" is not sufficiently precise on its own. The conduct, authority, credentials, decision process, execution path, and product context determine the question that must be asked.

Use the official FTMO FAQ, Trading Objectives, and Terms and Conditions listed below. Read their latest versions and any documents they incorporate. Check the account dashboard and official notices. Record what was reviewed and ask support about unresolved facts. Because rules and products can change after this article's verification date, never treat this editorial page as a permanent statement of FTMO policy.

Keep identity and credentials under the named client's control. Do not allow remote operation, order entry, recovery access, or discretionary decisions while permission is uncertain. Evaluate EAs, copying, signals, HFT descriptions, technical support, and IP circumstances separately because none of those labels automatically answers who controls the account. Never use technical measures to disguise a person, place, device, or execution source.

Treat account managers and passing services as independent vendors. Their sales claims, affiliates, reviews, refunds, and asserted history cannot authorize activity for FTMO. This review provides no test results, success statistics, prices, pass rates, or testimonials. It does not predict a payout, funding decision, account review, or dispute outcome. Compliance should be established before commercial value is considered.

Finally, separate contractual permission from legality. FTMO can explain its current program position, while qualified independent professionals can advise on legal questions in a relevant jurisdiction. Neither inquiry should be replaced by online reassurance. If the answer remains unclear, the defensible decision is to pause, trade personally, protect the account, and choose a route whose permission can be documented.