> 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/classes/employee-self-service/manage-your-equipment-my-services.md).

# Manage your Equipment (My services)

<figure><img src="/files/athi5npVyyhLTUkl8C09" alt=""><figcaption></figcaption></figure>

## My services – Manage what is assigned to you

**My services** is the place where you manage everything that has been issued to you for work, whether it’s a device, a software subscription, or another resource you rely on in your daily tasks. The goal isn’t just to show what you have, but to give you clarity and autonomy over the lifecycle of those items.

Instead of relying on back-and-forth communication with your IT team, you can access the key information directly. Every service card reflects its current status, how long it remains available, and whether it is renewed automatically. This helps you understand the commitments attached to a device or application without needing to interpret contracts or internal policies.

### Confirming receipt and reporting issues

Some resources require a short acknowledgement once you have received them physically. This small step ensures that the system keeps an accurate record of what is in your possession and prevents misunderstandings later. You can complete this with one click as soon as the item arrives.

If something is not working as expected—whether the device is damaged, misconfigured, or simply cannot be used—you can report the problem directly from the same place. You do not need to search for contact forms or explain what you are referring to, because the system automatically links your request to the correct item. This makes support faster and easier for both sides.

### Exploring a service in detail

By selecting **Show details**, you can access a deeper view of an individual service.\
This page gives you the full context: what exactly has been assigned, under which plan or subscription, and what terms apply to it.

Depending on how your organization works, you may also see assignment information, renewal conditions, or other details that help you understand the lifecycle of the item. The purpose here is transparency: you shouldn’t have to guess how something is managed or who is responsible for it.

### Requesting changes or taking actions

<figure><img src="/files/eeIz1tqcc0i7Rtn1l6f9" alt="" width="251"><figcaption></figcaption></figure>

In many cases, you can request adjustments directly from the service instead of opening tickets manually. Typical examples include returning a device you no longer need, asking for a replacement, or requesting a successor service when something needs to be upgraded.

* **Return** the device when it is no longer required
* **Swap** it if it is broken, lost, or outdated
* Request a **Successor service** when you need the next version or an alternative

These actions follow automated workflows behind the scenes, so your request doesn’t get lost in emails or chats. It also ensures that your organization can track processes, stock, and costs in a structured way.


---

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

```
GET https://hub.equipme.io/classes/employee-self-service/manage-your-equipment-my-services.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
