FIELD FEATURES

Visible, Hidden and Internal fields

Choose Logical Forms field visibility, distinguish hidden browser values from server-owned Internal values, and understand summaries and conditions.

2 min read · Updated November 19, 2026

Where supported, Advanced → Visibility controls whether a field is shown publicly, hidden in the public form, or kept Internal. This is separate from conditional logic, which decides whether a question applies to the current answers.

Choose a visibility mode

Mode Public form Value behavior
Visible Normal public controls Ordinary input and validation
Hidden Controls remain in a hidden public wrapper Values remain browser-supplied and can be inspected or changed
Internal No public controls or source metadata The server uses configured defaults or trusted extension values

The builder keeps cards visible with a badge so you can configure them. Saved Preview follows public presentation even when an administrator opens it. Changing visibility does not erase historical entry answers.

Use Hidden for presentation

A hidden question can carry a source value, default or other browser input without displaying it. It is not a place for credentials, permission decisions or values the visitor must not alter. The dedicated Hidden field type also collects a hidden string, with its own smaller settings set.

Hidden Required remains a data requirement. Provide a valid initial value if the visitor cannot fill the field visibly. Failures use general feedback because an invisible control cannot offer a useful focus target.

Use Internal for server-owned values

Internal values are entry-only on the public surface, including for a signed-in administrator. They do not add a role selector or a public staff-editing control. Public input cannot replace an Internal value; the server uses its configured default or trusted integration behavior.

Internal fields skip submission Required checks that a visitor cannot satisfy, while nonempty values still undergo their ordinary format validation. Dashboard/API permissions remain unchanged. The Pro dashboard editor keeps Internal values read-only.

Conditions and population

A statically hidden field can be a conditional source while applicable. If its conditions deactivate it, its answer is cleared/excluded under the normal conditional policy.

Internal fields are not public rule sources or targets, and public dynamic population is ignored. Existing rule configurations are retained if a field changes mode, but references to an Internal source do not match. Review dependent rules when changing visibility.

Entries and output summaries

Authorized entry management can still display saved Hidden and Internal answers. A notification's automatic all-fields summary omits Internal fields but can include Hidden answers. A visitor confirmation's summary excludes Hidden and Internal values, as well as uploaded files.

An explicit field merge tag can deliberately include an otherwise excluded value. Review message templates for their audience: visibility is not output encryption. See merge tags and conditional field logic for the related behavior.