Skip to content

Set up a vault from start to finish

A vault records investor capital and funds defined credit facilities. Start with the deployment steps, then configure the operating policies on the saved vault.

Before you start

  • Open the Asset Manager workspace with an approved entity and the wallet authorized for vault creation.
  • Confirm the network, approved deposit asset, and the asset's decimals.
  • Save the people or wallets that will serve as Curator, Allocator, Guardian, and Fee Recipient in Roles.
  • Agree the vault's share structure, fee model, participation rules, and intended credit facilities.

A fee recipient receives fees. that assignment does not grant authority to deploy or configure the vault.

1. Choose the vault and team

Go to Vaults → Add Vault. The first step is Vault & Team.

Add Vault with Vault Name, Deposit Asset, Curator, Allocator, Guardian, and Fee Recipient controls.
Add Vault: Vault & Team · Product interface with sample records. Select the image to open it at full size.
  • Vault Name: enter a name of up to 21 characters. Use a name investors can recognize in the vault list.
  • Deposit Asset: select an approved saved asset. Its identity, symbol, and decimals determine amount inputs and the generated vault logo.
  • Curator: select the saved role responsible for the vault's permitted configuration actions.
  • Allocator: select the saved role responsible for allocation within approved facilities and caps.
  • Guardian: select the saved role for the supported protective actions.
  • Fee Recipient: select the saved fee recipient. Check the address behind the display name.

The owner is resolved from the current entity and authority context. Selecting a team member does not grant additional authority.

2. Choose the vault type

Open Vault Type and choose Single Share or Senior / Junior tranche vault.

Vault Type with Single Share and Senior / Junior tranche vault choices.
Add Vault: Vault Type · Product interface with sample records. Select the image to open it at full size.

Single Share uses one share class. A tranche vault separates Senior and Junior claims. Tranche settings appear only when the chosen structure supports them.

For a tranche vault, set Senior Target Yield and Min. Junior Buffer as percentages. These settings define the configured allocation and protection rules. they do not guarantee a return or eliminate credit losses.

Check which asset and transfer policies apply before choosing a tranche structure. Continue with the structure shown in the summary panel.

3. Choose how fees are charged

Open Fee Mode. Choose Charge borrowers or Charge depositors.

Add Vault: borrower-paid fees
Add Vault: borrower-paid fees · Product interface with sample records. Select the image to open it at full size.
  • Charge borrowers: set the manager spread. The creation control accepts 0–2%. This spread follows the borrower-interest fee path.
  • Charge depositors: set the Performance Fee, from 0–50%, and Management Fee, from 0–5%, where displayed.
  • Confirm the fee recipient and the chosen model in the summary. A hidden field from the other model is not an additional fee selection.
Add Vault: depositor-paid fees
Add Vault: depositor-paid fees · Product interface with sample records. Select the image to open it at full size.

These are control limits, not recommended fee levels. Protocol fees and manager fees have distinct accounting and cash paths.

4. Choose share mobility

Open Share Mobility. Select the transfer profile supported by the chosen vault and share structure.

Add Vault: Share Mobility
Add Vault: Share Mobility · Product interface with sample records. Select the image to open it at full size.

Review whether shares are non-transferable, protected by policy, or support manager-authorized adapters. A transferable share remains subject to the applicable access and asset policies.

Adapter authorization does not establish economic safety or guarantee that an adapter will return shares. Read Share Mobility before enabling an adapter-dependent workflow.

5. Review and create the vault

Check the summary against your mandate: deposit asset, team wallets, vault type, fee model, and mobility profile. Submit the creation action and complete the required wallet steps.

Wait until the new vault appears in Vaults with a saved contract address. Open it and reload. Confirm the saved settings match the review.

6. Configure operating policies

In the new vault, open Settings.

  1. Set Limits & Access: deposit cap, minimum deposit, per-user cap, and participation rules.

  2. Review Fees, recipients, and automatic sweep thresholds where available.

  3. Verify Roles and the authority attached to each wallet.

  4. For a tranche vault, review Tranches.

  5. Review Withdrawal Policy and Share Mobility.

7. Connect credit facilities

Open Credit Facilities in the vault. Select an approved facility and review its loan asset, collateral asset, oracle, and rate model.

Configure Allocation Capacity, Rate Limits, Oracle Policy, and Availability.

Use Allocation to commit capital within the approved limits. Allocation authority does not grant permission to change deployments, employee authority, recovery settings, or payout recipients.

8. Check readiness before accepting capital

  • The vault appears after reload with the intended asset, structure, and team.
  • Participation and deposit limits match the mandate.
  • Fee recipients and percentages match the saved review.
  • Each intended facility has the correct availability, capacity, draw controls, and valuation policy.
  • Allocation and routing use approved facilities. Required liquidity and exit constraints are understood.
  • The investor-facing vault details and fact sheet show the intended terms.

Resolve common setup problems

No deposit asset: check approval and support for the selected network. Register or approve the asset through the appropriate authorized workflow first.

No saved role: add the role in the manager's Roles workspace. Reopen Add Vault and select the saved record.

A control is unavailable: review your current wallet, entity, role, and the chosen vault structure. Unsupported or unauthorized controls cannot be enabled by changing local input values.

The transaction confirmed but the vault is absent: check the operation status and persisted data refresh. Keep the transaction reference and avoid creating a second vault while the first creation is unresolved.