> For the complete documentation index, see [llms.txt](https://leveracc.gitbook.io/leveracc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leveracc.gitbook.io/leveracc-docs/how-it-works/accounts-and-permissions.md).

# Accounts & Permissions

LeverAcc Accounts on HyperEVM: what the owner, execution and risk wallets can and cannot do, and the governance roles above each account.

## One account per user, per project

Every trader gets a **LeverAcc Account**: a smart contract on HyperEVM created by the Account Factory from the user's wallet, the partner's project ID and a salt. The Account is the user's financing ledger. It is not a custodial wallet and not a 4337 smart wallet.

The user's **owner wallet** (their own self-custodied EVM wallet) controls the Account. Every money-moving action — borrow, repay, withdraw, stop — requires the owner's EIP-712 signature.

## Wallets and what they can do

| Wallet               | Held by                                       | Can                                                                                   | Cannot                                |
| -------------------- | --------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------- |
| **Owner wallet**     | User                                          | Sign borrow, repay, withdraw and stop intents; bind a project and an execution wallet | —                                     |
| **Execution wallet** | Partner (or the user, for self-run setups)    | Place and cancel orders on Hyperliquid                                                | Withdraw funds, settle                |
| **Risk wallet**      | LeverAcc (generated and kept by the platform) | Cancel orders, reduce or close positions                                              | Withdraw funds, open new risk, settle |

Binding an execution wallet requires both the owner's signature and the partner project's approval. Execution wallets can be rotated or revoked; if a wallet is lost or compromised, a recovery path lets the owner restore control on HyperCore without moving funds.

## Roles above the account

| Role                             | Purpose                                                   |
| -------------------------------- | --------------------------------------------------------- |
| Super Admin / Super Operator     | Protocol governance and operations                        |
| Project Admin / Project Operator | Per-partner configuration (borrow caps, approvals)        |
| Guardian                         | Emergency freeze and account-level withdrawal restriction |

The protocol can be put in **Frozen** mode in an emergency. Governance actions from LeverAcc's control plane go through a create → approve → execute workflow with a full audit trail.