> For the complete documentation index, see [llms.txt](https://support-en.braver.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support-en.braver.net/guides/integrations/leomed/deploy-braver-via-leomed-platform.md).

# Deploy Braver via Leomed

Configure your organization in just 3 steps!

{% hint style="info" %}
The process typically involves creating a pre-production environment and then a production environment. The first step is required only once, as we will use the same information.

**The other two steps will need to be repeated for both environments.**
{% endhint %}

### Here are the steps to configure your organization in Braver:

{% stepper %}
{% step %}
**Share your organization's information with Braver team**

Complete the form below:

{% embed url="<https://braverhealth.typeform.com/to/xuw0zj3i>" %}
{% endstep %}

{% step %}
**Access administrative application**

{% hint style="warning" %}
Before proceeding with this step, you must wait for a member of Gustav or Braver team to confirm that the integration is functional.

Subsequently, if you have not yet created your account, you should have received an email invitation. Here is [the tutorial](/guides/for-healthcare-professionals/account-creation/independent-account-creation.md) to help you create your account.
{% endhint %}

You can access the administrative application via [https://admin.braver.net](https://admin.braver.net/#/login). Use the same information you use to log into your Braver account (email + password)
{% endstep %}

{% step %}
**Grant "Admin" role to the right people**

Here is [how to grant a role to an existing user.](/guides/for-administrators/users/how-to-grant-role-to-existing-user.md)

{% hint style="info" %}
When activating Braver user accounts, the Leomed platform provides Braver with all roles and permissions except the "Admin" role. This role must therefore be manually granted in Braver's administrative application.

The Admin role gives a user permission to log into the administrative application and thus create workplaces, teams, and invite users. However, since you are using Braver via an integration with Leomed, all these actions are facilitated for you by the integration between the two platforms.
{% endhint %}

The most useful functionality in Braver's administrative application will be **the audit log**. Here is [how to search in the audit log](/guides/for-administrators/audit-logs/how-to-search-in-audit-logs.md).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
For inviting patients and caregivers, this is done through Leomed. Here is [the tutorial](/guides/integrations/leomed/activate-patient-or-caregiver-account.md) to guide you.
{% endhint %}

{% hint style="success" %}
**Congratulations, your organization is now part of the Braver network!** 🎉

Only two sections remain to be reviewed:

* [Patient and Caregiver Module](/guides/for-administrators/configuration-guide.md)
* [Other Technical Details](/guides/for-administrators/configuration-guide.md)
  {% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support-en.braver.net/guides/integrations/leomed/deploy-braver-via-leomed-platform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.