Private Fields

Private Fields let an Administrator mark a single form field as sensitive so requesters can still fill it in, but its answer stays out of non-admin views, email notifications, exports, approval certificates, and search. Use it for answers like a bank account, a salary, or an ID number that approvers do not need to read in order to decide. The people allowed to see the content — super admins, team owners, team admins, and the workflow's owner — find it in a collapsed Private Fields section on the request and approval pages. You'll need a workflow whose form already contains the field you want to protect, open on its Form tab.

Who this is for: admin.

Mark the sensitive field Private

When a form collects something like a bank account or an ID number, you want the requester to enter it without every approver reading it — marking the field Private keeps it on the form while holding the answer back from non-admin views, email notifications, exports, certificates, and the search index. This is visibility shaping, not encryption or access control: the value still lives in the database, the requester who typed it cannot see it again on the request page, and the workflow API and Zapier payload still include private field entries.

1. Sign in as an Administrator.

2. Click the card for the field whose answer should stay hidden — the example uses Account number.

   

3. On the field's Content tab, click Advanced to open the advanced settings.

   

4. Click Private. The switch's on-screen note confirms the behavior: private fields appear on the form but are not shared with non-admin users or included in email notifications.