Skip to content
  • There are no suggestions because the search field is empty.

PII Admin Settings

The Knowledge Anywhere LMS supports PII settings, allowing obfuscation of data for specific admins

PII Access on Admin Profiles

The Personal Identifiable Information "PII" feature toggle is visible by Admins when editing admin profiles and is disabled by default for new admins. The ability to set the toggle is dependent on the Admin Access level.

When enabled: Admins can see learners’ first name, last name, and email on the Learner Search results page. (These details are always visible when editing an individual learner.)

Names and information will be obfuscated by asterisks (*) with the first and last characters being visible. EX: Johnson will appear as J*****n

PII Access on Custom User Fields

PII settings can also affect Custom User Fields, displaying or obfuscating them depending on the check.

  • Admins with PII access enabled on their admin profile: see the actual value and can edit it (subject to their role permissions).

  • Admins without PII access (PII unchecked on their admin profile): see the value obfuscated everywhere and the field is read-only, even if their role would otherwise allow editing.

A custom User Field will need to be set as PII while editing. Activating the PII toggle will obfuscate the field based on Admin configuration.

The "i" will read, "Marks this custom field as PII. Admins without PII access will see the value obfuscated and cannot edit it; admins with PII access will see the actual value."

Dropdown fields (important limitation)
For dropdown-type custom fields marked as PII, all option labels are obfuscated for admins without PII access. Options can still be selected/used, but names/labels aren’t shown. It’s not possible to obfuscate only the selected value while leaving the other options visible.

Admin areas that are affected by PII settings

  • Reports: all reports, including running, filtering, and downloading.

  • User Profile: viewing/fetching profile (incl. custom fields) and updating users (custom fields, state, country, domain).

  • Groups: fetching/viewing group custom fields.

  • Reg Codes: any views/flows that surface custom fields.