> For the complete documentation index, see [llms.txt](https://framework.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.ishare.eu/version-3.0/detailed-descriptions/functional/primary-use-cases/3.-h2m-service-provision-with-identity-info-at-the-ip.md).

# 2. H2M service provision with identity info at the IP

In use case 2, a service is provided by the Service Provider to the Human Service Consumer. Identity info is held at the Identity Provider.

### Roles <a href="#id-3.h2mserviceprovisionwithidentityinfoattheip-roles" id="id-3.h2mserviceprovisionwithidentityinfoattheip-roles"></a>

<table data-header-hidden data-full-width="true"><thead><tr><th width="178"></th><th width="164"></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><br><br></td><td></td><td><strong>Delegation info PIP</strong></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td><em>No delegation</em></td><td>Service Provider</td><td>Entitled Party</td><td>Authorization Reg</td></tr><tr><td><strong>Auth info PIP</strong></td><td>Identity Provider</td><td>2.</td><td>2a</td><td>2b</td><td>2c</td></tr></tbody></table>

As no delegation takes place, the legal entity fulfilling the Entitled Party role also fulfils the Service Consumer role.

Note that an [Identity Broker ](/version-3.0/detailed-descriptions/functional/primary-use-cases/3.-h2m-service-provision-with-identity-info-at-the-ip/with-identity-broker.md)can be introduced to broker the relation between the Service Provider and the Identity Provider(s). This is optional and useful in situations with several Identity Providers.


---

# 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://framework.ishare.eu/version-3.0/detailed-descriptions/functional/primary-use-cases/3.-h2m-service-provision-with-identity-info-at-the-ip.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.