Overview
When you make a field mandatory in the CRM, it affects record creation differently than it does webform submissions. Understanding this distinction is important for ensuring complete data collection across all entry points.
How CRM Mandatory Fields Work
When you set a field as mandatory in a CRM module (such as Leads), it prevents record creation if that field is empty. This applies to:
Manual record creation by staff
Records created through forms and integrations
Records created via webhooks
Other automated record creation methods
Webforms Require Separate Configuration
Making a field mandatory in the CRM does not automatically make it required on webforms. Webform requirements must be configured separately.
For webform submissions to require a field, you need to:
Set the field as required directly on the webform itself.
Configure the requirement on your website form.
Ensure both the CRM requirement and the webform requirement are enabled
Why Both Settings Are Needed
The CRM requirement and webform requirement work independently:
CRM Requirement: Prevents incomplete records from being saved in the system
Webform Requirement: Ensures visitors complete the field before submitting the form
Without both settings configured, you may experience scenarios where webforms submit successfully, but records cannot be created in the CRM due to missing mandatory information.
Best Practices
✅ Configure both requirements: Set fields as mandatory in both the CRM and on webforms for complete data collection.
✅ Test your webforms: After making CRM changes, test webform submissions to ensure they still process correctly.
✅ Coordinate with web team: Ensure website administrators know when CRM field requirements change so they can update webforms accordingly.
Related Resources
For more information on field configuration and webform mapping, see:
How to Map Webform Fields From CTM to Dazos (CRM)
How to Edit Fields in a Record (CRM)
Module Layouts & Fields configuration guides