> 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/getting-started/provisioning.md).

# Provisioning

Learn how the process of provisioning OE looks like.

After receiving a provisioning request, Emporix prepares a OE tenant for you. When the tenant is ready, you'll receive an email notification to activate your account. Then, you can access the Emporix Management Dashboard and Developer Portal.

* [Management Dashboard](https://dashboard.emporix.io/) is where you access OE.
* [Developer Portal](https://app.emporix.io/) is where you manage your account, tenant or API Keys.

{% hint style="warning" %}
If you want to place a provisioning request, contact our [Emporix Support Team](mailto:support@emporix.com).
{% 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/getting-started/provisioning.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.