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.
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
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
Org flag securityEnabled
HR Admin · Org Admin
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.
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.
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.
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.
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]
Masking is evaluated with PersonaContextService. AI audits and Work Graph must store masked summaries only — never raw salary, bank, tax, or medical values.