Use conditions and sensitive fields

Show the right questions and protect sensitive Short Text answers from casual viewing.

Conditions change which questions a client sees. An encrypted answer is masked until a team member chooses to reveal it.

Before you start

Conditional logic and encrypted Request answers are included with current Growth and Power Team plans.
Current Core workspaces do not get these options. Some older plans and active trials do. The builder shows an upgrade message when access is not included.
Conditions work only with an earlier field in the same Request.
Only Short Text can use Encrypt Answer.

Show or hide a field

Open the Request builder.
Select the field or Section you want to control.
Open its condition settings.
Add a rule.
Choose the earlier question that controls the rule.
Choose SHOW or HIDE, an operator, and a value when needed.
Add more rules if needed. Choose whether SHOW rules use AND or OR, and do the same for HIDE rules.
Open Preview and use Test to try each answer path.

SHOW rules use AND by default. HIDE rules use OR by default. If SHOW and HIDE both match, HIDE wins.

What are the condition limits?

A field can have up to 10 conditions.
A field cannot control itself.
The question that controls a rule must come before the field being controlled.
Section cannot control another field.
An encrypted Short Text field cannot control another field.
Color, File Upload, and Signature can only test whether an answer is empty or not empty.
A condition on a Section also controls the fields inside that Section.

Hidden fields do not count toward visible progress or required-field checks. Hidden answers also stay out of the team Form and Timeline views while the rule keeps the field hidden.

Encrypt a Short Text answer

Add or select Short Text.
In the field settings, turn on Encrypt Answer.
Save the field and test the Request.

Sydnee encrypts the saved answer. Clients and team members see dots instead of the value in normal views. A team member with access to the Request can use the reveal control for that one field.

Encrypted answers are not printed in the PDF. The PDF shows a note in place of the answer. Uploaded-file ZIP files do not contain Short Text answers.

What does “private” mean here?

Private request and Encrypt Answer solve different problems.

Private request limits portal access to one selected client.
Encrypt Answer protects one Short Text answer from casual viewing.
Encrypt Answer does not make the whole Request private.

Do not treat a signature field as identity proof. Do not use these controls as proof of a law or compliance standard.

Fix a common problem

If the condition controls are locked, your plan does not include them. Ask the workspace owner to review the plan.

If a field cannot be selected as a trigger, move it above the target field and make sure it is not a Section or encrypted Short Text field.