1. After receiving your invitation, follow the user setup guide to access your Fireblocks workspace and complete the registration process. Note that your Fireblocks Console sessions will timeout after one hour of inactivity, and you will be automatically logged out. This one-hour timeout period is fixed, so you cannot request to change it.
2. Review the available user roles for your workspace.
3. Add Console users .
4. Create vault accounts and asset wallets  to form a Sweep-to-Omnibus Vault structure. This structure uses vault accounts for each end client and a central vault account where funds are swept.
   • You can quickly set up vault accounts for a large number of clients and automate the movement of funds when receiving deposits from customers.
   • Example
5. Connect your exchange accounts and fiat accounts .
   • Review our supported exchange integrations.
6. Connect to counterparties using whitelisted addresses  and the Fireblocks Network .
7. Learn how to withdraw and deposit assets .
8. Learn how to track incoming transactions using the List Transactions API call or webhooks.
9. Update the Admin Quorum  to your preferences.

1. Read the REST API developer guide to learn more about available endpoints and view code examples.
2. Add API users.
3. Set up your API Co-Signer so you can automate transaction signing and approvals for workspace changes.
4. Configure a server for your API Co-Signer.
5. Determine your preferred transaction flow. You can initiate or sign transactions with your API using one of the following transaction flows:
   • In a semi-automated transaction flow, an API user (Editor or Non-Signing Admin) initiates transactions, and a Fireblocks Console user signs the transaction with their mobile device.
   • In a fully automated transaction flow, an API user (Signer or Admin) initiates transactions, and the API co-signer automatically signs the transaction. There are two setups for a fully automated transaction flow:
     1. Simple setup (usually for testing): One API user (Signer or Admin) is used to initiate transactions and connect to your API Co-Signer.
     2. Production setup (recommended for mainnet usage): One API user (Editor) initiates transactions and a second API user (Signer or Admin) is deployed on your API Co-Signer machine (secured within the SGX enclave) for signing transactions.
6. If needed, set up additional API users for actions other than initiating or signing transactions.
   • API users with the Approver role can approve certain transactions according to the Transaction Authorization Policy (TAP) as part of a 2-tier approval process.
   • API users with the Viewer role have read-only access to the workspace, can audit workspace activity and transaction logs, and receive webhook events.
7. Follow these API best practices:
   
   • Use the idempotency key and externalTxId paremeter appropriately.
   • Configure webhook URLs.
   • Whitelist IP addresses for your API users.
   • Complete this Typeform to receive all Fireblocks API updates.

1. Review the following articles about the Transaction Authorization Policy (TAP):
   
   • About the TAP
     • Includes the Intro to TAP video
   • Building your TAP
     
     • Includes the Publish Your TAP video
   • Rule parameters
   • TAP examples
   • TAP best practices
   • User group management and best practices
   • Transactions not covered by TAP
2. Build and publish your TAP.
3. After you receive confirmation that your workspace Owner and Admin Quorum have approved your TAP, test the transaction policies by withdrawing funds.

1. Learn about accessing Web3 applications using Fireblocks.
2. Review the Fireblocks Smart Contract API for Web3 operations.
3. Set up your Web3 connections using WalletConnect, the Fireblocks Chrome Extension, or MetaMask Institutional. 
4. Learn more about NFT support on Fireblocks.
5. Apply an amount cap on contract calls.
6. Review the DeFi security best practices article.
7. Make sure your TAP accommodates Web3 and Decentralized Finance (DeFi).
   • Example

1. Enable the One-Time Address feature, then send transactions to one-time addresses using the Create a transaction endpoint.
2. Enable the AML feature for transaction screening and monitoring.
3. Enable the Gas Station feature.

1. Learn about your backup and recovery options.
2. Complete the Key Share Backup for your mobile key shares. Your mobile device stores your MPC key share used for signing transactions.
3. Complete the Workspace Keys Backup. This process can be completed using a self-serve option or a third-party Disaster Recover Service (DRS).
4. If you completed the Workspace Keys Backup using the self-serve option, learn how to load your private keys to third-party wallets. Recovery is only necessary in the event of a disaster.

You must complete both Key Share Backup and Workspace Keys Backup before receiving funds into your Fireblocks Vault.

1. After receiving your invitation, follow the user setup guide to access your Fireblocks workspace and complete the registration process. Note that your Fireblocks Console sessions will timeout after one hour of inactivity, and you will be automatically logged out. This one-hour timeout period is fixed, so you cannot request to change it.
2. Review the available user roles for your workspace.
3. Add Console users .
4. Create vault accounts and asset wallets to form a Segregated structure. With this structure, assets are stored in individual vault accounts until the end client requests to withdraw funds.
   • You may find this useful for rehypothecating funds in your custody. This structure can also be useful for internal treasury purposes.
5. Set up wallet addresses for the native tokens and ERC-20 assets you intend to custody.
6. Connect your exchange accounts and fiat accounts .
   • Review our supported exchange integrations.
7. Connect to counterparties using whitelisted addresses and the Fireblocks Network .
8. Learn how to withdraw and deposit assets .
9. Learn how to track incoming transactions using List Transactions API call or webhooks.
10. Update the Admin Quorum to your preferences.

1. Review the following articles about the Transaction Authorization Policy (TAP):
   
   • About the TAP
     • Includes the Intro to TAP video
   • Building your TAP
     
     • Includes the Publish Your TAP video
   • Rule parameters
   • TAP examples
   • TAP best practices
   • User group management and best practices
   • Transactions not covered by TAP
2. Build and publish your TAP.
3. After you receive confirmation that your workspace Owner and Admin Quorum have approved your TAP, test the transaction policies by withdrawing funds.

1. Learn about accessing Web3 applications using Fireblocks.
2. Review the Fireblocks Smart Contract API for Web3 operations.
3. Set up your Web3 connections using WalletConnect, the Fireblocks Chrome Extension, or MetaMask Institutional.
4. Learn more about NFT support on Fireblocks.
5. Apply an amount cap on contract calls.
6. Review the DeFi security best practices article.
7. Make sure your TAP accommodates Web3 and Decentralized Finance (DeFi).
   • Example

1. Enable the One-Time Address feature, then send transactions to one-time addresses using the Create a transaction endpoint.
2. Enable the AML feature for transaction screening and monitoring.
3. Enable the Gas Station feature.

1. Learn about your backup and recovery options.
2. Complete the Key Share Backup for your mobile key shares. Your mobile device stores your MPC key share used for signing transactions.
3. Complete the Workspace Keys Backup. This process can be completed using a self-serve option or a third-party Disaster Recover Service (DRS).
4. If you completed the Workspace Keys Backup using the self-serve option, learn how to load your private keys to third-party wallets. Recovery is only necessary in the event of a disaster.

You must complete both Key Share Backup and Workspace Keys Backup before receiving funds into your Fireblocks Vault.

1. After receiving your invitation, follow the user setup guide to access your Fireblocks workspace and complete the registration process. Note that your Fireblocks Console sessions will timeout after one hour of inactivity, and you will be automatically logged out. This one-hour timeout period is fixed, so you cannot request to change it.
2. Review the available user roles for your workspace.
3. Add Console users .
4. Create vault accounts and asset wallets to form a Segregated structure. With this structure, assets are stored in individual vault accounts until the end client requests to withdraw funds.
   
   • This structure allows you to separate proprietary assets from your customer assets. Further, you can create vault accounts for separating assets into additional classes, such as vault accounts for each portfolio manager, for withdrawals or deposits, or per corporate client.
5. Connect your exchange accounts and fiat accounts .
   • Review our supported exchange integrations.
6. Connect to counterparties using whitelisted addresses and the Fireblocks Network .
7. Learn how to withdraw and deposit assets .
8. Learn how to track incoming transactions using List Transactions API call or webhooks.
9. Update the Admin Quorum to your preferences.

1. Review the following articles about the Transaction Authorization Policy (TAP):
   
   • About the TAP
     • Includes the Intro to TAP video
   • Building your TAP
     
     • Includes the Publish Your TAP video
   • Rule parameters
   • TAP examples
   • TAP best practices
   • User group management and best practices
   • Transactions not covered by TAP
2. Build and publish your TAP.
3. After you receive confirmation that your workspace Owner and Admin Quorum have approved your TAP, test the transaction policies by withdrawing funds.

1. Learn about accessing Web3 applications using Fireblocks.
2. Review the Fireblocks Smart Contract API for Web3 operations.
3. Set up your Web3 connections using WalletConnect, the Fireblocks Chrome Extension, or MetaMask Institutional.
4. Learn more about NFT support on Fireblocks.
5. Start staking assets.
6. Apply an amount cap on contract calls.
7. Review the DeFi security best practices article.
8. Make sure your TAP accommodates Web3 and Decentralized Finance (DeFi).
   • Example

1. Enable the One-Time Address feature, then send transactions to one-time addresses using the Create a transaction endpoint.
2. Enable the AML feature for transaction screening and monitoring.
3. Enable the Gas Station feature.

1. Learn about your backup and recovery options.
2. Complete the Key Share Backup for your mobile key shares. Your mobile device stores your MPC key share used for signing transactions.
3. Complete the Workspace Keys Backup. This process can be completed using a self-serve option or a third-party Disaster Recover Service (DRS).
4. If you completed the Workspace Keys Backup using the self-serve option, learn how to load your private keys to third-party wallets. Recovery is only necessary in the event of a disaster.

You must complete both Key Share Backup and Workspace Keys Backup before receiving funds into your Fireblocks Vault.