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

Restrict access to sensitive personnel information

Protect confidential personnel data by marking skill files and custom fields as sensitive. Sensitive items are only available to users whose role has the matching sensitive-content permissions. Everyone else cannot open a sensitive skill file, and sees Restricted content in place of a sensitive custom field value.


Before you start

Access to sensitive personnel data is governed by dedicated permissions, set per role in Company settings > Permissions. There are two independent groups: one for skill attachments and one for custom fields.

Note: These permissions apply only to items that have actually been marked sensitive. A skill file or custom field that is not marked sensitive behaves exactly as before and is governed by the normal personnel permissions.


Sensitive skill attachments

A skill file is marked sensitive with the Sensitive checkbox in the Skills section of a personnel record. Each action on a sensitive skill file is gated by its own permission:

 

Permission

What it allows for a sensitive skill

Read sensitive skill attachments

View and download the file. Without it, the skill still appears in the list but the file cannot be opened or downloaded.

Create sensitive skill attachments

Upload or attach a file to a skill that is marked sensitive.

Update sensitive skill attachments

Tick or clear the Sensitive checkbox, that is, mark a skill sensitive or remove the sensitive flag.

Delete sensitive skill attachments

Remove or delete the file from a sensitive skill.

 

Important: Creating a sensitive skill attachment from scratch needs both Create and Update. You use Update to tick the Sensitive checkbox, and Create to upload the file to it. A role with only one of the two cannot complete the task: with Update but not Create you can mark the skill sensitive but not attach the file; with Create but not Update you can attach a file but not mark it sensitive.

Add a sensitive skill file

  1. Open the personnel record and go to the Skills section.
  2. Tick Sensitive on the skill row. (Requires Update sensitive skill attachments — the checkbox is otherwise greyed out.) The tooltip reads: "When enabled this file will only be visible to roles with sensitive content access."
  3. Upload the file for that skill. (Requires Create sensitive skill attachments.)
  4. Save. The skill now shows as a Restricted file.

Note: WINDA-synced skills are managed by the integration, so their sensitive setting and file cannot be edited here.


Sensitive personnel custom fields

A custom field is marked sensitive on its template, in Company settings > Personnel > Custom fields. Two permissions govern sensitive custom field values:

 

Permission

What it allows

Read sensitive custom fields

See the value of a sensitive custom field. Without it, the value shows as Restricted content.

Update sensitive custom fields

Change the value of a sensitive custom field.

 

Important: To set, change, or import a sensitive custom field value, a role needs both Read and Update sensitive custom fields. This is deliberate: a user who cannot see a value must not be able to overwrite it, so Update on its own is not enough without Read.

Mark a custom field as sensitive

  1. Go to Company settings > Personnel > Custom fields.
  2. Add or edit a custom field. Use Add custom field to create a new one.
  3. Enable Sensitive on the field.
  4. Save.

From then on, only roles with Read sensitive custom fields can see the value; everyone else sees Restricted content, and only roles with both Read and Update sensitive custom fields can change it.


Where the protection applies

Marking an item as sensitive protects it everywhere the data is shown or moved, including:

  • Employee lists
  • The resource calendar
  • Lookups
  • Exports
  • Imports

Note: During an import, a sensitive custom field is skipped for users without the required permissions: "This is a sensitive field. It will be ignored during import because you don't have permission to update sensitive custom fields." This prevents a value you cannot see from being blanked on import.