> 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/oe-user-guides/management-dashboard/accessing-oe.md).

# Accessing OE

Orchestration Engine is available as a module in the Management Dashboard.

{% hint style="danger" %}
The Orchestration Engine module will be **removed from the Management Dashboard at the end of 2026**. The Orchestration Engine will remain available in the backend. Only its Management Dashboard representation is being discontinued. Its functionality is now fully available in [Value Stream Modeller](https://developer.emporix.io/vsm-guides/) — use the VSM documentation for current user guidance.
{% endhint %}

OE is available from the Emporix Management Dashboard. The dashboard is where you perform your administration and configuration tasks. It’s also where you check your data and statistics.

As a customer, you receive your tenant details with credentials to log in to Emporix Management Dashboard when the [provisioning process](/oe-user-guides/getting-started/provisioning.md) is complete.

To access OE:

1. Use the link provided to you in the account activation email and log in to the dashboard with your email address and password.

<figure><img src="https://2734760799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dAaH7DfB59pzZwLxmur%2Fuploads%2Fgit-blob-00c0da2a19cc3aea0901a618299814c26a645ccd%2Fwelcome_screen.png?alt=media" alt="" width="150"><figcaption></figcaption></figure>

2. After you log in to Emporix Management Dashboard, you can see the welcome page. Go to **Orchestration** using the navigation menu on the left side of the application.\
   If you are an Emporix Commerce Engine (CE) customer as well, you can see all the CE modules in the navigation menu as well. If you use OE alone, the CE modules are not visible and you have access only to the Orchestration and Administration modules, depending on your assigned role.

<figure><img src="https://2734760799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dAaH7DfB59pzZwLxmur%2Fuploads%2Fgit-blob-ae906834cf599bc92e3bbade5a99898e805dfeed%2Fdashboard_vs.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To learn more about the features of Management Dashboard, see [Emporix Management Dashboard](/user-guides/management-dashboard/introduction.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://developer.emporix.io/oe-user-guides/management-dashboard/accessing-oe.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.
