Skip to main content

Security Policies

Updated this week

When you manage digital assets as a team, protecting funds goes beyond keeping credentials safe. You need a system that defines roles, controls actions, and ensures no single person can put your assets at risk.

Bron provides one of the most comprehensive security policy frameworks in the digital asset space — with controls that can exceed those of a traditional bank account. Let’s explore the key features and how they can help you.

You can invite team members to your workspace and assign each one a role that determines what they can see and do.

Owner has full control over the workspace and assets — they can perform any action, including withdrawals, swaps, staking, managing members, and updating security settings.

Member has operational access to assets and can interact with funds (withdraw, swap, stake), but cannot manage team members or change security settings.

Viewer has read-only access. They can view balances and activity and may be asked to confirm transactions, but cannot initiate or execute transactions independently.

Guardian is a trusted contact for account recovery. They help regain access to the workspace if it is lost.

Beneficiary is a designated recipient of the workspace assets in the event of the owner's passing or incapacitation. Beneficiaries are configured as part of the inheritance setup — see Inheritance for details.

2. Security Policies And Change Review

Security policies let you control how sensitive workspace changes are handled — whether they require team approval or a waiting period before taking effect. This is your main safeguard against unauthorized modifications to critical settings.

You can apply protection to three types of actions: changes to transaction limits, changes to the address book, and changes to team membership. Each can be individually configured.

2.1 How To Configure

Go to Settings → Security Policies and enable the Security Protection Policy. Once enabled, select your preferred protection method (Security Delay or Member Approval) and toggle on the specific actions you want to protect.

2.2 Protection Methods

There are two ways to protect these actions:

Security Delay holds a change for 48 hours before it takes effect, giving the team time to notice and respond if something looks wrong. This is available on all plans.

Member Approval requires a designated team member to explicitly approve the change before it is applied. This is available on the Enterprise plan only ($2,000/mo or 1M BRON).

💡 Member approval — available on Enterprise plan only ($2,000/mo or 1M BRON)

The selected protection method will be applied to the policies you enable.

2.3 Protected Actions under Policies

You can apply protection to the following actions:

  • Transaction limits changed

  • Address book changed

  • Team members changed

Each of these can be individually configured to require a security delay or approval.

3. Withdrawal Settings

In addition to policy-based protections, you can restrict where and how funds leave your workspace.

Address Book Lock means funds can only be withdrawn to addresses that have been pre-approved in your address book — any other destination will be blocked.

New Address Withdrawal Lock prevents withdrawals to newly added addresses for 48 hours, giving the team time to review before funds can move.

API Key Creation Control lets you restrict who can create new API keys, reducing the risk of unauthorized programmatic access.

Bron Tag Search Visibility controls whether other users can find your workspace by searching its tag.

These settings are especially useful for preventing unauthorized withdrawals and protecting against social engineering attacks.

Transaction limits let you define rules for when additional controls — such as approval or a delay — are required before a transaction executes. They don't block activity outright; they add a layer of review when transactions meet certain thresholds or conditions.

You can configure limits by amount, transaction type (single or cumulative), source accounts, destination type (address book, external address, or internal account), and which team members the rule applies to. Swaps and DeFi interactions (via WalletConnect) can be excluded from limits if needed.

For full details on setting up and managing transaction limits, see Transaction Limits

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

Did this answer your question?