Form conditions
A condition watches one field and changes another. It is how a page stays short: only the questions that apply to this client appear, and the fields that must not be edited stay locked.
What a condition can do
When the rule you set is true, the affected fields can be shown, hidden, made required, made read-only, or filled with a value automatically.
Steps
- Open the conditions area of your experience.
- Pick the source field, an operator and the value that should trigger the rule. For example: Type equals Company.
- Choose the affected fields and the action for each one.
- Preview both paths, one where the rule matches and one where it does not.
Good to know
- Fields inside a hidden section are not submitted, so required fields in them will not block the client.
- Keep each rule readable. One source field and a short list of affected fields is easier to debug later than a chain of nested rules.
- Check the phone layout after adding a rule, since page length changes for each path.
Related tutorials
Keep going with these lessons.

Push Data to Your CRM and Attach the PDF
Send a submission into your CRM, map each field, and attach the signed PDF to the record.
Doc TemplatesIntegrations

Guard Sign-In
Ask visitors to identify themselves before a document or Experience opens.
Doc TemplatesExperience Builder

Advanced set value
Keep a copied value in sync with its source, and write into variables.
Doc Templates
