> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/overview/getting-started.md).

# Getting Started

The getting started guides help each role focus on the right AppControl features.

Choose the guide that matches your role:

* **Platform Administrator.** Manage platform-wide settings, standards, hosting, and licenses.
* **Group Administrator.** Manage app groups, access, and standards for a delegated set of apps.
* **App Owner.** Manage service ownership for one or more Mendix apps.
* **App Administrator.** Manage daily app operations, releases, policies, and tasks.
* **Developer.** Build Mendix apps in line with organizational standards.

### Role guides

* [Platform Administrator](https://docs.bluestorm.io/overview/getting-started/platform-administrator.md)
* [Group Administrator](https://docs.bluestorm.io/overview/getting-started/group-administrator.md)
* [App Owner](https://docs.bluestorm.io/overview/getting-started/app-owner.md)
* [App Administrator](https://docs.bluestorm.io/overview/getting-started/app-administrator.md)
* [Developer](https://docs.bluestorm.io/overview/getting-started/developer.md)

### Task-based tutorials

Use [Tutorials](https://docs.bluestorm.io/overview/tutorials.md) when you want step-by-step help for a specific workflow.


---

# 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://docs.bluestorm.io/overview/getting-started.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.
