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

# Service Owners

Some services do not belong to one person. A server, a shared device, infrastructure at a location or a centrally managed workplace service is usually looked after by a team rather than an individual.

For these cases you can assign service ownership to an organizational group instead of a specific employee. Responsibility then follows the team, not a name that has to be updated whenever someone changes role.

## Assign a group as Service Owner

The assigned group appears under **Service owner** in the assignment details of the service instance.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FyXPN0wMBGnBuvK2HiqNk%2F2-asset-detail.png?alt=media&#x26;token=72636a26-85b7-4a88-aebb-771c60c80f63" alt=""><figcaption><p>Asset details showing the assigned Service Owner group under Assignment details.</p></figcaption></figure>

## How Service Owner access works

Assigning a group does not automatically give every member of that group additional access.

An employee receives Service Owner access only when **both** conditions are met:

1. The employee is a member of the assigned Service Owner group.
2. The employee has the **Service Business Owner** role.

{% hint style="warning" %}
The role has to be assigned separately. Selecting a group as Service Owner does not grant it.
{% endhint %}

This separation lets you record which team is responsible for a service without widening permissions for everyone on that team.

## What a Service Owner sees

Employees who meet both requirements find the relevant services in their Inventory, even when those services are not assigned to them personally.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FkftjSK8Dvz5qIhXiTUNx%2F1-inventory.png?alt=media&#x26;token=a1bb1e0b-8eae-4efc-8c50-4947c01bf1df" alt=""><figcaption><p>Inventory view showing the services available to an authorized Service Owner.</p></figcaption></figure>

## Set a default Service Owner in the Service Portfolio

If a product should always end up with the same responsible team, you can configure this once on the product instead of after every order.

Product details include a **Responsibilities** section. Under **Service owner**, select the group that should become responsible for future service instances created from that product. When the product is ordered and a new instance is created, the group is carried over automatically.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2F3YJOsDJSf5ptpsKvGUn8%2F3-service-portfolio-detail.png?alt=media&#x26;token=5dabafb2-56fb-45a6-b7d7-6e3b111b488b" alt=""><figcaption><p>Service Portfolio product with Management and Service Owner groups configured under Responsibilities.</p></figcaption></figure>

### Management and Service owner are not the same thing

The two fields under Responsibilities do different jobs:

* **Management** determines which group may manage the product in the Service Portfolio.
* **Service owner** determines which group is assigned as Service Owner when a service instance is created from the product.

They can point to the same group, but they do not have to.

## Availability

Service Owner assignment through groups is available in customer environments, including managed and standalone customer environments. It is not available in supplier environments.


---

# 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, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/equipme/offer-management/service-portfolio/service-owners.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.