# Acquiring an enterprise user role

{% hint style="warning" %}
Before continuing with this section, please ensure that an [EWC Account](/energy-solutions/digital-spine-by-energy-web/component-guides/ddhub-client-gateway/deployment-guide/preparing-to-set-up-a-client-gateway/creating-and-funding-an-ewc-account.md) has been prepared and that it has enough [EWT to fund](/energy-solutions/digital-spine-by-energy-web/component-guides/ddhub-client-gateway/deployment-guide/preparing-to-set-up-a-client-gateway/creating-and-funding-an-ewc-account.md#funding-an-ewc-account) the on-chain transactions.
{% endhint %}

It is important to identify in advance which roles are actually required when setting-up the DDHub Client GW.

<figure><img src="/files/7lu6yHLMkANdy7IPVx2u" alt="" width="563"><figcaption><p>Enterprise User Role Categories</p></figcaption></figure>

There will be two (2) enterprise user role categories to keep in mind:

1. DDHub Message Broker Role
2. Application-level Enterprise User Role

## DDHub Message Broker Role

In order to gain basic access to the DDHub Message Broker, the following roles are needed:

* `user.roles.mb.apps.ddhub.energyweb.auth.ewc` - basic role requirement in order to gain access to the message broker
* `topiccreator.roles.mb.apps.ddhub.energyweb.auth.ewc` - *<mark style="color:purple;">optional</mark>* role in order to gain write access to the topic management APIs of the message broker

## Application-level Enterprise User Role

{% hint style="info" %}
The enterprise user must acquire first the DDHub Message Broker role for these application-level enterprise user roles to take effect in the Digital Spine ecosystem.
{% endhint %}

Application-level enterprise user roles are necessary to gain access to the data schemas of the target applications or projects. These roles must be identified in advance and must be created by the application or project owner/s.

Please refer to [ENS in Digital Spine Ecosystem](/energy-solutions/digital-spine-by-energy-web/component-guides/energy-web-name-service-ens/ens-in-digital-spine-ecosystem.md#enterprise-namespaces) for more details on the creation of these roles.

## Acquiring enterprise user roles

To acquire enterprise user roles, there are two (2) options available:

1. [Request via DDHub Client GW UI using the Role Management module](/energy-solutions/digital-spine-by-energy-web/component-guides/ddhub-client-gateway/deployment-guide/preparing-to-set-up-a-client-gateway/acquiring-an-enterprise-user-role/request-role-using-ddhub-client-gateway-ui.md)
2. [Request via Switchboard](/energy-solutions/digital-spine-by-energy-web/component-guides/ddhub-client-gateway/deployment-guide/preparing-to-set-up-a-client-gateway/acquiring-an-enterprise-user-role/request-role-using-switchboard.md)

{% hint style="success" %}
For DDHub Message Broker `user` role, the DDHub Client GW Admin can request it right [after setting-up the private key](/energy-solutions/digital-spine-by-energy-web/component-guides/ddhub-client-gateway/deployment-guide/preparing-to-set-up-a-client-gateway/acquiring-an-enterprise-user-role/request-user-role-after-setting-up-the-private-key.md) using the DDHub Client GW UI.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs-launchpad.energyweb.org/energy-solutions/digital-spine-by-energy-web/component-guides/ddhub-client-gateway/deployment-guide/preparing-to-set-up-a-client-gateway/acquiring-an-enterprise-user-role.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.