Brahma Console offers two primary methods of authentication to ensure secure access and protect sensitive user information like address books and account data.

By default, the Console requires off-chain, gasless wallet signatures for authentication. This method verifies that the person attempting to access the Console is the legitimate owner of the connected wallet. It's crucial for maintaining the integrity of the user's data and preventing unauthorized access.

To provide a smoother experience, especially for users of MPC wallets where a single EOA key is split into multiple fragments, Brahma Console introduces password authentication. This method reduces friction for users who might otherwise need to provide multiple signatures.

Users have the flexibility to enable password authentication during the initial Console setup or at any point afterward. To set or update a password, navigate to the authentication settings located in the Console's settings page or use the signature icon button in the top right menu bar. A wallet signature from the owner’s wallet will be required to save, change, or disable the password to confirm the changes securely.

At any point, Console users retain the option to revert to using wallet signatures as an alternative authentication method, ensuring flexibility and control over their security preferences.

For teams onboarding onto the Console, the first owner to set up the Console has the option to establish a password as the authentication method. Subsequent owners of a multi-sig console can independently manage their authentication preferences from the settings page, enabling a password for their accounts at their convenience.

This dual authentication approach caters to various user needs, balancing security with ease of use, and affirms Brahma Console's commitment to providing a user-centric platform.