> 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/inventory/asset-details.md).

# Detail page of a service

The detail page of a service: header, features (e.g. serial number), configuration, add-ons, assignment, costs, notes, documents and history.

You open the detail page by clicking a service in the inventory, in the warehouse, in the service catalog, on employee and location pages, in orders or in cost management. Employees reach it via "My workspace" → "My equipment" (with a limited range of functions, see [My equipment](/dokumentation/self-service/my-services.md)).

## Header

* Image, category, name and **status** (see [Status of a service](/dokumentation/assets/inventory/status.md))
* **"Asset ID"**: the unique identifier in equipme
* **"Inventory number"**: your own asset label, e.g. barcode, sticker or ERP number. Edit it via the pencil icon. The inventory number is only used within the company.
* Links **"Detailed description"** and **"Service agreement"**, if the provider has added them
* For add-ons and linked services: the note **"Primary instance: …"** with a link to the main service
* **"Shipment details"** with a tracking link while the service is in transit
* **"History"**: timeline of all status changes with search. You can also withdraw option changes here that have not yet been processed.
* **"Create ticket"**: submit a support request for this service in Equipme Operate (only with an active ticket system, see [Support requests and tickets](/dokumentation/self-service/tickets.md))

## Note and documents

* **"Note"**: formatted free text, e.g. handover instructions.
* **"Documents"**: upload, open, rename and delete files, e.g. invoices, warranty receipts or handover protocols.

## Tabs

### "Features"

* **"Preset"**: features inherited from the product (read-only).
* **Custom features** of this individual item: via **"Add feature"** with "Feature name" and "Feature value".

{% hint style="info" %}
You maintain **serial number, IMEI, MAC address & co.** as a feature, e.g. feature name "Serial number". There is no separate field for this.
{% endhint %}

**Visibility of a feature.** Each feature has the visibility **"Public"** (default for new features) or **"Internal"**. You switch it on the feature with "Set visibility to 'internal'" or "Set visibility to 'public'". The visibility controls which **companies** see a feature, not which people in your company:

| Visibility     | Who sees the feature                                                                          |
| -------------- | --------------------------------------------------------------------------------------------- |
| **"Public"**   | All companies that access the asset, i.e. your company and e.g. your provider or the supplier |
| **"Internal"** | Only the company that created the feature (the "Author")                                      |

Within your company, everyone who may see the asset sees both kinds, including the employee the asset is assigned to. An internal feature of your provider, on the other hand, is not visible to you. You cannot edit features of another author.

### "Configuration"

Shows the booked options (e.g. storage size, color, software edition). If the status and product allow a change, you select a different variant. The new price is displayed. With **"Save"**, the change is submitted as an **order request of the type "Change"**; it only takes effect after approval and ordering.

### "Services & extras"

* **"Already booked"**: booked add-ons and linked services, each with "Open details".
* **"Available to book"**: matching add-ons and linked services. Choose an offer, collect the entries with **"Add to request"** and submit them together ("Request …"). They end up as order requests in the cart.

### "Service instances" and "Service user"

Only for basic services (e.g. a Microsoft 365 tenant): shows the services that depend on it or the connected users.

## Sidebar

### "Lifecycle"

The card has two areas:

* **"Confirmation of receipt"**: status of the confirmation. If it shows "Pending confirmation", the employee or a responsible manager confirms with the check mark **"Confirm"**; administrators can cancel the request via the ✗. Without a running request, **"Request confirmation of receipt"** may be available.
* **"Lifecycle"**: all actions possible in the current status: "Request provision", "Define successor service", "Store service", "Replace service". See [Lifecycle actions](/dokumentation/assets/inventory/lifecycle-actions.md).

If a process is currently running, the actions are locked ("Actions are locked while this process is running."). If you lack edit rights, you see "You can view this service, but not edit it."

### "Assignment details"

"Employee", "Location" or "Warehouse", "Group", "Cost center", "Service owner", "Delivery address", "Provisioning date" and billing address. Use the pencil icon to reassign the service (see [Reassign](/dokumentation/assets/inventory/lifecycle-actions.md#reassigning-a-service)).

### "Financial Overview"

Only with permission to see prices: "One-time costs", "Recurring costs" with "Billing cycle", "Activation date", "Initial term", "Remaining term", "Term extension", "Offer type", "Supplier", "Invoice issuer".

## Footer

* **"Cancel service"** or **"Cancel"** (as long as the service has only been ordered)
* **"Remove"**: only for self-provided services (see [Terminate, cancel or remove](/dokumentation/assets/inventory/lifecycle-actions.md#terminating-cancelling-or-removing))


---

# 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/inventory/asset-details.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.