Ask the broker or funding provider that issued the account to confirm its status and the reason for the restriction. A disabled account, successful Rithmic login and missing trading permission are different states. Preserve the exact message and account context; reconnecting, changing gateways or resetting a password does not establish that a trading restriction has been removed.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Identify what is actually restricted
| Symptom | Investigation |
|---|---|
| Entire login rejected | Issued credentials, System, login/account status |
| Login works, account missing | Account provisioning, expiry, removal or application scope |
| Account visible, new order rejected | Exact rejection, permissions and applicable risk restrictions |
| Only liquidation-related actions allowed | Provider restrictions and the actual account state |
| Copier unavailable | Copy-trading entitlement separately from ordinary account access |
A green connection indicator does not establish that every account under the login can submit an order. The inspected native session also had a separate copier-not-enabled message, illustrating why access to one feature is not proof of access to another.
Check status through the issuer
- Preserve the exact message, timestamp/timezone, platform/version and selected account context.
- Review the provider's authenticated account-status information and current rules for that account stage.
- Check whether the relevant subscription or account has expired, been removed or reached an applicable restriction. Do not diagnose failure from a label alone.
- Ask the issuer to confirm which restriction applies and what official process, if any, restores access.
- After a confirmed change, reconnect when appropriate and verify the intended account and permissions through the supported workflow.
Apex's login article includes account expiration in its checks. Quantower's issues guide gives a provider-evaluation interpretation for “Only Admins Can Place Trades.” These are scoped examples. They do not establish one universal reason for all disabled accounts or every occurrence of that text.
If positions or orders may remain
Confirm their state with an available supported interface or the provider. Do not assume disablement flattened the position, canceled all orders or guarantees that an exit action is permitted. Ask the provider which urgent procedure applies to the restricted account.
Risk parameters can explain some restrictions, but their visible fields and actual enforcement are separate. Read risk parameters and liquidation-only access without changing controls to experiment.
Keep recovery operations distinct
A password reset concerns a credential. An evaluation-account reset, reactivation, subscription renewal or permission change can be a different operation. Use the provider's exact wording and terms. Do not buy a reset or new subscription merely because an app cannot log in.
Support needs the error, time, application version, System/Gateway and affected account identity through its official channel. Do not send a password or publish private identifiers in an article screenshot.
Common questions
Can I log in while one account is disabled?
The login and individual account permissions are separate checks. Verify which account is affected instead of assuming that login success makes all accounts tradable.
Does changing gateways restore a disabled account?
No restoration is established by a gateway change. The provider must confirm the account restriction and permitted recovery process.
Should I reset the password?
Only when credential recovery is the actual problem. See password reset for that separate task.
Does disabled always mean a drawdown breach?
Do not infer a single cause. Ask the issuer to confirm the account-specific reason and evidence.