# 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](https://dev.ishare.eu/authorisation-registry-role/m2m-verifiable-credential-endpoints) for machine Service Consumers and via the [OIDC4VC/VP Endpoints](https://dev.ishare.eu/authorisation-registry-role/openid4vci-endpoints) 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](https://dev.ishare.eu/all-roles-common-endpoints/access-token-m2m)
* [ ] [Capabilities](https://dev.ishare.eu/all-roles-common-endpoints/capabilities)
* [ ] [Delegation](https://dev.ishare.eu/authorisation-registry-role/delegation-endpoint)