> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/safety-and-controls/account-controls.md).

# account controls

## account controls

the account page is the control center for identity, wallets, x surfaces, and bridge preferences.

### identity and wallet

you can:

* link an x identity
* link a supported evm wallet
* select the canonical trading wallet
* use an external manual wallet or an eligible embedded wallet
* review whether delegated execution is available

### x controls

mentions and dms can be enabled or disabled independently. turning one off stops new commands from that surface without removing the other.

operator-level hard stops can disable social trading, mention trading, dm trading, bridging, or execution even when your account setting is on.

### action controls

depending on the active deployment policy, an action may require:

* delegated-wallet enrollment
* explicit confirmation
* mfa
* a trading disclosure
* regional or sanctions checks
* daily or per-trade notional limits
* minimum liquidity
* a wallet policy

these checks are evaluated at execution time. changing an account preference does not guarantee that a pending action will pass later policy checks.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trover.tech/safety-and-controls/account-controls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
