Issue a credential¶

Credential issued to a person (an employee of the organization). It allows them to identify themselves and prove their powers or roles within the organization to external services.

When to use it: when you want to grant access to or accredit a specific employee.

Required recipient data: first name, last name, email and employee number.

Credential issued to a machine, service or application (not to a person). It allows a system to identify itself automatically to other services.

When to use it: when you want to accredit a service or application of the organization.

Required data: the service domain and, optionally, an IP address.

The format determines how the credential is structured and protected.

• W3C VC Data Model v2.0 — Standard format and the most compatible with external services.

• SD-JWT VC — Lets the holder show only the necessary data in each presentation, without revealing the rest. Recommended when data privacy is a priority.

  → For more technical information about this format, see SD-JWT VC.

The main difference is whether a PIN is required to accept the credential.

• Authorization Code — The recipient accepts the credential directly from the email or QR code.
• Pre-Authorized Code — The recipient receives a PIN by email after logging in to the wallet, and must enter it to accept the credential.

How the offer is delivered to the recipient. The offer expires after 10 minutes.

• Email — An email with the offer is sent.
• QR code — The portal displays a QR code on screen.

Fill in the Mandatee fields and select at least one power in the Powers section.

Available powers

Powers may vary by organization. The following are some examples.

Function	Actions	Description
Onboarding	Execute	Allows managing the onboarding process for new participants.
Product offering	Create, Update, Delete	Allows creating, modifying and deleting product or service offerings.
Certification	Upload, Attest	Allows uploading and attesting certifications on behalf of the organization.

Before filling in the data, generate the private key by clicking Generate key in the Private key section. This step is mandatory in order to create the credential.

Fill in the Mandatee fields and select at least one power in the Powers section.

Available powers

Powers may vary by organization. The following are some examples.

Function	Actions	Description
Onboarding	Execute	Allows managing the onboarding process for new participants.
Product offering	Create, Update, Delete	Allows creating, modifying and deleting product or service offerings.
Certification	Upload, Attest	Allows uploading and attesting certifications on behalf of the organization.

Save the private key before continuing

When confirming the creation, the portal asks you to check the box "I confirm that I have securely copied and saved the private key". Without it, it will not be possible to use the credential later.

Credential issued to a person (an employee of the organization). It allows them to identify themselves and prove their powers or roles within the organization to external services.

When to use it: when you want to grant access to or accredit a specific employee.

Required recipient data: first name, last name, email and employee number.

Credential issued to a machine, service or application (not to a person). It allows a system to identify itself automatically to other services.

When to use it: when you want to accredit a service or application of the organization.

Required data: the service domain and, optionally, an IP address.

The format determines how the credential is structured and protected.

• W3C VC Data Model v2.0 — Standard format and the most compatible with external services.

• SD-JWT VC — Lets the holder show only the necessary data in each presentation, without revealing the rest. Recommended when data privacy is a priority.

  → For more technical information about this format, see SD-JWT VC.

The main difference is whether a PIN is required to accept the credential.

• Authorization Code — The recipient accepts the credential directly from the email or QR code.
• Pre-Authorized Code — The recipient receives a PIN by email after logging in to the wallet, and must enter it to accept the credential.

How the offer is delivered to the recipient. The offer expires after 10 minutes.

• Email — An email with the offer is sent.
• QR code — The portal displays a QR code on screen.

Fill in the Mandatee fields, the Mandator fields and select at least one power in the Powers section.

Available powers

Powers may vary by organization. The following are some examples.

Function	Actions	Description
Onboarding	Execute	Allows managing the onboarding process for new participants.
Product offering	Create, Update, Delete	Allows creating, modifying and deleting product or service offerings.
Certification	Upload, Attest	Allows uploading and attesting certifications on behalf of the organization.

Before filling in the data, generate the private key by clicking Generate key in the Private key section. This step is mandatory in order to create the credential.

Fill in the Mandatee fields, the Mandator fields and select at least one power in the Powers section.

Available powers

Powers may vary by organization. The following are some examples.

Function	Actions	Description
Onboarding	Execute	Allows managing the onboarding process for new participants.
Product offering	Create, Update, Delete	Allows creating, modifying and deleting product or service offerings.
Certification	Upload, Attest	Allows uploading and attesting certifications on behalf of the organization.

Save the private key before continuing

When confirming the creation, the portal asks you to check the box "I confirm that I have securely copied and saved the private key". Without it, it will not be possible to use the credential later.