Brahma Docs
Access Console
  • Brahma Overview
  • Brahma Accounts
    • Key benefits
    • Which Account Version Is Right for You?
    • Understanding the dashboard
    • Brahma
      • Onboarding to Brahma
      • In-App Features
        • Swapping
        • Bridging
        • Lending
      • Multichain
      • Transacting in Brahma
        • Transaction Builder
        • Smart Execution
      • Connecting to Onchain Applications
        • Brahma Connect
        • Wallet Connect
      • Portfolio Management
        • Unified History
        • Positions
    • Brahma Pro
      • Converting your account to Pro
      • Onboarding to Brahma Pro
      • In-App Features
        • Swapping
        • Bridging
        • Lending
      • Multichain
      • Transacting in Brahma pro
        • Transaction Builder
        • Smart Execution
      • Connecting to Onchain Applications
        • Brahma Connect
        • Wallet Connect
      • Portfolio Management
        • Unified History
        • Positions
      • Team Management & Access Control
        • Inviting Operator & Role Management
        • Sub-Accounts
        • Policies
          • Types of Policies
      • Custom Transaction Builder
    • Brahma | Strategies
      • Automations
        • TWAP | DCA Automation
        • Morpho Yield Optimizer
        • Infrared iBGT Automation
        • BGT Automation
        • Berabaddies AutoBGT
      • Templates
        • Morpho Earn
  • Brahma ConsoleKit
    • API Reference
  • Rewards
    • Brahma Rewards
      • Brahma Imprint NFT
      • Karma & Levels | SNAPSHOTED
  • Brahma Agents | Built with Console kit
    • Surge & Purge Agent
    • 🦋Morpho Agent
  • FAQs
    • Brahma Imprint NFT | FAQs
    • Brahma & Brahma Pro FAQs
    • Brahma Connect FAQs
  • Others
    • Security Audits
    • Pricing & Fees
    • Risks
      • Counterparty Risk
      • Other Risks
    • Error Codes
  • Change log
  • Github
  • Discord
  • Press Kit
  • Developer
    • Deployed Contracts: Console
    • Brahma Console Integration [for dApp developers]
Powered by GitBook
On this page
  • A. Global Policy
  • B. Protocol Policy
  • C. Granular Transfer Policies
  1. Brahma Accounts
  2. Brahma Pro
  3. Team Management & Access Control
  4. Policies

Types of Policies

PreviousPoliciesNextCustom Transaction Builder

Last updated 5 months ago

Through the smart contracts, access permissions are programmatically managed and enforced, ensuring that only authorised operators can engage in specific transactions or operations. Brahma enables various Access Control parameters through Policies to ensure optimal transparency and delegation outlets.

Our Policies employ a quantitative approach to assess user’s eligibility, taking into consideration factors such as assigned actions within your account, transaction history, and adherence to protocol governance rules.

A. Global Policy

The Brahma Global Policy is a series of policies restricting contract interactions, creating a controlled "Walled Garden"where transactions can only have a specific set of recipients.

Account admins can activate Global Policy to allow precise protocol interactions, and set overarching asset policies and granular transfer policies, ensuring compliance. This approach mitigates numerous risks and fosters a secure environment for authorised transactions, reinforcing transparency within all overlapping policy frameworks.

  1. Asset Policy

  2. Transfer Recipients

Asset policies within Sub-Accounts create a resilient framework that not only protects assets from contract vulnerabilities but also ensures a strategic and controlled approach to fund management, thereby enhancing the overall operational integrity of the Sub-Account.

Admin can assign transaction limits on selected assets with a maximal outgoing limit in a given time frame. This ensures that assigned operators are in a controlled transaction environment.

To limit transactions on specific assets, the admin can also place restrictions by barring the asset from the whitelist.

B. Protocol Policy

The Interaction Policy regulates system interactions by whitelisting approved protocols and custom contracts. External protocol interactions are restricted by default to enhance security and prevent unauthorised third-party access. The policy acts as a contract gatekeeper, ensuring adherence to predefined parameters and safeguarding overall system integrity.

Admins can pre-verify and whitelist certain protocols and define contract functions for operation within the Sub-Account.

C. Granular Transfer Policies

Granular Transfer policies upkeep transfer limits within the Sub-Account

As an admin, transfer funds, monitor ownership transactions, and employ kill-switches with a streamlined emergency protocol.