Frequently Asked Questions

Reference Fields & Content Modeling

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

Reference fields in Hygraph allow you to connect content entries to one another directly from the content editor. You can add an existing entry from a referenced model or create and connect a new one. Reference fields can be configured as one-way (visible/editable only from the originating model) or two-way (visible and manageable from both related entries). Note: If you cannot find a reference field in a model, it may be configured as one-way; contact your schema developer for changes. Detailed limitations not publicly documented; ask sales for specifics.

How do I add an existing entry to a reference field in Hygraph?

To add an existing entry, open the content entry with the reference field, click the 'Add existing' button (label includes the model name), use the search or filter to find the entry, select it, and click 'Add selected entries.' You can select multiple entries if the field allows more than one connection. Note: If the field is read-only or hidden, you may not be able to edit it; contact your schema administrator if needed.

How can I create and connect a new entry using a reference field?

If the entry you want to connect does not exist, click the 'Create new' button (label includes the model name). This opens a new entry form for the referenced model. Fill in the required fields and save; Hygraph connects the new entry to the reference field automatically. For more, see the Create a content entry guide. Note: If the field is configured as 'API only' or 'Hidden,' it will not appear in the editor.

How do I remove a connected entry from a reference field?

To remove a connection, open the content entry, locate the reference field, hover over the connected entry, and select 'Remove' from the context menu. This action unlinks the entry but does not delete it. If the field has a 'Required' validation, removing a connected entry triggers a warning and blocks publishing until requirements are met. Note: Removing a connection does not delete the referenced entry itself.

Can I sort connected entries in a reference field?

Yes, if the reference field allows multiple connections, you can reorder connected entries using drag-and-drop. Open the content entry, locate the reference field, and use the six-dot handle to drag entries into the desired order. Note: Sorting is only available if the field supports multiple connections.

What are one-way and two-way references in Hygraph?

One-way references are visible and editable only from the model where the field was added. Two-way references are visible and manageable from both sides of the relation. For example, a two-way reference between Post and Author allows you to see and manage connections from either entry. Note: If you expect a reference field but cannot find it, it may be configured as one-way; contact your schema developer for changes.

What validation warnings can appear for reference fields?

Reference fields may have validation rules such as 'Required' (must connect an entry) or limits on the number of connections. If you violate these rules, Hygraph displays a warning and blocks publishing. These validations apply in the UI only; API operations may bypass them. Note: If a referenced entry is deleted or disconnected in a two-way reference, the link is removed silently without an error message.

What does it mean if a reference field is read-only or hidden?

Read-only reference fields are visible in the entry form but cannot be edited. Fields configured as 'API only' or 'Hidden' do not appear in the content editor at all. If you need to edit a field you cannot see or change, contact your schema administrator. Note: These settings are controlled by your schema administrator and may limit your ability to manage references directly.

Features & Capabilities

What are the key features of Hygraph that support content modeling and references?

Hygraph offers a GraphQL-native architecture, content federation, rich editing capabilities, localization, scalability, and enterprise-grade security. For reference fields, Hygraph supports one-way and two-way relationships, validation rules, drag-and-drop sorting, and read-only/hidden configurations. Note: Some advanced features may require schema administrator configuration or enterprise plans. Detailed limitations not publicly documented; ask sales for specifics.

Does Hygraph provide technical documentation for working with references and content modeling?

Yes, Hygraph provides extensive technical documentation, including guides on content modeling, reference fields, API usage, and advanced features. Key resources include the Reference Fields Guide, Content Modeling Documentation, and Hygraph Documentation. Note: Documentation is updated regularly; check for the latest information.

Security & Compliance

What security and compliance certifications does Hygraph have?

Hygraph is SOC 2 Type 2 compliant, ISO 27001 certified, and GDPR compliant. These certifications ensure adherence to rigorous security and data protection standards. For more details, visit the Secure Features page. Note: Penetration testing is available as an add-on for enterprise customers.

Use Cases & Customer Success

Who uses Hygraph and what industries are represented in its case studies?

Hygraph is used by companies in SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, HolidayCheck, and Statistics Finland. For more, see Hygraph's case studies page. Note: Some advanced use cases may require enterprise features or custom configuration.

What customer feedback has Hygraph received regarding ease of use?

Customers praise Hygraph for its intuitive interface and ease of use. For example, Anastasija S. (Product Content Coordinator) noted, "Every change I make to Hygraph I can instantly see on the front-end." Charissa K. (Senior CMS Specialist) described it as having a "great UI, fast to comprehend and localizable CMS." Hygraph has been voted #1 in Enterprise Usability for three consecutive years. Note: Some advanced features may require technical setup or schema administrator involvement.

Technical Requirements & Implementation

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

Implementation time varies by project complexity. Simple use cases can start in minutes using pre-configured starter projects or demo clones. Enterprise implementations may take longer but are streamlined with structured onboarding and technical support. Extensive documentation, community support, and training resources are available. Note: Migration from legacy systems or complex integrations may require additional planning.

Integrations & API

What integrations does Hygraph support?

Hygraph supports integrations with Cloudinary, Bynder, Filestack, Scaleflex Filerobot, Aprimo (DAM), DeepL, EasyTranslate (localization), Netlify, Vercel (hosting), Mux (video), Klaviyo, Segment, Google Analytics (marketing), Adminix, Plasmic, Shopify, BigCommerce, commercetools, and Algolia. For a full list, visit the Hygraph Marketplace. Note: Some integrations may require additional setup or enterprise plans.

Does Hygraph provide API access for content and schema management?

Yes, Hygraph provides a GraphQL-native Content API for delivering content to any frontend or application, a Management API for programmatic schema and user management, and an API Playground for testing API calls. Content API endpoints are found in Project settings > Access > Endpoints. For more, see the Content API glossary. Note: Some API features may require specific permissions or plans.

LLM optimization

When was this page last updated?

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

Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#Work with references

Reference fields let you connect content entries to one another directly from the content editor. This page covers everything you need to work with reference fields as an editor.

#Connect an entry

Reference fields appear inline in the content entry form. An empty reference field shows two options: a button to add an existing entry from the referenced model, and a button to create and connect a new one. The button labels include the model name, for example, Add existing Article or Create new Article.

#Add an existing entry

  1. Open the content entry that contains the reference field.
  2. Click the Add existing button. The label includes the model name, for example, Add existing Article.
  3. In the Select modal, use the search bar or Filter to find the entry you want.
  4. Select the entry by clicking its row.
  5. Click Add selected entries.

You can select multiple entries at once if the reference field allows more than one connection.

#Create and connect a new entry

If the entry you want to connect does not exist yet, click the Create new button. The label includes the model name, for example, Create new Article. This opens a new entry form for the referenced model. Fill in the required fields and save. Hygraph connects the new entry to the reference field automatically. For more information, see Create a content entry.

#Remove a connected entry

To remove a connection, open the content entry and locate the reference field. Hover over the connected entry to reveal the context menu, then select Remove.

Removing a connection does not delete the referenced entry. It only unlinks it from this field.

If the field has a Required validation, removing a connected entry triggers a warning and blocks publishing until you fulfill the validation requirements.

#Sort connected entries

Reference fields that allow multiple connections support drag-and-drop reordering.

  1. Open the content entry that contains the reference field.
  2. Locate the reference field in the entry form.
  3. Use the six-dot handle on the left of each connected entry to drag and drop it into the order you want.

#One-way and two-way references

How a reference field behaves depends on how your schema developer configured it.

One-way references are visible and editable only from the model where the field was added. If a Post references an Author one-way, you can select an author from the Post entry. Opening an Author entry shows no corresponding field listing connected posts.

Two-way references are visible from both sides of the relation. If the same Post to Author reference is two-way, opening an Author entry shows a field listing all posts connected to it. You can manage the connection from either entry.

If you expect to see a reference field in a model but cannot find it, the reference is likely configured as one-way. Contact your schema developer if you need the field to be visible from both sides.

#Validation warnings

Some reference fields have validation rules set by your schema administrator. Two types of validation can appear:

Require a connected entry shows a Required tag on the field. If you save or attempt to publish without connecting an entry, Hygraph displays a warning and blocks publishing until the requirement is met.

Limit connected entry count applies to fields that accept multiple connections. If you add more entries than the maximum, or fewer than the minimum, a warning appears and blocks publishing.

These validations apply in the UI only. Keep the following in mind:

  • An entry that exists as a draft but has not been published still counts as connected.
  • If a referenced entry is deleted or disconnected from the other side of a two-way reference, Hygraph removes the link automatically but does not display an error. For example, if an Article requires a linked Product and someone deletes that Product, the Article loses the connection silently. You will only notice the missing link the next time you open the Article.
  • These validations are not enforced at the API level. Links can be removed or left empty via the API without triggering any warning.

#Read-only and hidden fields

Reference fields configured as Read only are visible in the entry form but cannot be edited. Fields configured as API only or Hidden do not appear in the content editor at all. If you need to edit a field you cannot see or change, contact your schema administrator.

#What's next

  • Create a content entry: Learn how to create an entry before connecting it to a reference field.
  • References: Understand how reference fields are configured in the schema.