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

# App Manager tour

The App Manager is where you create Apps, watch them run, and look after the workspace and the account around them. It opens on the Dashboard.

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-829eca9ed1e0a19fbf849de1fa321def2c857139%2Fmanager-dashboard.png?alt=media" alt="The App Manager on its Dashboard: the menu, the workspace switcher, the band saying what needs you, and the four tiles over the Apps table"><figcaption></figcaption></figure>

## The menu

Every screen of the Manager hangs in the menu on the left. The arrow on its edge folds it to icons.

* [**Dashboard**](#dashboard): what needs you in the workspace, and how its Apps run and are used.
* [**Apps**](https://docs.heisenware.com/app-manager/app-manager/apps.md): the workspace's Apps. Create one, set its name, language and [access](https://docs.heisenware.com/app-manager/app-manager/users-and-access.md), run or stop it, and open it in the App Builder.
* [**Databases**](https://docs.heisenware.com/app-builder/app-builder/database-editor.md): opens the workspace's Database editor in a tab of its own. It belongs to the workspace, not to an App.
* [**Planning**](https://docs.heisenware.com/app-manager/app-manager/planning.md): the assistant's planning seat, where you plan a whole set of Apps before building any of them. It is there only where the installation has the assistant.
* [**Agents**](https://docs.heisenware.com/app-manager/app-manager/agents.md): build, update, restart and roll out the [agents](https://docs.heisenware.com/concepts/agents-and-where-code-runs.md) that run on your own hosts.
* [**Integrations**](https://docs.heisenware.com/app-manager/app-manager/integrations.md): logins for things outside that connect to the workspace: MQTT and VRPC clients, local MCP servers, Microsoft 365 Copilot agents.
* [**AI clients**](https://docs.heisenware.com/app-manager/app-manager/ai-clients.md): connect your own AI, such as Claude or ChatGPT, by the workspace's MCP address, and see or end every connection.
* [**Members**](https://docs.heisenware.com/app-manager/app-manager/members.md): the people who build in this account, and what each of them reaches.
* [**Plan & Billing**](https://docs.heisenware.com/app-manager/app-manager/plan-and-billing.md): the plan, the quotas, the credits the assistant spends and the workspaces. Owners of the account see this entry; nobody else does.

An entry carries a badge when its screen wants you: Apps that are not running, agents that are offline or behind their fleet's build, an outdated local MCP server. The Dashboard names the same items.

## Around the menu

* **Workspace switcher**: at the top, showing the [workspace](https://docs.heisenware.com/app-manager/app-manager/workspaces.md) you are in. It lists the workspaces you reach with their domains, switches between them, and lets an owner of the account add one.
* **Documentation**: at the foot, opens these pages beside the screen. The panel reads full width or as a column you can drag wider; the **?** beside a title opens the page about that title. Your choice of light or dark follows into the panel.
* **Account menu**: the three dots beside your name, with **Dark mode** and **Log out**.

## Dashboard

The Dashboard is where the App Manager opens. It shows what needs you in the workspace, and how its Apps run and are used:

* **Needs you** lists the Apps deployed to run that are not running, the agents that are offline or behind their fleet's build, and outdated local MCP servers, each linked to its page. The same items carry a badge in the menu. When nothing needs you, it says *All clear*.
* **Active users today** counts the users who signed in to one of the Apps, with the last 14 days and the change against the week before. **Apps running** counts the Apps running of all the workspace holds, and **Agents online** the agents connected. An owner of the account sees the **credits**, every other member the number of **App users**. Every figure but the active users opens its page.
* **Apps** lists every App of the workspace with its status, how many users are online now, how many it has, and a bar per day over the last 14 days. Click a column header to sort, and a row to open the App.
* A new workspace sees its **first steps**, ticked from what it already holds, until you put them away. An owner of the account also sees the plan and how many Apps it allows.

The Dashboard reads again when you come back to it, or when you click Refresh.


---

# 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.heisenware.com/app-manager/app-manager.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.
