Sub-Accounts can be used to manage different investment portfolios within the single overarching Main Console Account, allowing owners and operators in teams or individually to segregate and track the performance of automations and strategies including:
Trading Strategies: users can leverage Sub-Accounts to implement different trading strategies, including position management, LPing across assets or reward harvesting. Trading teams can isolate funds for distinct strategies, minimising their risk and optimising portfolio management.
Automated Transactions: Sub-Accounts can be deployed to automate specific transactions, such as setting up recurring asset purchases (DCA) and triggered auto-exits (TWAP or limit orders). More on upcoming Console Automation possibilities here.
Risk Management: Sub-Accounts are designated to cater for different risk profiles and purposes within asset management teams, based on the client’s risk and reward appetite. This aids in risk management and prevents unintended financial exposure while managing funds through Console.
Customised Access: Sub-Accounts can have different levels of access and permissions within teams. In fact, different users and teams might need different degrees of control or visibility.. For instance, a primary account owner could delegate fund management responsibilities to specific Sub-Account operators with restricted access to managing positions.
Console Owners maintain uninterrupted access to their Safe Wallet and can deploy Sub-Accounts or Safe via https://safe.global or by interacting directly with Safe contracts. Operator roles only retain access to assigned Sub-Accounts and do not have access to Main Console as per granular policy parameters. At any time Console does not have direct access to deployed accounts.