DOCTYPE html>
Fireblocks Wallet Extension Installation and DApp Account Recovery Steps

Install the browser add-on directly from the Chrome Web Store or Firefox Add-ons marketplace; verify the developer's name matches the official provider to avoid counterfeit software. This initial step establishes a protected gateway for managing your digital holdings and interacting with decentralized applications.
Configuration requires linking the tool to your institutional vault. You will need your API credentials, which consist of a private key, API key, and the URL for your specific workspace. These three elements, entered into the add-on's settings, create a secure, authenticated connection without exposing sensitive data to your browser's memory.
For accessing a smart contract-based application, the process involves specific approval flows. After initiating a transaction within the app, the add-on will present a detailed request. This must be reviewed and authorized by the designated number of transaction approvers within your organization's policy, ensuring no single point of failure.
Should you encounter a lost connection or need to re-establish access from a new device, your recovery path relies on your corporate credentials. Log into the main platform dashboard, regenerate new API keys if necessary, and repeat the initial pairing steps with the fresh credentials. Your asset permissions and policies remain intact, governed by the institutional framework.
Fireblocks Wallet Extension Setup and DApp Recovery Guide

Install the browser add-on exclusively from the official Chrome Web Store or Firefox Add-ons portal. After adding it, initiate the connection process by selecting your organization and signing in with your corporate credentials. This step authorizes the plugin to communicate with your institutional vault, establishing a secure bridge for transaction signing without direct private key exposure on your machine.
For re-establishing access to decentralized applications, your vault's policy engine is central. If a connected application disappears, re-authenticate by navigating to the desired DApp and selecting the institutional tool from your browser's menu. The system will request approvals according to pre-defined governance rules–often requiring multiple team members to confirm via mobile devices. Ensure your transaction policies are configured for the specific application's contract addresses to prevent unnecessary rejections during this re-linking phase.

• Confirm MPC key shares are distributed and accessible to designated approvers.
• Pre-whitelist frequently used smart contract addresses in your workspace policy to streamline future interactions.
• If authentication loops occur, clear the browser's local storage for the DApp's site and restart the connection flow from the plugin's interface.

Installing the Extension and Connecting Your First Vault

Navigate directly to the Chrome Web Store and search for the official tool by name.
Click 'Add to Chrome' and confirm the installation; the icon will appear in your browser's toolbar within seconds.
Authenticate using your existing enterprise account credentials or a registered hardware authentication device–this step is mandatory and non-negotiable for security policy enforcement.
Post-authentication, the interface presents your institutional vault structure. Select the specific vault and asset account you intend to use for transactions. This choice dictates transaction signing policies; a development vault often has lower approval thresholds than a production treasury vault.
Confirm the connection within your browser when a decentralized application requests access, ensuring you grant permissions only to the specific vault account selected, not your entire organization's hierarchy.
Your vault is now active for browser-based interactions.
FAQ:

I installed the Fireblocks wallet extension but can't connect it to my Fireblocks account. What am I doing wrong?

The most common issue is attempting to use the browser extension alone. The Fireblocks extension is not a standalone wallet; it's a connector for the Fireblocks web platform. To set it up correctly, first log into your Fireblocks account on the web platform (app.fireblocks.io). Once logged in, navigate to the 'Settings' and then 'Browser Extension' section. There, you will find specific instructions to link your extension, which usually involves confirming a connection request. The extension must be authenticated through your main web account to gain access to your vaults and policies.
Can I recover access to my decentralized applications (dApps) and connected sites if I switch browsers or computers?

Yes, your dApp connections and permissions are managed through your Fireblocks organization's policies and user permissions, not stored locally on a single browser. When you set up the Fireblocks extension on a new browser or device, you first authenticate it with your main Fireblocks web account. After authentication, the extension will have access to the same vaults and wallets defined by your user role. You will need to manually reconnect to each dApp (like a DeFi protocol or NFT marketplace) by visiting the site and initiating a wallet connection, selecting the Fireblocks extension. Your transaction policies and approvals remain intact as they are server-side settings.
What's the difference between the Fireblocks browser extension and a regular MetaMask-style extension?

The core difference is custody and transaction governance. MetaMask is a self-custody software wallet where you alone control the private keys. The Fireblocks extension is an interface for an institutional-grade, policy-controlled custody platform. You do not hold the private keys directly; they are secured by Fireblocks' infrastructure. Every transaction you initiate via the extension must comply with pre-defined approval policies set by your organization (e.g., requiring 2-of-3 admins to approve). It's designed for teams and businesses, not individual retail users. The extension lets you interact with dApps while maintaining enterprise security and workflow controls.
If I lose my laptop, is there a risk someone could use my installed Fireblocks extension to move funds?

No, there is minimal risk if your laptop is lost or stolen. The Fireblocks extension itself does not store login credentials or private keys. Access requires authentication via the main Fireblocks web platform, which is protected by your login (email/password) and likely multi-factor authentication (MFA). An attacker with physical access to your computer would still need to bypass these primary login barriers. Additionally, even if they accessed your account, all transactions would be blocked by your organization's transaction policy, which would require additional approvals from other designated users, preventing unilateral fund movement.
How do I manage which wallets or vaults are visible and usable within the browser extension when connecting to a dApp?

Wallet visibility is controlled from the Fireblocks web console, not the extension. An administrator in your organization can assign specific vaults and asset wallets to your user account. When you connect the Fireblocks extension to a dApp and click to select an account, you will only see the wallets you have been granted permission to use. To change which wallets are available, an admin must adjust your user permissions in the 'Users' section of the web console, assigning the relevant vaults. You cannot add or remove wallets from the extension interface itself; it reflects the permissions set at the organizational level.
I installed the Fireblocks browser extension, but my existing dapps don't recognize it as a connected wallet. How do I fix this?

This is a common issue. The Fireblocks extension operates differently from standard personal wallets like MetaMask because it connects to your institutional Fireblocks account. To resolve it, first ensure you are fully logged into the extension with your Fireblocks credentials. Then, visit the dapp you want to use. Instead of the dapp automatically detecting the wallet, you must manually connect it. Look for a "Connect Wallet" button on the dapp's website. Click it and select "Fireblocks" or "WalletConnect" from the list of wallet options. A connection request will appear in your Fireblocks extension pop-up for you to approve. Once approved, the dapp will have access to the vaults and addresses associated with your Fireblocks account. You may need to repeat this process for each separate dapp.
If my computer crashes and I need to set up the Fireblocks extension on a new machine, what steps are required to recover my access and dapp connections?

Recovery is straightforward because your assets and access policies are managed on the Fireblocks platform, not locally on your device. On your new computer, simply install the Fireblocks browser extension from the official Chrome Web Store or Firefox Add-ons site. When you open it, log in using your Fireblocks email and password. You will then need to complete your configured multi-factor authentication steps, which could involve approving the login via a mobile authenticator app or a hardware device. After authentication, your extension will sync with your Fireblocks account, displaying all your assigned vaults and addresses. Your dapp connections, however, are not stored in the extension. You will need to revisit each decentralized application and use the "Connect Wallet" process again, selecting Fireblocks and approving the connection. Your transaction approval workflows and policy rules remain intact as they are set on the Fireblocks backend.