> For the complete documentation index, see [llms.txt](https://trustbok.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trustbok.ishare.eu/apply-ishare/authorisation/deployment-and-use-cases.md).

# Deployment & Use Cases

The iSHARE Trust Framework allows flexibility in how the Authorisation Registry is implemented and operated. Depending on governance requirements, operational scale, and the structure of a data space, different deployment models can be adopted. This section describes a general overview of those models and illustrates how the AR is applied in practice across real data spaces.

### Deployment models

The iSHARE framework does not prescribe a single deployment model for Authorisation Registries. Several patterns are used in practice, each suited to different governance and operational contexts:

{% hint style="info" %}
Similarly, the iSHARE Trust Framework does not define one single implementation. All the following deployment models can be implemented using either [Verifiable Credentials](https://framework.ishare.eu/detailed-descriptions/technical/structure-of-delegation-evidence/data-rights-credential-vc) or [API flow](https://dev.ishare.eu/authorisation-registry-role/delegation-endpoint).
{% endhint %}

#### Single AR as a shared service in a data space

A single AR serves all participants in a given data space. This is the simplest model and the easiest to govern collectively. It works well for tightly scoped data spaces with a defined membership and a shared governance body.

<img src="/files/7pqQjoQzqmI32QQ8OyJY" alt="" height="457" width="624">

<p align="center">Figure 14: AR as a single shared service under governance authority</p>

#### Distributed or federated AR

Multiple ARs operate within the same data space, each serving different participants or capability areas. Service Providers discover the applicable AR per capability. This model scales better for large or heterogeneous data spaces and allows specialised governance for different types of delegations.

<img src="/files/uI56ptNZg9EhkZUWACyH" alt="" height="584.5" width="624">

<p align="center">Figure 15: Distributed or federated AR under the governance authority</p>

{% hint style="info" %}
These are the very first basic deployment models; however, please keep in mind that there could be more variations and alternatives. For example, there can be multiple Authorisation Registries per Data Sharing Initiative and per service.&#x20;
{% endhint %}

### Use Cases

The following examples illustrate how the Authorisation Registry is applied across real data spaces — what role it plays, and what value it provides to participants. See more use cases here.

#### 1. DVU ([Datastelsel Verduurzaming Utiliteit - Data System for Sustainability in Utility Buildings](https://ishare.eu/ecosystem/ishare-in-data-spaces/dvu/))&#x20;

DVU enables trusted data sharing to support sustainability and energy optimisation of non-residential buildings, involving building owners, energy service providers, technology providers, and public authorities.

Role of the Authorisation Registry:

* Stores and enforces delegation policies that govern which parties may access building and energy consumption data on behalf of data owners
* Issues delegation evidence to Energy Companies, confirming that a Consumer has been authorised by the relevant Building Owner
* Enables building owners to set, update, and revoke access rights at any time, maintaining control over sensitive energy data throughout the data sharing lifecycle

Value:

* Allows building owners to share sensitive consumption data with confidence, knowing that access is governed and revocable
* Removes the need for bilateral access agreements between every pair of participants
* Supports scalable data sharing for energy optimisation, digital twin development, and CO2 reduction reporting

#### 2. DMI  ([Dutch Metropolitan Innovations](https://ishare.eu/ecosystem/ishare-in-data-spaces/dmi/))

DMI develops and manages data infrastructure for smart, sustainable urbanisation and mobility, bringing together public authorities, infrastructure operators, and private organisations in a governed, federated data space.

Role of the Authorisation Registry:

* Governs access control at every point in the DMI data flow, ensuring that only authorised parties can request and receive data
* Stores delegation policies on behalf of Entitled Parties, enabling data owners to define access rights per participant, capability, or context
* Works alongside AMdEX and the iSHARE governance layer to enforce compliance before any transaction is processed

Value:

* Supports trusted collaboration across public and private stakeholders with fundamentally different mandates and risk profiles
* Enables data owners ,including municipalities, to share data transparently and with full auditability
* Reduces onboarding friction for new participants by providing a shared authorisation infrastructure rather than requiring per-relationship setup


---

# 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://trustbok.ishare.eu/apply-ishare/authorisation/deployment-and-use-cases.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.
