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

# Service catalog

Service catalog: managing basic services (e.g. tenants) and cloud services.

**Path:** sidebar → **"Assets" → "Service catalog"**

The service catalog has two tabs.

## "Basic services"

Basic services are company-wide foundations on which other services build, e.g. a Microsoft 365 tenant on which individual user licenses run.

* The list shows active and requested basic services with "Service name", "Service user", "Instances" (dependent services), "Business Owner", "Monthly price", "One-time price" and "Status".
* **"Add"** opens the Marketplace, filtered to basic services.
* A click opens the detail page with the tabs "Service instances" and "Service user".

**Rules:**

* Each basic service exists only once per company.
* Services that require a basic service can only be ordered once the basic service exists or has been requested. The Marketplace points this out.
* If a basic service is cancelled, all dependent services are cancelled as well.

## "Cloud services"

Here you group cloud resources into **cloud services** (containers), e.g. per project or environment, to see their costs together.

* Columns: "ID", "Name", "Services" (number of resources), "Cost center", "Current costs", "Forecast".
* **"New"**: create a cloud service with a "Service name".
* **"Import"**: import resources via Excel; instead of employee and location, you specify the cloud service ID (see [Record and import inventory](/dokumentation/assets/inventory/record-and-import-inventory.md)).
* **"Delete"**: only for empty cloud services.
* In the detail view, you rename the cloud service, see the assigned resources and add more from the Marketplace via "Add".


---

# 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/service-catalog.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.