Vault policies

Vault policies control the maximum value that can be moved through a vault within a defined period. Policies are enforced before the signing stage. If a movement exceeds a policy limit, it is blocked and never reaches signers.

Updated 05 Aug 20261 min read

#Setting a transaction limit

Required role: Owner, or a role with the Manage Workspace permission.

Required permissions: MANAGE_WORKSPACE

  1. Navigate to the Policies page.
  2. Select the vault whose limits you want to configure.
  3. Set the Transaction Limit. This is the maximum amount for a single movement from this vault.
  4. Save the policy.

#Configuring a cycle period

Required role: Owner, or a role with the Manage Workspace permission.

Required permissions: MANAGE_WORKSPACE

A cycle period defines how frequently the vault's usage counters reset. SQRL supports two cycle periods.

  • Weekly. Counters reset once per week on the configured cycle day.
  • Monthly. Counters reset once per month on the configured cycle day.
  1. Navigate to the Policies page and open the vault's policy settings.
  2. Select the Cycle Period, either Weekly or Monthly.
  3. Set the Cycle Day. This is the day of the week for weekly, or the day of the month for monthly, when counters reset.
  4. Save the policy.

#Per-role limits

Required role: Owner, or a role with the Manage Workspace permission.

Required permissions: MANAGE_WORKSPACE

In addition to vault-level limits, you can set per-role limits. These restrict how much a user in a given role can initiate within a single cycle, regardless of the vault's overall limit.

  1. Navigate to the Policies page.
  2. Open the policy settings for the role you want to limit.
  3. Set the limit amount for the role.
  4. Save the policy.
Key takeaway

Policies create a pre-signing safety net. A movement that violates a policy never reaches the signing stage. This stops costly mistakes before they progress through the signing workflow.

Was this page helpful?