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.
Actor mappings list by actor ID prefix. Encrypted PII (display name and email) is only loaded through detail operations — it is never shown in the list.

​
Browsing actor mappings

Matcher Actor Mappings page, used to link an opaque actor ID with human-readable details

Figure 1. Actor mappings page.

The page shows a paginated table of mappings: Type in the Actor ID prefix field to filter the table live — there is no separate search button. Use the Previous / Next buttons below the table to page through results.
Display name and email do not appear in the table. Encrypted PII is loaded only when you open a mapping’s detail operations, such as editing.

​
Permissions

The row actions and the header button are permission-gated:
  • New mapping requires write permission.
  • Edit requires both write and deanonymize permission — editing loads the decrypted PII, and without deanonymize permission the load is rejected.
  • Pseudonymize and Delete each require their own permission.
Buttons you lack permission for are hidden.

​
Creating an actor mapping

Click the New mapping button in the page header. The New actor mapping sheet opens with the following fields: Click Save.

​
Editing an actor mapping

Click Edit on a mapping row. The Edit actor mapping sheet opens with the current values pre-filled. The Actor ID field is locked — actor ID cannot be changed after creation; only the display name and email can be modified. Click Save to apply changes.

​
Pseudonymizing an actor mapping

Click Pseudonymize on a mapping row. The Pseudonymize actor mapping? confirmation dialog warns: “This changes audit deanonymization behavior. Continue only if this is intentional.” This operation replaces the display name and email with [REDACTED] while preserving the actor ID link, and cannot be undone. Click Pseudonymize to proceed.
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 Delete on a mapping row. The Delete actor mapping? confirmation dialog warns: “This changes audit deanonymization behavior. Continue only if this is intentional.” Click Delete to proceed.
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.