Skip to main content

Profiles

Profiles filter your Procivis One Desk application, allowing you to work within specific regulatory or operational frameworks with confidence. When you activate a profile, it ensures that everything you create and see aligns with that framework's requirements, eliminating guesswork around technical compliance.

You can switch between available profiles at any time, allowing you to move seamlessly from one regulatory context to another as your needs change.

How profiles work​

Profiles automatically configure the application to work within specific regulatory or operational frameworks by controlling what you can create and what you can see. This filtering happens at multiple levels — determining which technologies and standards are available, ensuring you are using the correct versions of those standards, and applying the specific configuration settings required for that regulatory context.

When a profile is active, it affects different types of assets in distinct ways: some assets are filtered by compatability with the active profile while other assets become permanently associated with the profile that was active during their creation.

Assets filtered by compatibility​

When a profile is active, the Desk only shows you:

  • Compatible options for creating new assets
  • Existing assets which are compatible with the profile

For example, when you create a new key, only algorithms compatible with the profile are shown. When you look at already created keys, only keys created with compatible algorithms are shown.

When you have no profile selected, all possible key algorithms are shown and all created keys are shown, regardless of algorithm.

Assets with permanent profile association​

When you create a credential or a proof request, the active profile goes a step further by being permanently attached to the credential or proof request. This means that when you have a profile active and you look at credentials or proofs, you only see the ones that were issued or requested while the profile is on.

This is different from other assets such as keys, identifiers, or schemas, which are shown if they are compatible with the active profile, whether they have been used with that profile or not.

Example profiles​

Profiles are custom-built to reflect the needs of particular contexts; the profiles available in your Desk application may differ from ones shown here.

EUDI​

The EUDI profile reflects the architecture of the eIDAS 2.0 regulatory framework.

swiyu​

The swiyu profile reflects the architecture of the Swiss e-ID Public Beta.

ISO mdoc​

The ISO mdoc, or ISO mDL, profile reflects the architecture of the ISO/IEC 18013-5 standard for mobile driving licenses and other credentials using the mdoc credential format.

Country profiles​

eIDAS 2.0 allows for each Member State to use subsets of the total supported architecture. A country profile applies the context of a particular country's implementation, allowing you to easily switch between interacting with wallets from one country to interacting with wallets from another country.

Your implementation​

Since profiles can be custom-built to suit particular contexts, it is important to understand what your Desk application supports.

See if profiles are enabled​

If you are using the Desk application and profiles are enabled, you will see a drop-down menu in the upper-right of your screen.

Using the API?

Retrieve the configuration and check the frontend object:

{
  "frontend": {
    "profilesEnabled": true
  }
}

See available profiles​

If using the Desk application and profiles are enabled, the profiles drop-down will show you all available profiles.

Using the API?

Retrieve the available profiles with GET on /api/config/profile/v1

Disable profiles​

To disable profiles in your Desk application, adjust the frontend configuration in your application.yml:

frontend:
  profilesEnabled: false