When you manage a wallet on your own, your main concern is protecting it from compromise — for example, through hacking or loss of credentials.
But when you manage digital assets as a team, you need more than that. You need a system that defines roles, controls actions, and ensures no single person can put your funds at risk.
That’s why Bron provides one of the most sophisticated policy engines in the digital asset space today — potentially offering more flexibility than most traditional bank accounts. Let’s explore the key features and how they can help you.
1. Team Access Levels
At the first layer of control, you can invite teammates to your workspace and define their access level:
Owner — full permissions across all workspace functions.
Member — cannot manage the team, but can perform operational tasks.
Viewer — read-only access.
Guardians — trusted contacts who help you regain access if you ever lose it.
2. Approval for Critical Changes
Next, you can define how global security settings apply to your workspace:
Apply changes immediately
Or require review and approval before changes take effect
If you choose the approval route, you decide which actions are considered critical and who must approve them.
This protects your setup from scenarios where an attacker might try to weaken your security — for example, by lowering limits or removing safeguards. Approval flows help distribute control across your team to reduce risks.
You can enable approval requirements for:
Transaction limit updates (adding or changing limits)
Address book updates (adding new addresses or editing existing ones)
Team changes (inviting new members or changing permissions)
Workspace security settings updates
3. Withdrawal Locks
Bron allows you to restrict where withdrawals can be sent.
When address book lock is enabled, funds can only be withdrawn to addresses that were pre-approved and saved in the address book. There’s no way to send funds outside of this safe list.
Finally, the Policy Engine lets you define flexible rules for transaction execution.
Limits don’t block transactions outright — they define thresholds that require additional approvals before a transaction can proceed.
You can configure rules based on:
Single transaction amount
Cumulative transaction volume over a set period
Source account
Destination address
Transaction author
Number of required approvals
Specific users to whom the limit applies
These controls help secure your operations both in daily activity and in emergency situations — ensuring that no transaction happens without the right oversight.
If you have questions, contact our support team via messenger on the Bron platform or by email support@bron.org.