Skip to main content

Managing Identities

An Identity is what the UI calls a wallet. This page covers creating one, touring its dashboard, and completing trust framework onboarding.

Creating an identity​

Open Create Wallet either from the 🪪 icon on an Identity Template row, or from the Dashboard. Fill in:

  • Wallet Name (required)
  • Configuration Template (required) — pick from your saved Identity Templates.

Click Create Wallet. You're taken straight to the new wallet's dashboard at /identities/{id}.

The Dashboard is your wallet list​

Your identities live on the main Dashboard (not a separate "wallets" page):

  • A search box ("Search identities…") filters by name.
  • Bookmarked identities are shown first in their own group; everything else is under "Other Identities" (or "All Identities" if you have no bookmarks). This section auto-expands when there are no bookmarks yet, or while you're actively searching.
  • Each identity is shown as a card: name, a chip for its trust framework, and a chip for each capability it has (holder, issuer, verifier). A bookmark toggle sits on the card; click a card to open its dashboard.

The wallet dashboard​

Opening an identity takes you to /identities/{walletId}, which is the hub for everything you'll do with that wallet.

A breadcrumb (Dashboard › wallet name), a bookmark toggle, and a "⋮" menu with:

  • Edit identity
  • Configure issuers
  • Configure verifiers
  • Configure interactions
  • Configure trust framework (hidden for NOOP wallets)
  • Edit raw config
  • Delete identity

Identity info panel​

Shows the wallet's trust framework and copyable identifier (its DID or certificate), plus framework-specific status and actions — see Trust framework onboarding below. Two buttons are always present here: Accept and Present — these are the wallet's holder actions, covered in Accepting Credentials.

Interactions panel​

Two side-by-side cards, Issuers and Verifiers, listing every role configured for this wallet (from its template or from Configure interactions). Click an issuer row to start issuing that credential type (Issuing Credentials); click a verifier row to start a verification request (Verifying Credentials).

Credential tabs​

  • Held Credentials — always shown; what this wallet has received as a holder.
  • Issued Credentials — shown if the wallet has issuer capability.
  • Verification Results — shown if the wallet has verifier capability.

See Displaying Credentials for what you'll see inside each.

WMP Connections​

A section listing this wallet's WMP peer connections (Name / Roles / Status), with a Create verified connection button to start a new one. See Accepting Credentials for the connection flow.

The menu actions in detail​

  • Edit identity — change the wallet's name and its OIDC4VCI/OIDC4VP draft settings.
  • Configure issuers / Configure verifiers — add, edit, or remove issuer/verifier definitions on this specific wallet (the same form used inside Identity Templates — see Identity Templates).
  • Configure interactions — assign which Credential Type plays which issuer/verifier role for this wallet; this is what populates the Interactions panel.
  • Configure trust framework — edit the EBSI/EUDI/IDTL-specific configuration block.
  • Edit raw config — opens the full configuration as JSON, for advanced/bulk edits.
  • Delete identity — asks you to confirm ("Are you sure you want to delete {name}? This action cannot be undone.") before permanently removing the wallet and its data.

The floating Nexus Assistant is scoped to this wallet when opened from here — it can open the issuance or verification dialogs on your behalf. See The Nexus AI Assistant.

Trust framework onboarding​

A wallet on a non-NOOP trust framework must complete onboarding before it can issue credentials (holding and presenting work regardless). The Identity Info panel shows exactly what's outstanding.

NOOP​

No onboarding required — the wallet is ready to issue and verify as soon as its issuer/verifier definitions are configured.

EBSI​

The panel shows a DID Registry status chip: Onboarded or Needs onboarding (with an external link to view the entry in the DID Registry once onboarded), and an EBSI Roles row showing which of RTAO / TAO / TI accreditations the wallet holds (a TI chip links out to the Trusted Issuers Registry).

Recall from Introduction & Core Concepts that onboarding (registering the DID) and accreditation (gaining the right to act as RTAO/TAO/TI) are separate steps, and every wallet in the chain needs both:

  • An RTAO (Root Trusted Accreditation Organisation) obtains its onboarding credential directly from the EBSI conformance issuer, then onboards.
  • A TAO or TI receives its onboarding credential as an offer from its parent wallet (issued via the parent's reserved ebsi_issuer_authorization_to_onboard issuer), accepts it like any other credential offer, then onboards.
  • Accreditation works the same way one level up: the parent issues an accreditation credential via its reserved ebsi_issuer_accreditation_to_attest issuer.

For wallets that already hold RTAO/TAO accreditation, the panel exposes Authorize & Accredit and Revoke Accreditation buttons, letting you grant or withdraw a child wallet's accreditation directly from the UI instead of the raw API flow.

If the wallet is x509-identified, an X.509 Certificate row shows Installed or Not installed; Trusted Issuer wallets get an Acquire button to request one.

EUDI​

The panel shows certificate status: Certificate installed, or one of two setup actions depending on the wallet's role — Create Root Trust (for onboarding-authority wallets that anchor a trust chain) or Receive x509 Certificate (for holder wallets waiting on a certificate from their issuing authority).

IDTL​

The panel shows one of: Onboarded, Needs onboarding, or Needs X.509 certificate. A status of "Needs X.509 certificate" links to AcceptIdtlIdentityCredential — accept the certificate/credential offered by your onboarding authority the same way you'd accept any other credential offer (see Accepting Credentials).

Continue to Displaying Credentials.