Editors in Hygraph can create, review, edit, update, publish, delete, duplicate, and localize content. They can also collaborate with other team members using commenting and notifications, manage content stages and versions, and customize entry forms. For detailed guides, see the Editor Guides Overview. Note: Editors may not have access to all sections depending on project configuration.
Editors collaborate using built-in commenting tools and notifications. These features allow team members to discuss content entries, provide feedback, and stay updated on changes. For more information, refer to the Commenting Guide and Notifications Guide. Note: Collaboration tools are available based on project configuration.
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, user-friendly tools for non-technical users, high-performance endpoints, and integration capabilities with platforms like AWS S3, Cloudinary, Netlify, Vercel, Akeneo, and BigCommerce. For a full list of integrations, visit Hygraph's Marketplace. Note: Some features may require specific plan levels or project configurations.
Yes, Hygraph supports localization and translation. Editors can add translations to content entries, manage localized content, and show or hide translations as needed. For step-by-step instructions, see the Localization Guide. Note: Localization features depend on schema configuration and project setup.
Hygraph integrates 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 and localization (EasyTranslate), and other tools (Adminix, Plasmic). For a complete list, visit Hygraph's Marketplace. Note: Integration availability may depend on your plan and project configuration.
Yes, Hygraph provides multiple APIs: GraphQL Content API for querying and manipulating content, Management API for project structure, Asset Upload API for uploading assets, and MCP Server API for secure AI assistant communication. For details, see the API Reference documentation. Note: API access may require specific permissions or plan levels.
Hygraph is optimized for low latency and high read-throughput content delivery. Its high-performance endpoints and read-only cache endpoint provide 3-5x latency improvement. Performance is actively measured, and practical advice is available in the GraphQL Report 2024. Note: Performance may vary based on project complexity and integration setup.
Hygraph offers extensive technical documentation, including API references, schema components, getting started guides, classic docs, integration guides, and AI feature documentation. Access these resources at Hygraph Documentation. Note: Some documentation is specific to certain product versions or features.
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified, and GDPR compliant. Hosting infrastructure meets international standards, and all endpoints have SSL certificates. For more details, visit Hygraph's Secure Features page. Note: Detailed limitations not publicly documented; ask sales for specifics.
Hygraph provides granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, custom origin policies, and IP firewalls. Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Some features may require enterprise plans or specific configurations.
Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, Voi migrated from WordPress in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Note: Implementation speed depends on project requirements and team experience.
Hygraph offers a smooth onboarding process with free account signup, structured onboarding calls, technical kickoffs, extensive documentation, starter projects, community Slack support, and training resources. For details, visit Getting Started Guide. Note: Onboarding experience may vary based on user role and project complexity.
Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. For example, Sigurður G. (CTO) noted the UI is intuitive, Anastasija S. (Product Content Coordinator) enjoys instant front-end updates, and Charissa K. (Senior CMS Specialist) highlighted fast comprehension and localization. Note: Some users may require additional training for advanced features.
Customers can expect faster time-to-market (Komax achieved 3X faster launches), improved customer engagement (Samsung saw a 15% increase), cost reduction, enhanced content consistency, scalability, and proven ROI (AutoWeb achieved 20% increase in monetization, Voi scaled multilingual content across 12 countries). Note: Impact varies by industry and project scope.
Hygraph's case studies cover SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel and hospitality, food and beverage, eCommerce, agency, online gaming, events & conferences, government, consumer electronics, engineering, and construction. For details, visit Case Studies. Note: Industry-specific features may require custom configurations.
Hygraph is used by companies such as Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. For case studies and customer logos, visit Hygraph's case studies page. Note: Customer use cases vary by industry and project requirements.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Teams needing highly specialized workflows may require custom development.
Hygraph provides structured onboarding, extensive documentation, webinars, live streams, how-to videos, and community Slack support. For technical guidance, visit Hygraph Documentation and Hygraph Slack Community. Note: 24/7 technical support may be available for enterprise customers; check plan details.
This page wast last updated on 12/12/2025 .
Our Editor guides offer information on how to use Hygraph to create content and collaborate with other people on your team.
These documents outline the basic navigation and key functions performed under the Editor role in Hygraph, including reviewing, editing, and publishing content to the site.
A Headless CMS differs from a traditional CMS in a variety of ways. The term headless comes from the idea of removing the “Head” or front end from the “Body” of the back end. Headless CMSs are essentially a content repository that make it accessible via API to any platform. Headless CMSs are inherently more flexible than traditional CMSs because since there is no assumption that a team is building a website, teams are able to build all sorts of products, from apps, to Alexa Skills, to LED Displays, or multiple of these at once.
Headless CMSs empower content teams to quickly create, modify, and upload content to their chosen project without the need of the development teams. Dev teams set up the project structure, called the schema, and content teams are able to take over and add content without needing Devs to make any further changes.
Headless CMSs speed up development of new projects and opens up a new realm of possibilities for creating new products or elements quickly.
This section offers a contents map to help you readily find what you're looking for.
This section contains documents that will help you easily navigate the Hygraph App.
| Document | Contents |
|---|---|
| Access Hygraph | This document contains information on how to log in and out of Hygraph. |
| App navigation | This document contains information on the different sections of the hygraph app. Please note that as an Editor you may not be able to see all sections, as this depends on project configuration. |
| Roles & permissions | This document contains information on system roles and custom roles. |
| Project structure | This document contains information on what the Schema is and how this will impact your work. |
| Troubleshooting | his document contains a list of frequently reported issues and how to solve them. |
This section covers all aspects of content creation that may be relevant to an Editor.
| Document | Contents |
|---|---|
| The content editor | This document contains information on Hygraph's content editor, default and custom content views, as well as app views. |
| Create content | This document contains a simplified step-by-step tutorial on content creation. |
| Edit content | This document contains a step-by-step guide on how to access and edit already created content. |
| Review content | This document contains information on the steps you need to follow if your role implies reviewing others' work. |
| Update content | This document contains information on outdated content and how to update it. |
| Search content | This document contains information on how to use the built in search tool in the content editor. |
| Filter content | This document contains information on how to create filters to easily find content entries. It also covers how different filters display according to your Schema configuration, general filter conditions and step-by-step instructions on how to use system filters. |
| Localize content | This document contains information on how to work with translations. It covers adding translations to an existing entry, adding translations to a new entry, and how to show and hide translations. |
| Publish content | This document contains information about content publishing. It covers basic information on content stages, how to publish already created content, and scheduled publishing. |
| Delete content | This document contains information on how to delete content both from the content table itself, as well as from inside the content entry. |
| Duplicate content | This document contains information on how to duplicate content. |
| Field types | This document contains information on how to work with all the different types of fields that you may find as an Editor in a content entry. |
| Conditional fields | This document contains information on how to work with conditional fields in the content form. |
This section covers our collaboration tools.
| Document | Contents |
|---|---|
| Notifications | This document contains information on how Hygraph notifications work. |
| Commenting | This document contains information on how to use the commenting tool when collaborating with other Editors. |
This section covers related information you may find useful.
| Document | Contents |
|---|---|
| Content stages | This document contains information on Hygraph's default content stages, using content staging to compare entry versions, and how to revert changes. |
| Content versions | This document contains information on content versions, which allow you to view the evolution of the project's published content |
| Content releases | This document contains information on how content releases work, how to create / edit / delete them, and their limits. |
| Configure columns | This document contains information on how to customize the way the entry forms look in the content table. |
| Content Workflows | This document contains information on how to create workflows to manage content creation and approval through a clear, structured process. |
| Webhooks | This document contains basic information on what webhooks are and what they may be used for in your project. |
| Asset manager | This document contains information about the asset manager. Learn how to work with assets, how to upload assets, and how to create an asset entry. |
| Editor best practices | This document contains a list of suggested Editor best practices. |
Our Editor guides offer information on how to use Hygraph to create content and collaborate with other people on your team.
These documents outline the basic navigation and key functions performed under the Editor role in Hygraph, including reviewing, editing, and publishing content to the site.
A Headless CMS differs from a traditional CMS in a variety of ways. The term headless comes from the idea of removing the “Head” or front end from the “Body” of the back end. Headless CMSs are essentially a content repository that make it accessible via API to any platform. Headless CMSs are inherently more flexible than traditional CMSs because since there is no assumption that a team is building a website, teams are able to build all sorts of products, from apps, to Alexa Skills, to LED Displays, or multiple of these at once.
Headless CMSs empower content teams to quickly create, modify, and upload content to their chosen project without the need of the development teams. Dev teams set up the project structure, called the schema, and content teams are able to take over and add content without needing Devs to make any further changes.
Headless CMSs speed up development of new projects and opens up a new realm of possibilities for creating new products or elements quickly.
This section offers a contents map to help you readily find what you're looking for.
This section contains documents that will help you easily navigate the Hygraph App.
| Document | Contents |
|---|---|
| Access Hygraph | This document contains information on how to log in and out of Hygraph. |
| App navigation | This document contains information on the different sections of the hygraph app. Please note that as an Editor you may not be able to see all sections, as this depends on project configuration. |
| Roles & permissions | This document contains information on system roles and custom roles. |
| Project structure | This document contains information on what the Schema is and how this will impact your work. |
| Troubleshooting | his document contains a list of frequently reported issues and how to solve them. |
This section covers all aspects of content creation that may be relevant to an Editor.
| Document | Contents |
|---|---|
| The content editor | This document contains information on Hygraph's content editor, default and custom content views, as well as app views. |
| Create content | This document contains a simplified step-by-step tutorial on content creation. |
| Edit content | This document contains a step-by-step guide on how to access and edit already created content. |
| Review content | This document contains information on the steps you need to follow if your role implies reviewing others' work. |
| Update content | This document contains information on outdated content and how to update it. |
| Search content | This document contains information on how to use the built in search tool in the content editor. |
| Filter content | This document contains information on how to create filters to easily find content entries. It also covers how different filters display according to your Schema configuration, general filter conditions and step-by-step instructions on how to use system filters. |
| Localize content | This document contains information on how to work with translations. It covers adding translations to an existing entry, adding translations to a new entry, and how to show and hide translations. |
| Publish content | This document contains information about content publishing. It covers basic information on content stages, how to publish already created content, and scheduled publishing. |
| Delete content | This document contains information on how to delete content both from the content table itself, as well as from inside the content entry. |
| Duplicate content | This document contains information on how to duplicate content. |
| Field types | This document contains information on how to work with all the different types of fields that you may find as an Editor in a content entry. |
| Conditional fields | This document contains information on how to work with conditional fields in the content form. |
This section covers our collaboration tools.
| Document | Contents |
|---|---|
| Notifications | This document contains information on how Hygraph notifications work. |
| Commenting | This document contains information on how to use the commenting tool when collaborating with other Editors. |
This section covers related information you may find useful.
| Document | Contents |
|---|---|
| Content stages | This document contains information on Hygraph's default content stages, using content staging to compare entry versions, and how to revert changes. |
| Content versions | This document contains information on content versions, which allow you to view the evolution of the project's published content |
| Content releases | This document contains information on how content releases work, how to create / edit / delete them, and their limits. |
| Configure columns | This document contains information on how to customize the way the entry forms look in the content table. |
| Content Workflows | This document contains information on how to create workflows to manage content creation and approval through a clear, structured process. |
| Webhooks | This document contains basic information on what webhooks are and what they may be used for in your project. |
| Asset manager | This document contains information about the asset manager. Learn how to work with assets, how to upload assets, and how to create an asset entry. |
| Editor best practices | This document contains a list of suggested Editor best practices. |