> 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.md).

# Getting started

What equipme is, how the app is structured and how to get productive in just a few steps.

## What is equipme?

equipme represents your company's equipment as a **digital twin**: you see which locations, organizational units and employees exist and which work equipment (assets and services) is assigned to whom. The processes build on this:

1. **Map your organization**: create locations, groups, employees, cost centers and billing addresses, or import them via HR sync.
2. **Procure**: select services in the **Marketplace**, collect them as **order requests**, have them **approved** and **order** them.
3. **Manage**: Delivered services appear in the **inventory**. There you assign, exchange, store or cancel them.
4. **Control**: analyze costs, orders and invoices in **Controlling**.
5. **Automate** (optional): map processes such as onboarding, approvals or data synchronization with third-party systems in **Automation**.

Employees use the **self-service**: there they see their own equipment, request new work equipment and report problems.

## Basic terms

| Term                    | Meaning                                                                                                                                                                     |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Service**             | Anything that can be assigned to an employee, location or warehouse: hardware (e.g. a laptop), a software license, a cloud service, a professional service or an accessory. |
| **Asset**               | A specific instance of a service assigned to a target, e.g. "MacBook Pro, serial number …, assigned to Max Muster". Also called a *service instance* in the app.            |
| **Offer**               | An orderable variant of a service with price, term, billing interval and contract type (e.g. purchase or rental).                                                           |
| **Order request**       | A single requested item waiting for approval and ordering.                                                                                                                  |
| **Approval request**    | The process by which order requests are submitted to a responsible person for approval.                                                                                     |
| **Supplier / provider** | The company that delivers a service.                                                                                                                                        |

You can find a complete list in the [glossary](/dokumentation/help/glossary.md).

## What's next?

* [Sign-in and registration](/dokumentation/getting-started/sign-in-and-registration.md)
* [The user interface](/dokumentation/getting-started/user-interface.md)
* [Roles and views](/dokumentation/getting-started/roles-and-views.md)
* [The dashboard](/dokumentation/getting-started/dashboard.md)
* [Operating models: Hosted and Standalone](/dokumentation/getting-started/operating-models.md)
* [Initial setup (checklist for administrators)](/dokumentation/getting-started/initial-setup.md)
* [Rolling out equipme in your organization](/dokumentation/getting-started/rollout-guide.md)


---

# 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.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.