Overview
Visitor sign-in flows can often collect information that shouldn’t be visible to everyone with dashboard access, such as passport numbers, driver’s license numbers, dates of birth, or a production name that only security should see. Sensitive fields let admins mark individual sign-in fields as sensitive. Only people with the right permission can see those values.
Envoy still collects the data as usual. The sensitive setting controls who can see the response in the dashboard, exports, and analytics.
How sensitive fields work
Set per field, per sign-in flow. Marking a “Passport number” field as sensitive in a Contractor flow does not mark it as sensitive in a Candidate flow. They share the same field name but have separate settings. If several flows collect the same information, you'll need to configure it for each flow.
Visible only with permission. By default, only Global admins can view sensitive field values. Other admins can access it through a custom role.
Masked everywhere else. For anyone without permission, sensitive values are hidden in the visitor log, the invite log, individual entry and invite pages, the History log, exports, and analytics.
Configuring sensitive fields
Navigate to Visitors > Settings > Sign-in flows.
Click Edit on the desired visitor type.
Click on the Sign-in fields tab.
Click on Field options.
Navigate to Sensitive fields.
Use the drop-down to select the fields you want to conceal and mark as sensitive.
Click Save, then Confirm to finish enabling sensitive fields for this sign-in flow.
Repeat for every sign-in flow with information you want to mark as sensitive.
Adding sensitive fields to badges
While we don't recommend adding sensitive fields to badges, certain workflows may require it.
You can add a sensitive field to a badge the same way as any other field.
Navigate to Visitors > Settings > Sign-in flows.
Click Edit on the desired visitor type.
Click on the Badge tab, then click Edit next to Badge display.
Use the drop-down under Custom field to select the sensitive field.
Click Save, then Confirm you want to add a sensitive field to a badge.
Using Sensitive fields
Visitor and Invite log
Admins with permission see sensitive values masked by default and can click the reveal icon to show them.
Admins without permission see the value masked, with no option to reveal it.
These same rules apply to the History log and Event log.
With permissions


Without permissions


Author exceptions
Location and front desk admins can sign visitors in using the web dashboard. If they sign a visitor in and the sign-in flow includes a sensitive field, they can continue to see that field after sign-in. This does not apply to pre-registered visitors an admin signs in, only walk-up entries manually created by the admin.
Host notifications
Sensitive field values are not included in host notifications for anyone other than Global admins or those with custom roles including the sensitive fields permission.
Exporting sensitive fields and analytics
Anyone who can export visitor data can select sensitive fields. However, when the export runs, Envoy checks permissions.
Admins with permission receive the values.
Admins without permission receive the column title in their report, but the values are redacted.
Envoy checks permissions each time an export runs, so the same saved export template can produce different results depending on who runs it.
When an export or scheduled report includes sensitive fields, a confirmation warning appears before you continue.


By continuing, the person exporting or scheduling the report accepts responsibility for how they share that data.
Analytic dashboards also redact sensitive fields for anyone without permission, appearing as null.
Granting access to sensitive fields
By default, only Global admins have the Access sensitive fields permission. To give access to anyone else, such as a compliance or security team, add the permission to a custom role. This permission is available on company-wide and location-level roles.
Navigate to Manage > Roles.
Create a new role or edit an existing one.
Under Visitors permissions, enable Access sensitive fields.
Save, then assign the role.














