An internal field is a question only your team can see. You add it in the request builder like any other field, then switch on a single setting. Clients never see an internal field, or anything you put inside it.
Use internal fields to keep team-only information next to a client's answers in the same request:
- Team checklists and notes
- Files for your team, such as agreements or working papers
- Classifications and review outcomes
- An internal answer that decides which sections a client sees
Make a field internal
- Open Requests.
- Choose Edit on the request or template you want to change.
- Select the field you want to hide from the client. Its options appear beside it.
- Turn on Internal use only to make the field team-only.
You can make almost any field internal. The two exceptions are the KYC / AML field and the Calendly field, where the toggle isn't shown. ABR verification is a separate field type from KYC / AML, and you can make it internal.
Internal fields don't count toward the client's progress
Adding internal fields never changes how complete a request looks to your client. They stay off the client's to-do list, and they don't add to the completed count. So you can add as many as your team needs without making a request look unfinished.
Use an internal field to show or hide client sections
If every field in a section is internal, the section itself is hidden from the client. The exception is when the section has its own instructions: in that case, the client sees those instructions with a Next button but no fields.
An internal field's answer can decide which sections a client sees. For example, an internal checklist with boxes for Owns a company, Owns crypto and Owns a house can reveal the matching topic sections, so each client only sees the parts that apply to them. They never see the checklist itself.
To build the condition, see show and hide sections with conditions.
Exports include internal content by default
Marking a field internal hides it from clients in the request, but doesn't remove it from exports. Internal fields and internal comments are both included by default in the export options, and can also be sent to a connected cloud storage integration. To exclude them from an export or sync, turn those options off first.
Make an internal field confidential
You can also make an internal field confidential, which locks its value behind a password. It's a separate Confidential toggle in the same field options, so one field can be both internal and confidential. Not every field type can be made confidential. See confidential fields to set it up.