Skip to main content
The Actor Mappings page in the Matcher UI lets you associate opaque actor IDs (from JWT authentication) with human-readable information such as display name and email. This supports GDPR compliance by enabling pseudonymization and right-to-erasure operations directly from the UI.

Accessing the Actor Mappings page


Navigate to Matcher > Settings > Actor Mappings in the left sidebar.
A collapsible “What is an Actor Mapping?” helper is available at the top of the page explaining that an actor mapping associates an opaque actor ID with human-readable PII to support GDPR compliance.

Searching for an actor mapping


Matcher Actor Mappings search page, used to link an opaque actor ID with human-readable details
The page uses a search-first pattern. Enter an Actor ID in the search field and click Search to look up a mapping.
  • If a mapping exists, a result card appears with the actor’s details.
  • If no mapping is found, the page offers a Create Mapping button so you can register a new one immediately.
The search field can be pre-populated from a URL query parameter (e.g. when navigating from audit logs), allowing deep links directly to a specific actor mapping.

Result card


When a mapping is found, the result card displays:
FieldDescription
Actor IDThe opaque identifier from JWT authentication
Display NameThe human-readable name, or an em-dash if not set
EmailThe email address, or an em-dash if not set
Created atDate and time the mapping was created
Updated atDate and time of the last update
If the mapping has been pseudonymized, a yellow Pseudonymized badge appears on the card. The card provides three action buttons: Edit, Pseudonymize, and Delete.

Creating an actor mapping


Click the New Mapping button at the top of the page. A slide-over sheet opens with the following fields:
FieldDescription
Actor IDThe opaque identifier from JWT authentication (e.g. user:550e8400-e29b-41d4-a716-446655440000). Maximum 255 characters — values exceeding this limit are rejected with a 400 Bad Request validation error. Leading and trailing whitespace is automatically trimmed. Cannot be changed after creation
Display NameThe human-readable name (e.g. “John Doe”). Optional, but at least one of Display Name or Email is required
EmailThe email address (e.g. “john.doe@example.com”). Optional, but at least one of Display Name or Email is required
Click Create Mapping to save.

Editing an actor mapping


Click the Edit button on the result card. The slide-over sheet opens with the current values pre-filled. The Actor ID field is locked — only the display name and email can be modified. Click Update Mapping to apply changes.

Pseudonymizing an actor mapping


Click the Pseudonymize button on the result card. A confirmation dialog explains that this action replaces the display name and email with [REDACTED] while preserving the actor ID link. This operation cannot be undone. Confirm to proceed. After pseudonymization, the result card shows [REDACTED] values and a yellow Pseudonymized badge.
Pseudonymization supports GDPR Article 4(5) by making personal data no longer attributable to a specific individual without additional information, while keeping the structural link intact for reconciliation purposes.

Deleting an actor mapping


Click the Delete button on the result card. A confirmation dialog warns that this action removes the actor mapping in support of right-to-erasure requests, subject to retention obligations; physical removal is not guaranteed where retention is legally required. Confirm to proceed. The search state is cleared after deletion.
Deletion supports GDPR Article 17 (right to erasure) by removing the mapping between the opaque actor ID and personal data where permitted. Under Article 17(3), identifiers or audit/retention records may be retained where required for legal obligations, archiving purposes, or the establishment or defense of legal claims.