Admin · Compliance
Route /admin/security Flag securityEnabled

Masking Policy

Persona-aware field masking and sensitive data posture for salary, bank, tax, and similar fields.

Scroll to Flowcharts. Scenario: Set persona field masking.

Persona-aware masking

Who may see salary, bank, and tax — in the UI they already use

Masking policy is persona-aware field masking and sensitive-data posture for salary, bank, tax, and similar fields. It does not invent a vault; it decides what each persona sees on existing screens.

Admin → Security settings Route /admin/security Org flag securityEnabled HR Admin · Org Admin

The job of this console

Set which personas see which sensitive fields, confirm Employee 360 and payroll screens honor the policy, and keep AI / work-graph snippets on masked summaries. Change policy here, not by forking page code.

Seat at the table

Org and HR administrators. Payroll managers still need the payroll flag and persona; masking is additional. Employees should never see others’ bank fields because a flag was left open.

The working rhythm

Open the policy, adjust a persona’s field set, save, then view the same employee as that persona. Recheck analytics and AI audit logs for raw values.

Moments that bring you here

A new finance persona. An auditor asking who can see compensation. After an AI feature ships that might echo salary. When a screenshot leaked a bank field.

ⓘ
Masking is not encryption at rest
Source tables still hold the values. This console governs presentation and derived snippets. Do not persist unmasked sensitive fields in AI audit or graph metadata.

Flowcharts

1 — Mask a sensitive field

Select a field, set VISIBLE / MASKED / HIDDEN per persona, then save.

flowchart TD
  A[Open Security] --> B[Pick a field]
  B --> C[Set persona grants]
  C --> D[Save]
  D --> E[Employee 360 / exports honor policy]
  E --> F[Audit when writes enabled]
            
  1. 1
    Open Security settingsAdmin → Security settings.
  2. 2
    Select a fieldRegistry lists sensitive attributes.
  3. 3
    Set grantsVISIBLE, MASKED, or HIDDEN per persona.
  4. 4
    VerifyOpen Employee 360 as a restricted persona.

Overview

Masking is evaluated with PersonaContextService. AI audits and Work Graph must store masked summaries only — never raw salary, bank, tax, or medical values.

How to use

1. Default to MASKED
VISIBLE should be rare outside Payroll / HR Admin.
2. Export gates
Some rules also restrict CSV/PDF export.
3. Pair with retention
Hidden fields may still exist until Data retention purges them.