Transaction limits help you maintain control and security over your funds, especially in larger or distributed teams. While small teams may not need complex rules, setting up transaction policies is essential for workspaces with multiple users or higher operational risks.
1. What Can Be Configured
To set a transaction limit, go to Settings → Transaction Limits → Set New.
You can configure transaction limits based on the following parameters:
Transaction Amount Threshold — Set a minimum amount that triggers the rule, or apply it to any transaction amount.
Transaction Type — Choose between a single transaction (applies to each individual transaction) or multiple transactions (applies to the total value over a defined period).
Source Accounts (From) — Apply the rule to one, several, or all existing and future accounts. The threshold applies to the combined total across selected accounts.
Destination (To) — Define where the rule applies: Address Book, External Addresses, or Accounts (internal transfers).
Applies To (Users) — Choose whether the rule applies to selected users or all existing and new users.
2. Limit Execution Options
When a limit is triggered, you can define how the transaction is handled:
Approvals — Require one or more approvals before execution. You can set the number of required approvals and select which users are authorized to approve.
Security Delay — Delay the transaction for a set period before execution.
Exception — Allow transactions to execute instantly without approval or delay.
3. Additional Exceptions
You can allow certain operations to bypass transaction limits:
Swaps — allow swaps even when limits apply
DeFi (WalletConnect) — allow DeFi transactions even when limits apply
4. How Security Policies Apply
The way transaction limits are enforced depends on your Security Policies configuration:
Security Delay — Applies a 48 hours delay before changes or actions take effect (available on all plans)
Member Approval — Requires approval from a user before execution (Enterprise plan only — $2,000/mo or 1M BRON)
💡Member approval — available on Enterprise plan only ($2,000/mo or 1M BRON)
You can configure this in Settings → Security Policies.
5. Example: Setting Up Transaction Policies
Suppose your workspace has three users:
Owner — should have unlimited access to all funds
Finance Manager — handles regular payments with a known budget to known addresses
Operations Manager — manages the portfolio
5.1 Sample Policies
For the Owner:
Transactions from any account to any address of up to $10,000 per 24 hours do not require approval.
Transactions over $10,000 per 24 hours require approval by any other user. This protects against unauthorised withdrawals if the owner's account is compromised.
For the Finance Manager:
Transactions from any account to any saved address under $5,000 per 24 hours do not require approval.
Transactions over $5,000 per 24 hours to saved addresses require owner approval.
Any other transaction over $1,000 per 24 hours requires owner approval.
For the Operations Manager:
Internal transfers between workspace accounts do not require approval.
Transactions over $100,000 per 24 hours to saved addresses require approval from one user.
Transactions over $200,000 per 24 hours to saved addresses require approval from two users.
Transactions over $50,000 per 24 hours to any external address require approval from two users.
Bron's security policy allows you to implement any workflow you have in mind.
If you have questions, contact our support team via messenger on the Bron platform or by email support@bron.org.