Frequently Asked Questions

Conditional Fields & Schema Configuration

What are conditional fields in Hygraph and how do they work?

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 within the same model. This feature helps editors and developers manage complex, deeply nested content structures by only displaying relevant fields when certain conditions are met. For example, you can configure a reference field to only appear if a boolean field (like "In stock") is set to true. Note: Conditional visibility is only available for fields that are not required or hidden, and requires the presence of a boolean or enumeration field in your model. Learn more in the documentation.

How do I configure conditional visibility for a field in Hygraph?

To configure conditional visibility, open the field configuration and navigate to the Advanced tab. Enable the "Conditional visibility" checkbox. You can then select a boolean or enumeration field from the same model to set the condition. For boolean fields, you can choose "is" or "is not" and set the value to true or false. For enumeration fields, you can select conditions like "is", "is not", "contains any", "contains all", or "contains none" with specific values. Note: Conditional visibility cannot be enabled for required or hidden fields. See the official guide.

What are some practical examples of using conditional fields in Hygraph?

One example is a bookshop schema with an "Author" model containing a boolean field "In stock" and a reference field for related books. The reference field can be set to only appear if "In stock" is true. Another example uses an enumeration field "Offers" (e.g., Location 1, Location 2, Location 3) to display a reference field for books on sale only when "Offers" is set to a specific value like "Location 2". These configurations simplify content forms for editors working with nested or complex data. Note: Changing the base field value will delete content in hidden conditional fields upon saving, to maintain data consistency. See more examples.

What limitations or troubleshooting steps should I be aware of when using conditional fields?

Conditional visibility cannot be enabled for fields that are required or hidden. To enable it, deselect the "Make field required" checkbox and ensure the field is set to "Read / Write" or "Read only". Additionally, your model must include a boolean or enumeration field to use as the condition. If the conditional visibility checkbox is grayed out, check these requirements. Note: Editing the base field (boolean or enumeration) and changing its value will delete any content stored in hidden conditional fields upon saving. See troubleshooting guide.

Features & Capabilities

What are the key features of Hygraph for content management?

Hygraph offers a GraphQL-native architecture, content federation to integrate multiple data sources, enterprise-grade security and compliance (SOC 2 Type 2, ISO 27001, GDPR), Smart Edge Cache, localization, granular permissions, and a user-friendly interface for non-technical users. It also provides high-performance endpoints, extensive integration options, and structured onboarding and support. Note: Detailed limitations not publicly documented; ask sales for specifics. See feature details.

What integrations does Hygraph support?

Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting and deployment platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and others like Adminix and Plasmic. For a full list, visit the Hygraph Marketplace. Note: Integration capabilities may vary by plan and use case.

Does Hygraph provide APIs for content management and integration?

Yes, Hygraph provides several APIs: the GraphQL Content API for querying and manipulating content, the Management API for handling project structure, the Asset Upload API for uploading files, and the MCP Server API for secure communication with AI assistants. Each API is documented in detail in the API Reference. Note: API usage and limits may depend on your subscription plan.

Use Cases & Benefits

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. It is suitable for industries such as SaaS, eCommerce, media, healthcare, automotive, fintech, education technology, and more. Its flexibility and scalability support a wide range of content management and digital experience needs. Note: Teams with highly specialized legacy requirements may need to evaluate fit. See case studies.

What business impact can customers expect from using Hygraph?

Customers have reported faster time-to-market (e.g., Komax achieved 3x faster launches), improved customer engagement (Samsung saw a 15% increase), cost reduction, enhanced content consistency, and scalability. For example, Voi scaled multilingual content across 12 countries and 10 languages, and AutoWeb increased website monetization by 20%. Note: Results may vary based on implementation and use case. See more success stories.

Product Performance & Security

How does Hygraph ensure high performance for content delivery?

Hygraph offers high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint provides 3-5x latency improvement, and the platform actively measures GraphQL API performance, sharing best practices in the GraphQL Report 2024. Note: Actual performance may depend on project complexity and integration choices. Read more about performance improvements.

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. The platform also supports granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, and secure API policies. Note: For highly regulated industries, confirm specific compliance requirements with sales. See security details.

Implementation & Support

How long does it take to implement Hygraph and how easy is it to start?

Implementation time varies by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph offers structured onboarding, starter projects, extensive documentation, and community support to help users get started quickly. Note: Large-scale migrations may require additional planning. See onboarding resources.

What technical documentation and resources are available for Hygraph users?

Hygraph provides comprehensive API reference documentation, guides on schema components and references, getting started tutorials, integration guides (e.g., Mux, Akeneo, Auth0), and AI feature documentation. Classic documentation is available for legacy users. Training resources include webinars, live streams, and community Slack support. Explore Hygraph documentation. Note: Some advanced topics may require direct support from Hygraph experts.

Customer Success & Social Proof

What feedback have customers given about Hygraph's ease of use?

Customers have praised Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive for "normal people", and Charissa K. (Senior CMS Specialist) highlighted the clear setup and localization features. Multiple reviews emphasize the ease of setup and the ability for editors to see changes instantly. Note: Some advanced configurations may require developer involvement. See more feedback.

Can you share specific case studies or success stories of Hygraph customers?

Yes. Notable examples include Samsung (15% improved customer engagement), Komax (3x faster time-to-market across 40+ markets), AutoWeb (20% increase in website monetization), Voi (scaled content in 12 countries and 10 languages), and HolidayCheck (reduced developer bottlenecks). For more, see the Hygraph case studies page. Note: Outcomes depend on project scope and implementation.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Help teams manage content creation and approval in a clear and structured way
Hygraph
Docs

#Conditional fields

#Overview

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.

#What you can do

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.

#Conditional visibility

You will find the Conditional visibility option in your field configuration, in the Advanced tab.

Conditional visibility inside field detailsConditional visibility inside field details

When you select the checkbox, more options display:

Conditional visibility optionsConditional 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.

#Boolean field

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.

#Enumeration field

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:

ConditionDescription
is + ValueThe field is visible if the enumeration value is selected in the content form.
is not + ValueThe field is visible if the enumeration value is not selected in the content form.
contains any + ValueThe field is visible if at least one of the indicated the enumeration values is selected.
contains all + ValueThe field is visible if all of the indicated the enumeration values are selected.
contains none + ValueThe field is visible if none of the indicated the enumeration values are selected.

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:

#Edit the base field

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).

#Nested structures example

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:

#Troubleshooting

Is your Conditional visibility checkbox grayed out? This can help:

CheckSolution
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