> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/administration-control-plane/dashboard-and-usage.md).

# Dashboard and usage

The dashboard shows resource totals and plan consumption for the selected organization.

Use it to review setup, track usage, and act on plan limits.

### Resource summary

#### Applications

Shows the total number of applications in the selected organization.

Use it to confirm product coverage and ownership.

#### Projects

Shows the total number of projects in the selected organization.

Projects are the execution workspaces for teams and releases.

#### Users

Shows the number of users with access to the organization.

This includes admins, contributors, and read-only members.

#### Integrations

Shows the configured external connections.

This can include CI/CD tools, ALM systems, chat platforms, and internal services.

<figure><img src="/files/92nAfCHWvRijo0BN3JHp" alt=""><figcaption></figcaption></figure>

### Upgrade your plan

Admins can start a plan upgrade from the dashboard.

New entitlements appear after provisioning completes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mozarkdocs.gitbook.io/appx_documentation/administration-control-plane/dashboard-and-usage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.