> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/user-guides/management-dashboard/extensions.md).

# Extensions

Create and add a custom MD extension.

### Extending Management Dashboard

The Management Dashboard allows you to connect external custom modules and embed them into the application. This way, you have everything at hand in a single place.

The **Extensions** module is the place where you can see all your embedded custom extensions and use them directly from the Management Dashboard.

{% hint style="warning" %}
This node is visible **only** when you have enabled some custom extensions. Otherwise, the Extensions node doesn't appear in the Management Dashboard.
{% endhint %}

As a prerequisite for the extensions, connect a custom module and have it available in Management Dashboard. For the configuration details, see:

* [Extensions](/user-guides/management-dashboard/administration/extensions.md) guide in the administration section that shows how to create a connection.
* [Enabling Custom Extensions](/user-guides/extensibility-and-integrations/extensibility-cases/custom-extensions.md) guide that shows how to create a connection, with an example use case.


---

# 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://developer.emporix.io/user-guides/management-dashboard/extensions.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.