Administrators build create and edit forms from eligible object properties and can show association fields only when configured conditions are met.

Build a form

1. Open the object in https://app.woodsportal.com.
2. Open Views, then Form.
3. Add eligible properties from the field palette.
4. Arrange the fields in the required order.
5. Configure required and supported field behavior.
6. Save the form and test it with the intended role.

Add a conditional association field

1. Add the supported association field to the form.
2. Choose the related object and association behavior.
3. Configure the condition that controls when the association field appears.
4. Save the form.
5. Test both a condition that hides the association field and one that displays it.
6. When displayed, select an authorized related record and submit the form.

Rules

• Only eligible visible or editable properties should be used for the relevant form action.
• The portal user still needs object and association permissions.
• Validation follows the field, pipeline, and association configuration.
• A conditional association field should not be treated as visible in every form state.

Edit labels and use conditional logic

• Replace internal field labels with clear customer-facing labels where the form builder supports label editing.
• Use supported conditional rules to show a field or association only when its controlling value requires it.
• Test every condition branch, including the state where the field is hidden.
• Confirm that required-field rules do not block submission when a conditional field is hidden.

Figure: Build a record-creation form from HubSpot properties and associated objects.