> 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/quick-walkthroughs/participant-management.md).

# Participant Management

(Adding Participants on the Participant Registry UI)

This page explains how a Participant can be added to the Participant Registry.

#### 1. Fill out participant details

<figure><img src="https://2110281265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKDJDsmddUm6vG90kdzt%2Fuploads%2F1z5Zedbmu5piBT1kwT7C%2Fimage.png?alt=media&amp;token=8fe3795f-67e8-4103-8ade-7a45f028f2f6" alt=""><figcaption><p>Adding Participant Details</p></figcaption></figure>

<details>

<summary>Participant details</summary>

While generating/obtaining the certificate, a valid **PartyID** is also required. This PartyID or identifier is used to register the participant in the dataspace.\
The **party name** is the Organisation Name used to generate/obtain the certificate.\
**Adherence status** should be active for participants that are in compliance with the dataspace agreements.\
**Capabilities url** is an optional URL for parties providing services, referring to the [Capabilities endpoint](https://dev.ishare.eu/common/capabilities.html) used to discover the participant's services. \
**Registrar Data Space ID** - is the ID of the dataspace onboarding the participant.

</details>

#### 2. Adding the certificate

If a certificate is required (see below), upload the certificate and click 'Save'.

<div align="center"><figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101141727381/original/i7eIRQn3hVbn8GRmAyy5jBhDVHZ31Z53Lg.png?1708011071" alt=""><figcaption><p>Certificates addition in the Participant Registry</p></figcaption></figure></div>

#### 3. Add an Authorisation Registry and additional details

For parties with the role of Entitled Party, optionally an Authorisation Registry can be added.

<figure><img src="https://2110281265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKDJDsmddUm6vG90kdzt%2Fuploads%2FjyAv14lSVhlod2YXs3y1%2Fimage.png?alt=media&amp;token=36145b52-5754-4dec-9d8d-42ec80868e86" alt=""><figcaption><p>Adding Additional Details</p></figcaption></figure>

<details>

<summary>AR &#x26; additional details </summary>

Authorisation Registry and Additional Participant Details are optional.

</details>

#### 4. Add agreements and add the party to the right dataspace

Add two agreements (Terms of Use and Accession Agreement) and optionally extra agreements that are specific for a data space.&#x20;

<figure><img src="https://2110281265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKDJDsmddUm6vG90kdzt%2Fuploads%2FN7eSRLw4GztSwkFlGgwM%2Fimage.png?alt=media&amp;token=33342c87-c7ab-485f-ad28-8a8d8c8cb326" alt=""><figcaption><p>Adding Agreements</p></figcaption></figure>

<details>

<summary>Agreements</summary>

The signed Terms Of Use and Accession Agreement are required for all participants. Dummy agreements can be added for test environment.

For Certified Parties - Certified Parties agreement is required.&#x20;

For more information on the Legal agreements required for onboarding participants to a dataspace, refer to the [Legal Agreements in the Trust Framework.](https://framework.ishare.eu/detailed-descriptions/legal)&#x20;

</details>

#### 5. Add party roles

Select the roles which the participant will fulfill.&#x20;

<figure><img src="https://2110281265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfKDJDsmddUm6vG90kdzt%2Fuploads%2F8OYiOCP4aJ5iXCqVRnsd%2Fimage.png?alt=media&amp;token=0f2eb3e0-667f-4922-8049-efdb182b5fe3" alt=""><figcaption><p>Adding Roles</p></figcaption></figure>

<details>

<summary>Roles </summary>

A minimum of one role is required to be added. Organisation or Participants can also play multiple roles.

For clarity on Roles used in the Trust Framework,[ refer here](https://framework.ishare.eu/main-aspects-of-the-ishare-trust-framework/framework-and-roles).&#x20;

</details>

{% hint style="info" %}

For all participants with the role of Service Provider, Service Consumer with machine-to-machine API implementation, Authorization Registry or Identity Provider a certificate is required.

* For production implementations refer to [iSHARE's eSEAL Guide](https://github.com/iSHAREScheme/eSEALsGuide).
* For UAT/test implementations refer to [creating a test certificate](/apply-ishare/test-certificate.md).
  {% endhint %}


---

# 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://trustbok.ishare.eu/apply-ishare/quick-walkthroughs/participant-management.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.
