> For the complete documentation index, see [llms.txt](https://docs.brahma.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brahma.fi/brahma-accounts/brahma-pro/converting-your-account-to-pro.md).

# Converting your account to Pro

> Upgrading to Brahma pro unlocks advanced features tailored for power users, teams, and those looking for more control over their onchain activities. Before proceeding, here’s everything you need to know about the conversion process.

## Important Note: Permanent Upgrade

The upgrade to Brahma pro is a **one-time, irreversible change**. Once you convert, your account cannot revert to the standard version. Carefully consider whether Brahma pro’s features align with your needs before upgrading.

#### Why Upgrade to Brahma pro?

**Brahma pro** offers advanced functionality, ideal for users who need added flexibility, security, and control. Key features include:

* **Multi-Owner and Multi-Signature Support**: Add multiple owners and set signature thresholds for enhanced security. This is especially useful for shared accounts or users looking for extra security.
* **Sub-Accounts and Transaction Policies**: Organise and manage separate sub-accounts, allowing you to structure your operations into distinct “buckets.” Each sub-account can have specific permissions and transaction policies, perfect for teams or users managing multiple DeFi strategies.
* **Custom Transaction Builder**: Directly interact with any smart contract by creating custom transactions using contract ABIs. This feature is valuable for advanced DeFi operations, providing full control over contract interactions.

## Who Should Consider Upgrading?

* **Advanced Individual Users**: If you’re an individual seeking additional security (e.g., multi-signature support) or need to manage complex workflows (e.g., multiple sub-accounts), Brahma pro offers the tools for streamlined management.
* **Teams and Organisations**: Brahma pro is ideal for teams like protocol treasuries, asset managers, and other teams that need multi-user access and structured permissions.

## Can I Use Both Brahma and Brahma pro?

Yes! You can create multipleaccount. This allows you to maintain both a standard account for simpler transactions and a **Brahma pro** for more advanced use cases. You can switch between them as needed, giving you flexibility in how you manage different types of operations.

How to Upgrade

1. Go to the **Settings** page in your account.

<figure><img src="/files/wSwTReIINJriQTh87PPG" alt=""><figcaption></figcaption></figure>

2. Under **Brahma pro**, click on **Convert to Brahma pro**.
3. Confirm the conversion when prompted. Remember, this is a permanent upgrade.

***

#### **Learn More About Brahma Pro**

Before making the switch, review the full list of Console Pro features and considerations:

{% content-ref url="/pages/vYCcbaobcGc5JvEJ5tJI" %}
[Which Account Version Is Right for You?](/brahma-accounts/which-account-version-is-right-for-you.md)
{% endcontent-ref %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.brahma.fi/brahma-accounts/brahma-pro/converting-your-account-to-pro.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.