> 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/equipme/offer-management/service-portfolio.md).

# Service Portfolio

The service portfolio is the central place where your organisation defines everything it wants to offer inside equipme. It brings all services, items and internal offers together in one structured environment. Whether you provide hardware, software, workplace resources, cloud services or internal support packages, the portfolio is where each of these elements is created, described and managed.

{% hint style="info" %}
If your organisation is connected to a provider and you do not see the service portfolio in your equipme app, the module has not been enabled for your account. Only your provider can activate this module. Please contact your provider if you want to use the service portfolio.
{% endhint %}

The idea behind the service portfolio is simple but powerful. It gives your organisation a clear, consistent catalogue that employees or customers can request from, while providing you with the control you need to manage availability, pricing, lifecycle stages and the general behaviour of each service. Instead of information being scattered across tools or documented in spreadsheets, the portfolio becomes the single source of truth for everything you offer.

When you create a service, you define more than just a name. You describe how the service should be used, who it is meant for, and how it behaves in real workflows. You determine whether it is something that can be purchased, rented or assigned. You can define if it is a one time order, part of a recurring subscription, or something that requires approval. You decide how it appears for the end user, what information is visible, and which settings influence the ordering process. These definitions ensure that each service is consistent and predictable every time someone interacts with it.

The service portfolio also provides full flexibility for internal and external scenarios. You can create offers that your organisation provides internally to its own employees, as well as services that you want to offer directly to customers who work with you. In both cases, equipme ensures that your catalogue remains clean and easy to understand, no matter how many services you manage or how diverse they are.

Another important part of the portfolio is structure. Services can be organised into categories and enriched with attributes that help with filtering and internal organisation. This becomes especially useful as your catalogue grows, since employees and customers should always be able to navigate it intuitively. Clear structure reduces confusion and supports consistent decision making across your organisation.

Each service also plays a role in downstream processes. Once someone places an order, the service definition determines how it flows through approval steps, assignment, fulfilment and billing. A carefully maintained service portfolio therefore has a direct impact on how smooth and efficient your internal processes run. The more accurate the service definition, the fewer manual interventions are needed later.

The portfolio is also the foundation for more advanced capabilities in equipme. Features such as pricing models, subscription handling, service dependencies, templates or automated assignment all rely on clean service definitions. A well maintained catalogue becomes a key asset for automation, transparency and governance across your organisation.


---

# 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/equipme/offer-management/service-portfolio.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.