Unapproved or unauthorised changes to your workspace settings by other users can lead to a loss of control over your account or funds. To prevent this, Bron allows you to enable review policies for the following critical actions:
Approve transactions: Set flexible thresholds for outgoing transfers.
Approve transaction limit changes: Review any updates to transaction policy settings.
Approve address book changes: Review the addition of new addresses, renaming, or deletion of existing ones in the Address book.
Approve team member changes: Review the addition of new users, as well as any changes or deactivation of existing team members.
Approve workspace settings changes: Review any modifications to the review policies themselves.
Security delay for sensitive changes
For your safety, certain workspace and security settings are protected by a 48-hour security delay.
When this feature is enabled, any change to the settings listed below will not take effect immediately. Instead, the change is placed on hold and will be executed automatically after 48 hours. This gives you time to review the request and cancel it if the change was not intended.
Changes that trigger a 48-hour security delay
The security delay applies when you attempt to change any of the following:
Transaction limits
Address book settings (including address book lock)
Team members
Workspace settings
Approval and permission settings
For example, if you decide to change transaction limits in the future, the update will trigger a 48-hour security delay before becoming active. The same delay applies if you try to disable this security feature itself.
Where to enable this feature
The security delay can be enabled or managed from:
Workspace → Settings → Security
We strongly recommend keeping this feature enabled to protect your workspace from unauthorized or accidental changes.
How the Approval Process Works
When approval is enabled for any of these actions, changes require approval or rejection by another workspace user with the appropriate approval permissions before they take effect.
Example: Changing a Team Member’s Role
Enable Approvals: The workspace must have "Approve team member changes" enabled.
Request Change: Team Member 1 attempts to change another member’s role from Member to Owner. This creates a pending change request, but the change does not take effect immediately.
Review Request: Team Member 2 opens the team members page and sees the pending request. A popup displays the details of the requested change. Team Member 2 can either approve or reject the request.
If approved, the new privileges take effect immediately.
If rejected, the user’s permissions remain unchanged.
Note: Any other team member with the appropriate permissions can review and approve (or reject) the change.
Additional Details
No Expiry: Requests don’t expire. The creator can cancel them at any time.
Security: This process adds an extra layer of protection, ensuring no single user can make critical changes unchecked.
Single-owner workspaces
If your workspace has only one user with the Owner role, and that user makes changes that decrease security — for example, disabling approval processes or the address book lock — a 48-hours security delay will be activated. This delay postpones the application of such changes until the delay period finishes, providing additional protection from unapproved or accidental reductions in security settings.
If you have questions, contact our support team via messenger on the Bron platform or by email support@bron.org.