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

# The dashboard

The dashboard: key figures, quick actions and confirmations of receipt at a glance.

The **"Dashboard"** is the start page for roles with a company or manager view. You find it in the sidebar under "My company" or "My organization". It greets you according to the time of day and shows the most important key figures. Employees without any other role start on "My equipment" instead (see [Employee self-service](/dokumentation/self-service.md)).

## Quick actions (administrators only)

Colored tiles take you directly to common tasks:

| Quick action             | What happens                                                                                                                                                                                                         |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **"Onboard employee"**   | Opens the "Create employee" dialog. If there is no location yet, you are first asked to create one.                                                                                                                  |
| **"Order service"**      | Opens the [Marketplace](/dokumentation/procurement/marketplace.md).                                                                                                                                                  |
| **"Record inventory"**   | Records existing devices and services in the inventory (see [Recording and importing inventory](/dokumentation/assets/inventory/record-and-import-inventory.md)). If the module is not active, an info page appears. |
| **"Create ticket"**      | Opens a [support request](/dokumentation/self-service/tickets.md) in Equipme Operate (only with an active ticket system).                                                                                            |
| **"Create offer"**       | Creates your own service in the [Service portfolio](/dokumentation/offer-management/service-portfolio.md).                                                                                                           |
| **"Invite supplier"**    | Invites a supplier by email to collaborate via equipme (Standalone customers only).                                                                                                                                  |
| **"Automate processes"** | Opens the [workflows](/dokumentation/automation/workflows.md) or, without an Automation license, an info page.                                                                                                       |

## Key figures

Each tile has a link icon that takes you to the matching detail page. Which tiles you see depends on your role:

| Key figure                        | Content                                                                                                                                |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **"Pending approvals"**           | Approval requests waiting for a decision → [Approvals](/dokumentation/procurement/approvals.md)                                        |
| **"Open purchase requests"**      | Items that still need to be ordered → [Order requests](/dokumentation/procurement/order-requests-and-checkout.md)                      |
| **"Employees"**                   | Number of employees with trend                                                                                                         |
| **"Costs for the current month"** | Running costs for the month (only if you are allowed to see prices) → [Cost management](/dokumentation/controlling/cost-management.md) |
| **"Locations"**                   | Number of locations                                                                                                                    |
| **"Active assets"**               | Number of active services → [Inventory](/dokumentation/assets/inventory.md)                                                            |
| **Confirmation of receipt**       | Services whose receipt still needs to be confirmed (only if the feature is active)                                                     |

### Confirmation of receipt

If **"Confirmation of receipt"** is enabled in the [portal settings](/dokumentation/settings/portal-settings.md), the assigned employee or a responsible manager is asked to confirm receipt of new services. Pending confirmations appear on the dashboard and in the employee's profile. Click **"Review"** or **"Please confirm receipt."**.


---

# 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://hub.equipme.io/dokumentation/getting-started/dashboard.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.