Visibility Rules

Visibility rules conditionally show or hide individual fields based on prior answers or external data. Unlike navigation rules (which control page routing), visibility rules operate within a single page to dynamically adjust which fields the candidate sees.

How They Work

An admin attaches a visibility rule to a specific field
When the page loads, the platform evaluates the rule’s condition tree
If the rule evaluates to true, the element is shown
If the rule evaluates to false, the element is hidden

Common Use Cases

Scenario	Example
Conditional fields	Show “Spouse Name” only if marital status is “Married”
Role-specific questions	Show “CDL Number” only if position type is “Driver”
Document requirements	Show “Work Permit Upload” only if citizenship is not the hiring country
Age-based sections	Show “Guardian Consent” only if the candidate is under 18
Follow-up detail	Show “Please explain” only if the candidate selected “Other”

Condition Building

Visibility rules use the same condition tree system as decision rules:

Field conditions comparing form answers, application status, or profile data
Logical operators (AND, OR, NOT) for combining conditions
Dynamic data paths for referencing values anywhere in the Object Graph

Key Differences from Decision Rules

Aspect	Decision Rules	Visibility Rules
Scope	Page-level — evaluated after page submission	Element-level — evaluated when the page renders
Effect	Controls navigation (which page or stage comes next)	Controls display (show or hide a field)
Timing	After submission	Before submission (on page load)

Getting Started

Features

Settings

How They Work

Common Use Cases

Condition Building

Key Differences from Decision Rules

​How They Work

​Common Use Cases

​Condition Building

​Key Differences from Decision Rules

How They Work

Common Use Cases

Condition Building

Key Differences from Decision Rules