Account settings & signing authority
Understand the effect of account changes before approving them.
Browse all 38 guides
Available controls
Account settings opens on Overview, with the XRP balance, trust-line count and signing access. Choose Trust lines, Profile & incoming, Signing & keys, Issuer controls or Delete account. On mobile these categories wrap into a grid. Trust lines includes asset/issuer search; Add asset or Edit opens the focused editor. Signing authority, issuer permissions and deletion each keep their own review and wallet approval. Inline cautions identify signing lockout risks, effects on token holders, permanent No Freeze/clawback choices and account deletion. Cautions do not verify that you control an alternative key: independently test your signing methods before changing access.
| Area | Controls |
|---|---|
| Trust lines | Create or update a trust line; remove eligible zero-balance lines |
| Public properties | Domain, hashed avatar email and message key |
| Incoming preferences | Destination tags, deposit authorization and incoming-object restrictions |
| Issuer settings | Authorization, Default Ripple, Global Freeze, No Freeze, clawback permission, transfer rate and tick size |
| Security | Regular key, signer entries and quorum, master-key access |
| Delete account | Eligibility checks, full-address confirmation and destination review |
Critical account changes
Read the consequence warning and full transaction fields. Enabling No Freeze or issuer clawback is permanent. Disabling the master key can remove your ability to act if you do not control another working signing method. Never treat the existence of a regular-key address as proof you control its private key.
A signer-list transaction changes multi-signing permissions. This interface does not collect multiple signatures or recover missing keys. Account deletion closes the ledger account, burns the protocol deletion fee and sends eligible remaining XRP to the specified destination.
Wallet support
Xaman, Ledger USB and CROSSMARK use the same reviewed transaction submission path. A particular device, firmware, wallet or transaction type can still be rejected by the signing wallet. Do not enable blind signing or reveal a seed to work around a rejection. Xaman profile sign-in uses the provider’s verified account identity. Ledger and CROSSMARK ownership proofs currently require the classic address’s master-key signature; regular-key and multi-signature proof login are not implemented.
References
For protocol details and wallet integration documentation.
XRPL AccountSet reference