# Ecosystem set up

### Create an ecosystem

You can create an Ecosystem through the left side menu by clicking **Ecosystem -> Create Ecosystem** button.

When creating an ecosystem an on-chain trust registry is created on the blockchain, a list of relationships between issuers and verifiers. It simplifies the process of identifying which issuers and verifiers are trustworthy within a particular ecosystem.

{% hint style="info" %}
Ecosystem Tools is an add-on feature. If you do not see it in your menu bar and want it enabled for your account please contact <support@truvera.io>
{% endhint %}

First steps in creating your ecosystem is defining your brand. Ecosystem branding is important, it will be present on the credentials issued by the participants and verification templates for the verifiers. Having a clearly defined brand makes it easier for ecosystem participants to trust the ecosystem and have a unified experience from credential issuance, to storage and verification.

<figure><img src="/files/cDpslsLkpYkwVdBOj6SL" alt="" width="375"><figcaption></figcaption></figure>

You will need to set the Ecosystem **Name**, **Description,** add an **Ecosystem URL**, a valid URL that links to a page outlining the advantages and key details of joining your ecosystem.

**Ecosystem Administrator Profile DID** will allow you to choose from an existing or add a new DID that will be the administrator of the ecosystem.

Next step will allow you to set your Governance Framework document, that is used to communicate the rules and guidelines of the ecosystem to every stakeholder, ensuring clarity and consistency, which helps align all stakeholders on the processes surrounding issuance and verification.

<figure><img src="/files/HJ9Rf0ptf1t0JdMyU9Sm" alt="" width="375"><figcaption></figcaption></figure>

### Invite a participant

After the ecosystem is set up you can start inviting participants. Ecosystem participants can be Issuers, Verifiers or both depending on their role in your ecosystem. You will be able to assign credential schemas based on the role of the participant.

Ecosystem participants can have and manage their own Truvera accounts, but we also enable our customers to create ecosystems where the participant accounts are managed and paid for by them. Using [Sub-accounts](/truvera-api/sub-accounts.md) allows creation of additional Truvera accounts and inviting them to participate in the ecosystem using the API.

<figure><img src="/files/VbMsAwjUwSCQEizkzuST" alt=""><figcaption></figcaption></figure>

After clicking **Invite participants** you will be able to select a credential schema and a role of the participant.

<figure><img src="/files/MyZbXEqE5nb1U9XPt88Y" alt="" width="375"><figcaption></figcaption></figure>

Ecosystem participants will need to have an account with Truvera to join the ecosystem. When they are logged in to their Truvera Workspace account and click on the link provided by the ecosystem administrator, they will be immediately prompted to **Join the ecosystem** and select an organization profile that will be used to participate in the ecosystem.

<figure><img src="/files/vinCUjKbofn0X2L3psNn" alt=""><figcaption></figcaption></figure>

Ecosystem Administrator and participants will see the list of Issuers and Verifiers in the table.

<figure><img src="/files/qtuPXBQw7KC3yU4ThLHB" alt=""><figcaption></figcaption></figure>

Ecosystem administrator will be able to **Suspend**, **Remove** or **Edit** the existing Ecosystem participants. They can also change the role of the participant and assign schemas.

### Assign credential schemas

To assign a credential schema to participants you will need to first [create the schemas](/truvera-workspace/create-a-schema.md). To assign the schema you will click the **Add schema** button.

<figure><img src="/files/dpZnkiQERHIrqvHcFmCu" alt=""><figcaption></figcaption></figure>

You will be able to select from your schemas from a dropdown or enter schema URL and assign it to ecosystem participants.

<figure><img src="/files/g8jFn9UKOxN1aqqtYbCQ" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
You can choose to add a verification price for your schema, which will set a fee for each verification of credential using the selected schema. [Learn more about verification prices](/truvera-workspace/monetizing-credentials.md)
{% endhint %}

Credential schemas can have Restricted or Public verifiability. If the schema is assigned to at least one participant that can verify the schema, the verification will restricted to only those participants. If there are no assigned verifiers the schema will be publicly verifiable.

<figure><img src="/files/NkRCaG9vdvAsFa8mAzTA" alt=""><figcaption></figcaption></figure>

Assigned schemas will be immediately available to participants and once credentials are issued using a schema assigned to an ecosystem, the ecosystem branding will be visible throughout the entire credential user journey.

Ecosystem branding will be visible in the wallet once a credential is issued by an ecosystem participant.

![](/files/YysqrvC7S6eJv1K1Ityw)

### Add verification templates

Ecosystem administrator will be able to add verification templates that will be available for all ecosystem participants.

<figure><img src="/files/Yykq513baaB2wPZz9IyA" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.truvera.io/truvera-workspace/ecosystem-tools/ecosystem-set-up.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.