# Configure wallets and vaults

Vaults are organizational containers that group related wallets together. As an owner or administrator, you create vaults and wallets, configure wallet-level settings, and control which operations each wallet permits. This guide covers vault and wallet setup from the admin perspective.

## Create a vault

1. Go to **Vaults** in the console sidebar.
2. Select **Create vault**.
3. Enter a **name** and **description** for the vault.
4. Select **Create**.


Vault organization strategies
Use vaults to separate wallets by:

- **Business unit** — one vault per department or team
- **Risk profile** — separate hot wallets (frequent transactions) from cold storage
- **Asset class** — group wallets by blockchain or asset type
- **Environment** — separate operational wallets from test wallets in sandbox


## Create a wallet

1. Open the vault where you want the wallet.
2. Select **Create wallet**.
3. Enter a **wallet name**.
4. Select the **MPC quorum** to use for signing (or HSM in sandbox).
5. Select the **blockchain** the wallet supports.
6. Select **Create**.


Palisade places the wallet in a **CREATED** state and moves it to **PROVISIONED** after generating the wallet address. For MPC wallets, quorum members must approve the key generation before the wallet becomes provisioned.

New wallets are deposit-only
Palisade operates a zero-trust security model. Every new wallet blocks outgoing transactions by default. You must complete three steps before a wallet can send: create a transaction policy, register destination addresses, and enable outgoing transactions. See the sections below.

## Configure wallet settings

Open a wallet and select the **Settings** gear icon to access wallet-level configuration. The settings page has the following tabs:

### General

View wallet metadata including wallet ID, wallet address, public key, vault information, correlation ID, and external ID. All values are copyable.

### Details

View key management information for the wallet, including the MPC quorum assignment.

### Transactions

Control outgoing transaction behavior for the wallet:

#### Enable outgoing transactions

Three conditions must be met before a wallet can send:

1. At least one **transaction policy** exists for the asset you want to send.
2. At least one **address book entry** exists for the destination (not required for internal wallet-to-wallet transfers).
3. **Outgoing transactions** are explicitly enabled on the wallet.


To enable outgoing transactions:

1. Open the wallet.
2. Select **Enable transactions**.


You can disable outgoing transactions at any time from the wallet's **Settings** page.

See [Unlock outgoing transactions](/products/wallet/getting-started/unlock-outgoing-transactions) for the full walkthrough.

#### Enable raw signing

Raw signing allows the wallet to sign arbitrary data payloads, not just standard transfer transactions. Enable this only if your integration requires it.

1. Open the wallet and select the **Settings** gear icon, then go to the **Transactions** section.
2. Toggle the **Raw signing** switch to enabled.


Use with caution
Raw signing permits signing any data payload. Enable it only on wallets that need it, and pair it with strict transaction policies and approval groups.

#### Enable automatic transaction freeze

Automatic freeze places all incoming deposits into a frozen state until you manually review and unfreeze them. Use this for compliance-sensitive wallets that require manual review of every deposit.

1. Open the wallet and select the **Settings** gear icon, then go to the **Transactions** section.
2. Toggle **Freeze transactions by default** to enabled.


See [Configure transaction freeze controls](/products/wallet/admin-guide/configure-transaction-freeze) for full details.

### Sweeping

Enable or disable asset sweeping on the wallet. See [Configure asset sweeping](/products/wallet/admin-guide/configure-asset-sweeping) for setup instructions.

### Tags

Add tags to wallets for organizational purposes.

## Best practices

- **Use descriptive names** — include the purpose, blockchain, and environment in wallet names (for example, "Treasury - ETH - Production").
- **Start with deposit-only** — leave outgoing transactions disabled until you have configured policies, addresses, and approval groups.
- **Separate operational wallets from cold storage** — use different vaults with different quorums and approval requirements.
- **Minimize raw signing** — only enable raw signing on wallets that specifically need it.
- **Enable automatic freeze on compliance-sensitive wallets** — use default freeze for wallets that handle funds subject to AML or sanctions screening.


## Related guides

- [Create your first vault](/products/wallet/getting-started/create-your-first-vault) — Step-by-step vault creation
- [Create your first wallet](/products/wallet/getting-started/create-your-first-wallet) — Step-by-step wallet creation
- [Manage wallets](/products/wallet/user-interface/wallets/manage-wallets) — Reference documentation
- [Unlock outgoing transactions](/products/wallet/getting-started/unlock-outgoing-transactions) — Full guide to enabling sends
- [Blockchains and tokens](/products/wallet/user-interface/blockchains-and-tokens) — Feature availability by chain