Internal fields allow team members to store and manage internal information that is never visible to clients.
These fields can hold notes, files, checklists, or other details that help streamline workflows. Unlike standard fields, internal fields do not contribute to client to-do lists or completed task counters.
How to enable internal fields
To enable internal fields, activate the Internal use only option in the right bar when editing a given field:
| Note: Any field type except ID Verification can be marked as an internal. |
Internal fields can be helpful in various scenarios, such as:
- Tracking internal tasks – Use a checklist to manage onboarding steps outside of Content Snare
- Storing internal files – Keep internal documents related to a client (e.g., agreements, internal notes, or audit files)
- Conditional logic control – Use internal fields to show or hide sections within a request, creating a more tailored experience for clients
Internal field options
Values stored in internal fields can be confidential, meaning they require a password to unlock and access:
You can also add internal comments to these fields, but only team members can view them. In addition, internal fields support instructions, just like regular fields.
In case an entire section consists only of internal fields, the system will not display it to the client. However, if the section contains instructions, it will still be shown to the client with a Next button, acting as an instruction block.
Conditional logic and internal fields
It is also possible to use internal fields to set conditions in conditional logic, but with some key considerations.
Since clients never receive internal field values, the hidden/shown status of related fields is determined only when a team member views or edits the request. Clients will only see the last saved version of a request, reflecting the latest conditional logic status. If an internal field is linked to both an internal and a standard field, the logic still runs only when a team member updates the request.
For example, a team member might create an internal field with checkboxes like:
- Owns a company
- Owns crypto
- Owns a house
Based on these selections, the system is able to dynamically show or hide sections related to those topics. The client will only see a personalized version of the request without knowledge of the internal selections.
Related post: