Employee Field Visibility Considerations and Limitations

Review these considerations and limitations for employee field visibility.

• Employee field visibility rules allow access to a field’s existing accessibility setting. If the Employee object isn’t viewable to a user, employee field visibility can’t control access to its fields. To ensure field visibility rules work as expected, make sure that any employee sharing or field-level security settings are, at a minimum, set to read-only.
• Employee Workspace doesn’t support employee field visibility rules because enabling them can lead to unwanted behavior.
• Users can search on indexed fields, even if they’re hidden. The field values are still hidden, but the relevant records appear in the search results.
• We recommend assigning only one category per field. If a field belongs to multiple data classification categories, multiple rules are created using OR logic. As a result, the most permissible rule takes effect, which can lead to unwanted behavior. To avoid this scenario, use one category per field.
• Employee field visibility rules apply to users with View All Data permissions, such as admins. To view sensitive employee data, users need the View Concealed Field Data permission.
• Employee field visibility rules still show as active in the API, but they aren’t applied.
• You can’t assign data classification categories to compound fields, like Address.
• Hiding the UserId field prevents certain features from working.
• In reports, lookup fields and values are still visible even if those fields are hidden.
• Running Apex code in system mode bypasses any employee field visibility rules.
• If you change a compliance category API name, any rules in that category no longer work. Re-enable rules in the employee field visibility setup page.