> For the complete documentation index, see [llms.txt](https://docs.glbnxt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glbnxt.com/faq/glbnxt-platform/why-dont-i-see-my-apps.md).
# Why don't I see My Apps?
My Apps is a tab under **Platform Configuration → Application Management**. Three things decide whether you see it.
**Your role.** Only administrators have access to Application Management. If you are a moderator or user, ask an administrator in your organisation.
**Your subscription.** My Apps is not part of every plan:
* **Included**: the tab is visible and ready to use.
* **Available on request**: the tab shows **Not in your subscription**. Choose **Contact GLBNXT** to add it to your plan.
* **Not included**: the tab does not appear.
**Your organisation's setup.** GLBNXT prepares each organisation for My Apps before the tab appears. If your plan includes My Apps and you are an administrator but still don't see it, email .
To learn what My Apps does, see [My Apps](https://docs.glbnxt.com/configure-glbnxt/platform-configuration/application-management/my-apps).
---
# 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.glbnxt.com/faq/glbnxt-platform/why-dont-i-see-my-apps.md?ask=&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.
