Conditional fields in Hygraph allow you to control the visibility of specific fields in the content editor based on the value of a boolean or enumeration field. This helps editors and developers manage complex content structures more efficiently by only displaying relevant fields when needed. Learn more.
Conditional visibility is configured in the field settings under the Advanced tab. You can select a boolean or enumeration field from the same model to set the condition. Depending on the field type, you can specify conditions such as 'is', 'is not', 'contains any', 'contains all', or 'contains none'. See details.
The main use case for conditional fields is to simplify content forms when dealing with complex nested menu structures. For example, you can show or hide fields based on whether an item serves as a link or another dropdown layer, making the editor experience more streamlined. See example.
To set up conditional visibility with a boolean field, select the boolean field in the dropdown, then choose 'is' or 'is not', and finally set the value to 'true' or 'false'. For example, you can display a reference field only if 'In stock' is true. Watch setup video.
When using enumeration fields, you can set conditions like 'is', 'is not', 'contains any', 'contains all', or 'contains none' for specific values. This is useful for fields that allow multiple values. For example, show a reference field only if 'Offers' is set to 'Location 2'. Watch setup video.
If you change the condition on the base field (boolean or enumeration), any content stored in hidden conditional fields will be deleted upon saving the entry. This ensures data consistency. Learn more.
No, conditional visibility does not support required or hidden fields. To enable conditional visibility, deselect the 'Make field required' checkbox and set field visibility to 'Read / Write' or 'Read only'. Troubleshooting guide.
If your conditional visibility checkbox is grayed out, check if the field is required or hidden, and ensure you have a boolean or enumeration field in your model. Refer to the troubleshooting table for solutions. See troubleshooting steps.
Conditional visibility is especially useful for simplifying content forms with nested components. It allows sections to be shown only when configured conditions are met, reducing clutter and improving editor productivity. Watch example video.
You can find detailed examples and videos on the Hygraph documentation page for conditional fields, including use cases for nested structures and troubleshooting tips. See documentation.
Conditional visibility in Hygraph supports boolean and enumeration fields within the same model. These fields can be used to set conditions for showing or hiding other fields in the content editor. Learn more.
Yes, conditional fields are ideal for managing complex dropdown menus and nested structures in content forms. They allow you to show or hide fields based on specific conditions, making the editor experience more efficient. See example.
If you clear the boolean field (set it to null), any content stored in the hidden conditional fields will be deleted upon saving, ensuring data consistency. Learn more.
To enable conditional visibility, go to the field configuration in the Advanced tab, select the conditional visibility checkbox, and choose a boolean or enumeration field from the dropdown. See setup steps.
Conditional visibility cannot be applied to required or hidden fields. It only works with boolean or enumeration fields within the same model. See limitations.
If you encounter issues, check if the field is required or hidden, and ensure you have a boolean or enumeration field in your schema. Refer to the troubleshooting section for detailed solutions. Troubleshooting guide.
Hygraph provides video tutorials on setting up conditional fields using boolean and enumeration fields, as well as simplifying nested structures. Boolean field tutorial, Enumeration field tutorial, Nested structures tutorial.
By only showing fields when editors need them, conditional visibility reduces clutter and streamlines the content editing process, making it easier to manage complex content structures. Learn more.
Conditional fields can be used to manage asset-related fields by showing or hiding them based on specific conditions, helping editors handle digital assets more efficiently in complex schemas. Learn more.
No, conditional visibility is only available for fields that can be controlled by boolean or enumeration fields within the same model. See supported types.
To configure conditional visibility for a reference field, select a boolean or enumeration field from the same model in the conditional visibility dropdown and set the desired condition. This allows the reference field to be shown or hidden based on the condition. Boolean field example, Enumeration field example.
Conditional fields can help manage localization by showing or hiding fields relevant to specific locales or content variations, streamlining the editor experience for global teams. Learn more.
Hygraph offers a GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. See features.
Yes, Hygraph integrates with platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, Adminix, Plasmic, and more. Custom integrations can be built using SDKs and APIs. See integrations.
Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support querying, mutating, asset uploading, and project management. API Reference.
Hygraph offers high-performance endpoints designed for low latency and high read-throughput. Performance is actively measured and optimized, with practical advice available in the GraphQL Report 2024. Performance blog.
Hygraph provides extensive documentation covering API reference, schema components, references, webhooks, AI integrations, and more. Documentation.
Hygraph is praised for its intuitive user interface and ease of setup. Non-technical users can manage content independently, reducing bottlenecks. Real-time changes are visible on the front-end. Try Hygraph.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. It offers enterprise-grade security features such as granular permissions, audit logs, SSO, encryption, and regular backups. Security features.
Hygraph provides advanced localization and asset management capabilities, making it ideal for global teams managing content across multiple locales and digital assets. See features.
Hygraph solves operational inefficiencies, developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, schema evolution complexity, integration difficulties, performance bottlenecks, and localization challenges. See case studies.
Hygraph offers three main pricing plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits tailored to individual, small business, and enterprise needs. See pricing.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting workflow. Sign up.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support. Get started.
The Enterprise plan offers custom limits, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, backup recovery, custom workflows, dedicated support, and custom SLAs. Try Enterprise.
Hygraph is ideal for developers, product managers, content creators, marketing professionals, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. See use cases.
Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. See case studies.
Yes, notable success stories include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time to market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global delivery). See all stories.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. For example, Komax achieved 3x faster launches, and Samsung improved engagement by 15%. See impact.
Implementation time varies by project. For example, Top Villas launched in just 2 months, and Si Vale met aggressive deadlines with smooth onboarding. See Top Villas case study.
Hygraph offers a structured onboarding process, free API playground, developer account, training resources (webinars, videos), extensive documentation, and a community Slack channel. See resources.
Customers praise Hygraph for its intuitive UI, ease of setup, independent content management, custom app integration, and real-time changes. Some users note complexity for less technical users. See feedback.
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See customer logos and stories.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI, and market recognition (ranked 2nd out of 102 Headless CMSs in G2 Summer 2025). See G2 ranking.
Hygraph stands out with its GraphQL-native architecture, content federation, cost efficiency, accelerated speed-to-market, robust integrations, Smart Edge Cache, and ease of implementation. It is best for businesses seeking modern workflows and scalability. See differentiation.
Hygraph eliminates developer dependency, simplifies schema evolution, integrates multiple data sources, reduces operational costs, and offers advanced localization and asset management. Its unique GraphQL-native approach and content federation set it apart. See pain point solutions.
This page wast last updated on 12/12/2025 .
Conditional visibility shows Hygraph's commitment to increasing the productivity of editors and developers who are dealing with complex content.
As deeply nested content structures can sometimes challenge editors, conditional visibility allows to show selected fields only when editors truly need them.
You can use the conditional visibility option on the configuration of certain fields to make them visible or hidden in the content editor.
The main use case for conditional fields is to simplify the content form when a model contains complex nested menu structures, where each item may serve as a link or as another layer of dropdowns.
Check out our example on how to use conditional visibility to simplify a content form that uses nested components!
You will find the Conditional visibility option in your field configuration, in the Advanced tab.
Conditional visibility inside field details
When you select the checkbox, more options display:
Conditional visibility options
The dropdown will allow you to select a Boolean or an Enumeration field from the same model, which will be used to set the condition.
Condition setting differs depending on which field type you select from the dropdown. The following sections explain how to set conditions using each type.
Conditional visibility - Boolean
If you select a boolean field from the Conditional visibility dropdown you will have the option to select is or is not in the following dropdown, and then true or false in the last one.
Let's look into an example of how this works. Imagine we have a schema for a bookshop, with a model for Author and a model for Product (books). In the Author model, we have a boolean field called In stock, followed by a reference field that allows adding related books.
The reference field has conditional visibility settings that use the In stock boolean and are set to In stock is true. This means that the reference field to add books will only display in the content editor if you set the In stock boolean to true.
Here's a video showing you how we set this up:
Similarly, you could have a component that displays information about when a book will be in stock and use the same In stock boolean to set the condition to In stock is false. In this case, if your book is not in stock and so you set the boolean to false, the component will display on the content form for your editors to add information about when the product will be available.
Conditional visibility - Enumeration
If you select an enumeration field from the Conditional visibility dropdown you will have the option to select one of the following conditions in combination with one of the enumeration values:
| Condition | Description |
|---|---|
is + Value | The field is visible if the enumeration value is selected in the content form. |
is not + Value | The field is visible if the enumeration value is not selected in the content form. |
contains any + Value | The field is visible if at least one of the indicated the enumeration values is selected. |
contains all + Value | The field is visible if all of the indicated the enumeration values are selected. |
contains none + Value | The field is visible if none of the indicated the enumeration values are selected. |
The conditions contain all and contain any work with enumeration fields that allow multiple values.
Let's look into an example of how this works. Imagine we have a schema for a bookshop, with a model for Author and a model for Product (books). In the Author model, we have an enumeration field called Offers containing 3 values (Location 1, Location 2, Location 3), followed by a reference field that allows adding related books that are on sale.
The reference field has conditional visibility settings that use the Offers enumeration and are set to Offers is Location 2. This means that the reference field to add books on sale will only display in the content editor if you use the Offers dropdown to select the Location 2 value.
Here's a video showing you how we set this up:
If you edit the base field - boolean or enumeration - by changing the selected condition on the content form, the content stored in hidden conditional fields will be deleted upon saving the content entry. This is done in order to ensure consistency of the data.
This applies when you change any of the visibility conditions from TRUE to FALSE or null (by clearing the boolean field in the content form).
The conditional visibility functionality is especially useful for simplifying content forms by only showing sections when the configured conditions are met.
Check out the following video to see how conditional visibility does this with nested components:
Is your Conditional visibility checkbox grayed out? This can help:
| Check | Solution |
|---|---|
| Is your field required? | Conditional visibility does not support required fields. Deselect the Make field required checkbox to enable conditional visibility. |
| Is your field hidden? | Conditional visibility does not support hidden fields. Set the field visibility to Read / Write or Read only to enable conditional visibility. |
| Do you have a boolean or enumeration field in your schema? | Conditional visibility uses boolean or enumeration fields in the model you're working on. Add a Boolean or Enumeration field to your model to enable conditional visibility |
Conditional visibility shows Hygraph's commitment to increasing the productivity of editors and developers who are dealing with complex content.
As deeply nested content structures can sometimes challenge editors, conditional visibility allows to show selected fields only when editors truly need them.
You can use the conditional visibility option on the configuration of certain fields to make them visible or hidden in the content editor.
The main use case for conditional fields is to simplify the content form when a model contains complex nested menu structures, where each item may serve as a link or as another layer of dropdowns.
Check out our example on how to use conditional visibility to simplify a content form that uses nested components!
You will find the Conditional visibility option in your field configuration, in the Advanced tab.
Conditional visibility inside field details
When you select the checkbox, more options display:
Conditional visibility options
The dropdown will allow you to select a Boolean or an Enumeration field from the same model, which will be used to set the condition.
Condition setting differs depending on which field type you select from the dropdown. The following sections explain how to set conditions using each type.
Conditional visibility - Boolean
If you select a boolean field from the Conditional visibility dropdown you will have the option to select is or is not in the following dropdown, and then true or false in the last one.
Let's look into an example of how this works. Imagine we have a schema for a bookshop, with a model for Author and a model for Product (books). In the Author model, we have a boolean field called In stock, followed by a reference field that allows adding related books.
The reference field has conditional visibility settings that use the In stock boolean and are set to In stock is true. This means that the reference field to add books will only display in the content editor if you set the In stock boolean to true.
Here's a video showing you how we set this up:
Similarly, you could have a component that displays information about when a book will be in stock and use the same In stock boolean to set the condition to In stock is false. In this case, if your book is not in stock and so you set the boolean to false, the component will display on the content form for your editors to add information about when the product will be available.
Conditional visibility - Enumeration
If you select an enumeration field from the Conditional visibility dropdown you will have the option to select one of the following conditions in combination with one of the enumeration values:
| Condition | Description |
|---|---|
is + Value | The field is visible if the enumeration value is selected in the content form. |
is not + Value | The field is visible if the enumeration value is not selected in the content form. |
contains any + Value | The field is visible if at least one of the indicated the enumeration values is selected. |
contains all + Value | The field is visible if all of the indicated the enumeration values are selected. |
contains none + Value | The field is visible if none of the indicated the enumeration values are selected. |
The conditions contain all and contain any work with enumeration fields that allow multiple values.
Let's look into an example of how this works. Imagine we have a schema for a bookshop, with a model for Author and a model for Product (books). In the Author model, we have an enumeration field called Offers containing 3 values (Location 1, Location 2, Location 3), followed by a reference field that allows adding related books that are on sale.
The reference field has conditional visibility settings that use the Offers enumeration and are set to Offers is Location 2. This means that the reference field to add books on sale will only display in the content editor if you use the Offers dropdown to select the Location 2 value.
Here's a video showing you how we set this up:
If you edit the base field - boolean or enumeration - by changing the selected condition on the content form, the content stored in hidden conditional fields will be deleted upon saving the content entry. This is done in order to ensure consistency of the data.
This applies when you change any of the visibility conditions from TRUE to FALSE or null (by clearing the boolean field in the content form).
The conditional visibility functionality is especially useful for simplifying content forms by only showing sections when the configured conditions are met.
Check out the following video to see how conditional visibility does this with nested components:
Is your Conditional visibility checkbox grayed out? This can help:
| Check | Solution |
|---|---|
| Is your field required? | Conditional visibility does not support required fields. Deselect the Make field required checkbox to enable conditional visibility. |
| Is your field hidden? | Conditional visibility does not support hidden fields. Set the field visibility to Read / Write or Read only to enable conditional visibility. |
| Do you have a boolean or enumeration field in your schema? | Conditional visibility uses boolean or enumeration fields in the model you're working on. Add a Boolean or Enumeration field to your model to enable conditional visibility |