> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/version-3.0/authorisation-registry-role/getting-started.md).

# Getting started

The Authorisation Registry role is fulfilled by a legal entity that provides solutions for Adhering Parties for the storage of delegation and authorisation information. An Authorisation Registry:

* Can hold information on delegations to Service Consumers; i.e. information indicating what parts of the rights of an Entitled Party are delegated to a Service Consumer.
* Can check, based on this information, whether a machine representing a legal entity is authorised to take delivery of a service;
* Can confirm whether this is the case for the Service Provider;
* Can issue a DataRights (Verifiable) Credential on behalf of the Entitled Party to Service Consumer to store in a Credential Store (wallet) and present them to Service Providers during access workflows;
* Can expose them via the [DCP Endpoints](/version-3.0/authorisation-registry-role/m2m-verifiable-credential-endpoints.md) for machine Service Consumers and via the [OIDC4VC/VP Endpoints](/version-3.0/authorisation-registry-role/h2m-verifiable-credential-endpoints/openid4vci-endpoints.md) for human Service Consumers.

{% hint style="info" %}
For the structure of the DataRights Credential, see the [JSON Schema.](https://schemas.ishare.eu/v3/datarights/schema.json)

* Can bilaterally provide info about Authorisation Registry to Service Provider and/or Service Consumer.
  {% endhint %}

As a result, Adhering Parties can outsource tasks concerning the management of authorisation and delegation information to an Authorisation Registry instead of implementing their own tooling.

To double-check if required endpoints are implemented, please use the following list as a cheat sheet:

Authorisation Registry

* [ ] [Access Token](/version-3.0/all-roles-common-endpoints/access-token-m2m.md)
* [ ] [Capabilities](/version-3.0/all-roles-common-endpoints/capabilities.md)
* [ ] [Delegation](/version-3.0/authorisation-registry-role/delegation-endpoint.md)


---

# 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://dev.ishare.eu/version-3.0/authorisation-registry-role/getting-started.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.