# Allow conditional required properties on record creation only

**URL:** <https://community.hubspot.com/t/allow-conditional-required-properties-on-record-creation-only/155886>\
**Category:** HubSpot Ideas\
**Tags:** properties\
**Created:** [August 12, 2026, 10:56am UTC](https://community.hubspot.com/t/allow-conditional-required-properties-on-record-creation-only/155886 "2026-08-12T10:56:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anetthorvath](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/anetthorvath/32/226808_2.png) [@anetthorvath](https://community.hubspot.com/u/anetthorvath)\
**Post date:** [August 12, 2026, 10:56am UTC](https://community.hubspot.com/t/allow-conditional-required-properties-on-record-creation-only/155886/1 "2026-08-12T10:56:06Z")

</div>

**TL;DR:** Conditional property logic currently applies to both record creation and record editing. We would like the ability to make a property conditionally required only during record creation, while allowing existing records to be edited without requiring the dependent property.

We use conditional property logic to make certain properties required based on the value of another property.

**Example:**

- When creating a Company record and a specific property value is selected, an additional property should be required.
- After the record has been created, users should be able to edit the record without being forced to complete that dependent property.

Currently, conditional required properties are enforced during both record creation and record editing, including bulk edits.

This creates challenges for organizations that want to:

- Ensure data quality during record creation
- Allow users to update existing records without being blocked by unrelated mandatory fields

We would like the ability to configure conditional properties separately as:

- Required on record creation only
- Required on record update only
- Required on both record creation and record update

**Business impact**

This would provide much greater flexibility for CRM governance and data quality management. It would allow admins to enforce data collection when records are created, while avoiding unnecessary friction when users update existing records later in the lifecycle.

**A common use case** is requiring a property when a record is created, but allowing users to update other fields later without being blocked by the missing value.