> For the complete documentation index, see [llms.txt](https://template.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://template.ishare.eu/business-and-organisational-building-blocks/governance-building-blocks/participation-management.md).
# Participation Management
Smooth and secure participation is at the core of a functioning data space. According to the DSSC Blueprint 3.0, this building block outlines how participants are defined, onboarded, managed throughout their lifecycle, and, if needed, offboarded, with a strong emphasis on trust, clarity, legal alignment, and the conditions needed for secure and compliant data transactions and service provision.
According to DSSC, effective participation management includes:
* Clear roles and categories for data space participants,
* Defined onboarding and offboarding procedures, including identification, eligibility assessment, assignment of roles and access rights; monitoring of participant compliance with governance rules; suspension, revocation, or voluntary withdrawal procedures,
* Internal governance readiness, including role taxonomy (e.g. data rights holders, data providers, data consumers, etc), a common understanding of rights, responsibilities, technical access rules, and participation conditions aligned with the Data Space Governance Framework, and the Rulebook if defined (as described in the [Organisational Form & Governance Authority](https://template.ishare.eu/business-and-organisational-building-blocks/governance-building-blocks/organisational-form-and-governance-authority)),
* Mechanisms for ensuring inclusivity, compliance, data sovereignty, and scalability as the data sovereignty space grows.
By defining clear participation rules and lifecycle processes, the Participation Management, together with the Trust Framework and Governance Framework, ensures that data exchange takes place in a trusted environment where responsibilities, permissions, and accountability are clearly defined.
{% hint style="info" %}
The complete DSSC description is available [here](https://blueprint.dssc.eu/?pane=business\&intro=blueprint-in-the-broader-context\&f%5BblueprintVersion%5D=v3.0\&business=participation-management#ParticipationManagement).
{% endhint %}
The iSHARE Trust Framework directly supports this building block by offering:
Identification and Authorisation mechanisms
[Identification ](https://trustbok.ishare.eu/apply-ishare/identification)and [authorisation mechanisms](https://trustbok.ishare.eu/apply-ishare/authentication) that are aligned with eIDAS and organisational trust standards.
* **Multiple Identifiers:** Participants under the iSHARE Framework can be recognised by multiple identifiers (EORI or chamber of commerce numbers), which are recognised by converting into a common identifier, [iSHARE ID,](https://framework.ishare.eu/glossary-and-legal-notices/glossary#glossary-ishare-id) reducing onboarding barriers and improving interoperability across ecosystems.
Participant Registry
The Participant Registry role is fulfilled by a participant who validates and onboards the participants into the data space. The Data Space Governance Body defines the requirements and governs the process of onboarding participants into the data space.
* Can hold information on all participants in the data space; i.e. information indicating their level of assurance, services offered and roles performed in the data space.
* Has processes and criteria in place allowing for the onboarding or registration, update and review of participants;
* Can confirm whether a participant is a member of the data space.
* Can register and maintain claims for participants that are registered by other Participant Registries, provided that such claims are within the scope of the data space it governs and that mandatory validation requirements are fulfilled before claim submission.
* **Participant Registry API**: These specifications enable the creation and updating of participant information via API, ensuring alignment, automation, and participant lifecycle management.
For technical requirements, refer to [Participant Registry getting started in the developer portal.](https://dev.ishare.eu/participant-registry-role/getting-started)
A Role-Based Architecture with Functional Requirements per Role
See more here about [role-based architecture](https://framework.ishare.eu/main-aspects-of-the-ishare-trust-framework/framework-and-roles) and [functional requirements per role](https://framework.ishare.eu/detailed-descriptions/functional/functional-requirements-per-role).
Predefined Operational Processes
For [Admission](https://framework.ishare.eu/detailed-descriptions/operational/operational-processes/admission), [Withdrawal or Downgrade](https://framework.ishare.eu/detailed-descriptions/operational/operational-processes/withdrawal-or-downgrade), [Warnings, Suspension and Exclusion](https://framework.ishare.eu/detailed-descriptions/operational/operational-processes/warnings-suspension-and-exclusion),
Standardised Delegation Requests
Onboarding and participation processes now include the creation of standardised delegation evidence, strengthening trust and compliance (see here in [Structure of Delegation Evidence](https://framework.ishare.eu/detailed-descriptions/technical/structure-of-delegation-evidence)).
iSHARE also enables participants to define and enforce their own access and usage policies through [delegation structures](https://framework.ishare.eu/detailed-descriptions/functional/delegation-paths) and [licenses](https://framework.ishare.eu/detailed-descriptions/functional/licenses), further reinforcing participant autonomy and trust. (These are further discussed in the [Access and Usage Policies Enforcement](https://template.ishare.eu/technical-building-blocks/data-sovereignty-and-trust/access-and-usage-policies-and-enforcement) building block).
Figure 12. Offerings of the iSHARE Trust Framework.
#### **Participant requirements**
It is important to note that requirements may differ depending on the role and context. For example, a small organisation may need onboarding support to meet technical requirements, while a larger or more critical participant may be subject to stricter interoperability, security, or data quality checks. Likewise, a Data Provider may need clear internal responsibility for data rights and quality, while a service provider may need to demonstrate operational and technical compliance before admission.
Figure 13. Steps for the participation lifecycle
#### **How It Applies in Practice**
In practice, this requires organisations to establish clear internal responsibilities, decision-making processes, and the necessary capabilities for identification, attestation, delegation, and participant registry management. It is also important to consider admission criteria, data quality, interoperability, and ongoing compliance as the data space grows.
While the core onboarding procedures are provided by the iSHARE Trust Framework, each data space remains free to:
* Define additional operational, legal, or technical criteria,
* Customise participant categories and approval processes,
* Decide how strict admission criteria should be, balancing lower barriers to entry with interoperability, data quality, and compliance needs,
* Layer in sector-specific rules and lifecycle management mechanisms.
In short, well-managed participation is what transforms a set of organisations into a trusted data-sharing ecosystem. iSHARE provides the tools; your data space decides how to apply them throughout the participant lifecycle and as the ecosystem scales.
{% hint style="info" %}
Participation Management connects closely with other building blocks:
* **Identity & Attestation Management** – ensures verified and trusted participant identities.
* **Access & Usage Policies Enforcement** – makes sure that only participants with the right permissions and licenses can access a specific data set.
* **Regulatory Compliance & Contractual Frameworks** – embeds legal certainty into the participant lifecycle.
* **Organisational Form & Governance Authority:** Sets rules and requirements for establishing and running the data space.
* **Intermediaries & Operators:** Facilitate data transactions and operations while following governance rules.
* **Provenance & Traceability:** Require rules and processes to ensure compliance and transparency.
{% endhint %}
{% hint style="warning" %}
The guiding questions can help in the co-creation process and in defining this building block, so please see the next section.
{% 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 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://template.ishare.eu/business-and-organisational-building-blocks/governance-building-blocks/participation-management.md?ask=&goal=
```
`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.