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

# Assets

Overview of the Assets area: inventory, warehouse management and service catalog, plus the lifecycle of a service.

In the **"Assets"** menu you manage everything the company already owns, rents, leases or subscribes to. In equipme, every single asset is called a **service**, even hardware.

| Menu item                                                         | Content                                                         |
| ----------------------------------------------------------------- | --------------------------------------------------------------- |
| [**"Inventory"**](/dokumentation/assets/inventory.md)             | All of the company's services with assignment, costs and status |
| [**"Warehouse management"**](/dokumentation/assets/warehouse.md)  | Services that are in a warehouse waiting to be used             |
| [**"Service catalog"**](/dokumentation/assets/service-catalog.md) | Basic services (e.g. a Microsoft 365 tenant) and cloud services |

**Who has access?** All roles with read access to services, i.e. administrators, purchasers, planners and controllers. Supervisors, location managers and business owners find the inventory under **"My organization" → "Inventory"** and only see their own area of responsibility there. Employees see their own services under "My workspace" → ["My equipment"](/dokumentation/self-service/my-services.md).

## The lifecycle of a service

```
Order request → Approval → Ordered → Ordered (confirmed) → In delivery → Active
                                                                          │
                     Change options · Book add-ons · Reassign · Replace ◄┤
                                                                          │
                                  Store (warehouse) · Cancel (Cancelled) · Remove
```

1. **Procurement:** A service is created through an [order in the Marketplace](/dokumentation/procurement.md) or is [recorded or imported as existing inventory](/dokumentation/assets/inventory/record-and-import-inventory.md).
2. **Use:** Active services are assigned to an employee, a location and/or a warehouse. They can be moved, extended (add-ons, options) or replaced.
3. **End:** A service is stored, cancelled or (for your own assets) removed.

All actions and their prerequisites are described in [Lifecycle actions](/dokumentation/assets/inventory/lifecycle-actions.md). The meaning of each status is explained under [Status of a service](/dokumentation/assets/inventory/status.md).

{% hint style="info" %}
**What takes effect immediately and what creates a request:** Assignment, inventory number, cost center, group, notes, documents and features are saved **immediately**. Cancellations, option changes, add-ons, call-offs from the warehouse and replacements, on the other hand, create an [**order request**](/dokumentation/procurement/order-requests-and-checkout.md), which, depending on your settings, is approved and then ordered.
{% endhint %}


---

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