Announcing the ability to make fields required for custom objects

Announced on | Rollout starts | Rollout ends
January 13, 2026 | January 13, 2026 | January 16, 2026

Zendesk is excited to introduce the ability to configure fields as required for custom object records.

This announcement includes the following topics:

What is changing?

Why is Zendesk making this change?

What do I need to do?

What is changing?

When admins are creating or updating a custom object, they can now mark any of the custom object's fields as required.

Required custom object fields are treated the same as required fields on standard Zendesk objects. Any of the custom object's records that are created or updated after the field becomes required can't be saved without a value in all required fields.

Why is Zendesk making this change?

Zendesk realizes that there is essential data for you to capture in your custom object records. This change makes it possible for admins to identify the must-have data and enforce its presence for all records. It enforces completeness, enhances data quality, and increases consistency. Having more complete and consistent data also makes it possible to deliver more reliable insights when reporting on your custom data.

What do I need to do?

This feature is available to all plans with custom objects. You can edit a custom object's fields at any time to mark them as required. See Defining a custom object's schema with custom fields.

If you have feedback or questions related to this announcement, visit our community forum where we collect and manage customer product feedback. For general assistance with your Zendesk products, contact Zendesk Customer Support.