Transaction limits decide what happens when a transaction is large enough, or unusual enough, to deserve a second look. They don't block activity outright — they hold a transaction for a delay, send it for approval, or wave it through, depending on the rule it matches.

Small teams can get by with one rule. Workspaces with several users, or with higher operational risk, will want a few.

The Set transaction limit popup opens in Basic mode. Use Switch to advanced mode if you need per-account, per-destination or per-user rules.

Basic mode sets one limit across all accounts and all users for the period you choose, and applies it to withdrawals — both to saved address book records and to external addresses. It is the fastest way to get a meaningful limit in place.

Pick the period from the selector at the top: Daily transaction limit (24 hours), Monthly transaction limit (30 days) or Single transaction. With a daily or monthly period the limit applies to the combined value of transactions inside that rolling window; with Single transaction the rule checks each transaction on its own.

Type an amount, or use the $10,000 / $50,000 / $100,000 quick picks.

Tick Any amount to drop the threshold entirely — the rule then applies to every single transaction, regardless of value and regardless of period. Unticking it returns the form to a daily $10,000 limit, so re-enter your amount if you had one.

Choose what happens when the limit is exceeded:

Security delay — the withdrawal is delayed for a set time. Enter the Delay duration in hours; anything from 1 hour to 8760 (a year) is accepted. This works in a workspace of any size.

User approval — approval is required before execution. Set the Authorized approvers — leave Owners only to use current and future Owners, or pick individual users — and how many approvals you need under Approval required. At least 2 approvals are required, and the request creator counts as the first approver, so a second person always has to act.

Two switches sit at the bottom of basic mode: Swap and DeFi.

Both cover operations that need to be signed immediately. If they are not excluded from the limit, you simply won't be able to create a swap or a dApp transaction that exceeds it. Switch them on to let those operations through, off to hold them to the same rule as a normal withdrawal.

Check both switches before you confirm — they decide whether your everyday swaps and DeFi activity keep working under the new limit.

Advanced mode exposes every parameter, in this order:

Transaction amount threshold — the amount that triggers the rule, or Any transaction amount to apply it to everything.

Transaction type — Single transaction (the rule checks each transaction on its own) or Multiple transactions (the rule checks the combined value over a period).

Accumulation period (hours) — for multiple transactions only: the window during which amounts add up toward the threshold. Up to 336 hours (14 days).

From — the source accounts: one, several, or All existing and new accounts. With several accounts selected, the threshold applies to their combined total. Hidden accounts appear in the From/To search only after you reveal them with their PIN.

To — where the rule applies. Tick any combination of:

Applies to — All existing and new members, Owners only, or a specific set of users.

Protection — the same two options as basic mode, plus a third:

In advanced mode the approval hint reads: when an approver creates a transaction, their own approval is counted automatically — so if 3 approvals are required, only 2 more people need to act.

Additional exceptions — Swap (with an asset scope: all swappable assets, or a specific list) and DeFi (Wallet Connect). Unlike basic mode these are checkboxes and start unticked, so a new advanced rule applies to swaps and DeFi unless you say otherwise.

Each rule appears as a row with these columns:

Open a rule to review a pending request: New transaction limit request, Security delay applied or Approve transaction limit removal, each with Approve / Reject, and Cancel request for whoever created it.

Security delay and Exception rules are unlimited on every plan. The number of rules that use User approval depends on your plan — once you reach it, the popup tells you which plan lifts the cap. See Plans and billing in Settings.

Claiming rewards, staking, providing liquidity or any other action you sign through dApp Connect is a DeFi transaction. If one of your rules covers it and the DeFi exception on that rule is off, the transaction follows the rule's action — so it waits out the security delay or sits pending approval.

This happens regardless of the amount: dApp transactions don't carry a reliable USD value, so amount thresholds are ignored for them and even a small claim is caught by a rule with a high threshold.

To let DeFi transactions through in future:

Your Security Policies protect changes to your rules — not the transactions themselves. If the Manage transaction limits policy is enabled, creating, editing or deleting a rule is held until one of these is satisfied:

Both options are available on all plans. Only Owners can edit security policies. Enabling the Manage transaction limits policy for the first time takes effect immediately; disabling or re-enabling it later goes through the Policy change rule.

Configure it in Settings → Security → Security policies.

Suppose your workspace has an Owner with unlimited access, a Finance Manager who handles regular payments to known addresses, and an Operations Manager who manages the portfolio.

For the Owner:

For the Finance Manager:

For the Operations Manager:

Start in basic mode with a single daily limit, then switch to advanced and add the per-person rules once you know where the friction is.

If you have questions, contact our support team via messenger on the Bron platform or by email support@bron.org.