Content filtering in Hygraph allows users to restrict the entries displayed in a content table using specific parameters. This helps create curated overviews, locate specific types of content, and find entries that match multiple criteria, making content management more efficient and focused. Learn more.
Quick Filters in Hygraph provide predefined filters that can be instantly applied to content or asset views, reducing the time and effort needed to find relevant entries. You can add multiple Quick Filters from the filter menu, and each selected filter appears in the filter bar, updating the content table accordingly. See details.
Yes, Quick Filters can be applied to both regular content views and asset views, allowing for flexible and efficient filtering across different types of entries. Read more.
Column filters allow you to filter content by system and custom fields, such as stage, ID, or other schema-defined fields. While Quick Filters are predefined and instantly applied, column filters require configuration and can be tailored to specific field conditions. Both types function similarly but offer different levels of customization. Learn more.
To adjust filters manually, use the Filters menu at the top of any content view. You can select Quick or Column filters, configure conditions, and enter comparison values. Filters can be removed by clicking the 'X' next to them. For more details, see the manual adjustment guide.
Hygraph provides system filters such as Stage, ID, Created at, Updated at, Created by, Updated by, and Published by. These filters allow you to sort and find content based on system-level metadata and user relations. See system filters.
To filter by stage, select 'Stage' from the column filters and choose a condition and stage value. For ID, use the ID filter with conditions like 'is', 'starts with', or 'ends with'. For date fields (Created at, Updated at), select the field and use conditions such as 'less than' or 'greater than' with a calendar input. Stage, ID, Date.
Hygraph supports various filter conditions based on field types:
Currently, filters cannot be used for components, union type references, or Rich Text fields within the content editor. For advanced filtering on these fields, use the API Playground with GraphQL queries. Learn more.
Hygraph's editor UI is frequently praised for its intuitive and clear design, making it easy for both technical and non-technical users to navigate and manage content. Customers have noted that even those without technical expertise can start using Hygraph right away. Hygraph was recognized for "Best Usability" in Summer 2023. See user feedback.
Hygraph provides extensive documentation for content editors, including guides on project structure, editing content, field types, and more. Access the documentation at Editor Guides.
The Field Outline visually displays the structure of a content entry, allowing editors to navigate intuitively and make changes faster. This enhances usability and speeds up the editing process. Learn more.
Click to Edit lets editors click on elements in a Hygraph-powered preview and jump directly to the corresponding field in Studio, focusing the form on that field and keeping the preview open side-by-side. It ships with two powerful modes: Field Update (live visual feedback) and Field Focus (reverse lookup), enabling real-time preview and easier field identification. Read more.
Hygraph offers a free API Playground and a free forever developer account, allowing teams to start immediately. The structured onboarding process includes introduction calls, account provisioning, business and technical kickoffs, and content schema setup. Training resources and extensive documentation are available for step-by-step guidance. See onboarding details.
Implementation time varies by project scope. For example, Top Villas launched a new project within 2 months from initial contact, and Si Vale met aggressive deadlines during their initial implementation. The onboarding process is designed for efficiency and speed. See case study.
Hygraph provides 24/7 support via chat, email, and phone, real-time troubleshooting through Intercom chat, a community Slack channel, webinars, live streams, how-to videos, and extensive documentation. Enterprise customers receive a dedicated Customer Success Manager for personalized guidance. Explore resources.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified for hosting infrastructure, and GDPR compliant. These certifications ensure robust security and adherence to international standards. See security features.
Hygraph offers granular permissions, SSO integrations, audit logs, encryption at rest and in transit, regular backups, and a transparent process for reporting security issues. Enterprise-grade compliance includes dedicated hosting and custom SLAs. Learn more.
Hygraph features Smart Edge Cache for enhanced performance and faster content delivery, high-performance endpoints for reliability and speed, and practical advice for optimizing GraphQL API usage. These improvements are detailed in the performance blog.
Hygraph is ideal for developers, product managers, and marketing teams in industries such as ecommerce, automotive, technology, food and beverage, and manufacturing. It suits organizations modernizing legacy tech stacks, global enterprises needing localization, and those seeking scalable, future-proof content management. See more.
Hygraph addresses operational inefficiencies (reducing developer dependency, modernizing legacy stacks), financial challenges (lowering costs, accelerating speed-to-market), and technical issues (simplifying schema evolution, improving integration, optimizing performance, and enhancing localization and asset management). See KPIs.
Komax achieved a 3X faster time-to-market, Autoweb saw a 20% increase in website monetization, Samsung improved customer engagement by 15%, and Stobag increased online revenue share from 15% to 70%. More stories are available at customer stories.
Hygraph is cloud-based, so all deployment, updates, security, and infrastructure maintenance are managed by Hygraph. Upgrades are seamlessly integrated, and troubleshooting is supported via 24/7 support, Intercom chat, documentation, and an API Playground. Enterprise customers receive a dedicated Customer Success Manager. See support options.
Filtering allows you to use specific parameters to restrict the entries that display in a content table. This is helpful when trying to create a more curated overview of content.
These filters can be useful when building content views, looking for a specific type of content, or finding content that matches several parameters.
Filters
Our Quick Filters feature reduces the time and effort required to create a filter. You can now find the content you need, faster.
Quick Filters
It offers several predefined filters that apply instantly when selected, allowing you to focus on you work without unnecessary distractions.
You can apply Quick Filters to both regular content views and asset views.
To add Quick Filters, simply use the Filter menu to display the available options and select one.
Add a Quick Filter
Once you select a Quick Filter, the regular filter appears in the filter bar and the content table shows the sorted content.
You can apply more than one Quick Filter. To do this, simply use the filter menu again and select another one.
For instance, the following image shows a content table where two Quick Filters have been applied, Created by me & Only published entries:
Quick Filter applied
The Filters menu also contains column filters.
Column filters
Column filters allow you to filter content by some system and custom fields, stage and ID.
Quick and column filters function in the same way. The following document section explains how to use them.
You can find the filters on any content view, at the top of the content table. Clicking on the Filters menu displays your options for quick and column filters:
Filters menu
You can use the Search at the top of the filters menu to quickly find a filter.
To filter content, select one of the fields listed for filtering. It can be a quick or column filter:
At the moment, you can't use these filters for components, union type references, or Rich Text.
To remove a filter, simply click the X button next to it.
Filter content by stage
Filter to open the filter menu.Stage from the column filters list.Stage to pick a condition.For example, if you select is on the first dropdown, and then PUBLISHED on the second, the filter will show you all the content entries that are currently on the PUBLISHED stage.
It is not necessary to type in a keyword in the search field for this filter to work, so you can use the filter on its own to return search results on all the content in that model, or you can use it to narrow down a search that uses keywords.
An ID is a unique identifier of your content entry that the system assigns to it when you first save it. You can see it on the sidebar in the edit view, under Entry information.
Content entry ID
If you know the ID of a content entry you are looking for - totally or partially - you can use that to quickly find it using the ID filter.
Filter content by ID
Filter to open the filter menu.ID from the column filters list.ID to pick a condition.Some examples
Imagine we are looking for a content entry with the ID clgm2kql0bspm0burfoqjqhdl:
is clgm2kql0bspm0burfoqjqhdl as a filter. This would return only one result, the exact content entry you're looking for.clgm, you could use starts with cglm as a filter. This would return all content entries that have IDs that start with cglm.qhdl, you could use ends with qhdl as a filter. This would return all content entries that have IDs that end with qhdl.The Created at and Updated at filter look at DateTime fields in the content entry. This can be the date of creation/update, as well as any DateTime field in the schema configuration for the model.
Filter content by Created at
The DateTime field contains date/time information at UTC, which would look something like this 2007-12-03T10:15:30Z. Since this information is extremely exact, it is best to use the Created at filter with the less than or greater than conditions.
Filter to open the filter menu.Created at, or Updated at from the column filters list.These filters take a list of project users, and compare a value you provide to relational fields in the project, so - in a way - this would be filtering by relations.
Filter content by Created by
This filter functions like so:
Filter to open the filter menu.Created by, Updated by, or Published by from the column filters list.While all projects have the default system filters, different filters may display depending on your project schema configuration.
Let's go over this with an example. Look at the following project schema for a Product model:
Filters example: The Schema
It has fields for product name, slug, image, sections, description, price, a condition, an enumeration for product size, and a taxonomy for product category.
When you go to the Content editor section of the app, select the Product view, and click on the Filter menu, you will see most of the fields you saw in the schema as filters under "Column Filters", in addition to the system filters that are always there.
Filters example: The Content Editor
Some fields, such as rich text, can't be filtered in the content editor and require a different approach through the API Playground which, in turn, requires familiarity with GraphQL, and is not usually Editor work.
In general, a filter will provide different conditions depending on the type of field configured in the schema. You will find string, boolean, enums, taxonomy, reference, and DateTime.
Each type offers different conditions to filter by:
Strings are sequences of characters, so they are often used for text fields such as titles or descriptions. They offer the following conditions for filtering:
is: This condition filters for content that matches the text you enter.is not: This condition filters for content that doesn't match the text you enter.contains: This condition filters for content that contains the text you enter.doesn't contain: This condition filters for content that doesn't contain the text you enter.starts with: This condition filters for content that starts with the text you enter.doesn't start with: This condition filters for content that doesn't start with the text you enter.ends with: This condition filters for content that ends with the text you enter.doesn't end with: This condition filters for content that doesn't end with the text you enter.An good example of this type of filter that you can find in all projects is the ID filter.
Boolean fields can take two values: true and false. In all cases, booleans provide a condition dropdown, and then a second dropdown containing the true / false values.
The conditions dropdown menu for booleans contains the following options:
is: This condition filters for content that matches the value you select from the dropdown.is not: This condition filters for content that doesn't match the value you select from the dropdown.is null: This condition filters for content where no value has been assigned to the field. You do not need to select any value for this filter.is not null: This condition filters for content where a value has been assigned to the field. You do not need to select any value for this filter.For example, imagine you have a boolean for reviewed. Like all booleans, it can only take two values: true & false. So, if you set the filter to reviewed is true, the filter will return all entries where the reviewed boolean field has been set to true.
Enums are lists of items. Your project has them as system fields, like in the case of content stage, and may also have them as custom dropdown fields in the schema.
In all cases, enums provide a condition dropdown, and then a second dropdown containing the values configured on the list for that enum. Like this:
Taxonomy - example
The above example shows a filter where the enum is a list for product sizes. This particular field allows multiple values, so you have checkboxes next to every option in case you need to select more than one.
The conditions dropdown menu for enums contains the following options:
is: This condition displays content that is an exact match for the value you select from the dropdown.is not: This condition displays content that is not an exact match for the value you select from the dropdown.is null: This condition displays content where no value has been assigned to the field. You do not need to select any value for this filter.is not null: This condition displays content where a value has been assigned to the field. You do not need to select any value for this filter.includes all: This condition displays content that matches all the values you select from the dropdown.includes none: This condition displays content that matches none of the values you select from the dropdown.includes some: This condition displays content that matches some of the values you select from the dropdown.Please note that not all enums will display all the options above, some may display them partially. An example of this is the Stage filter.
A taxonomy is a group of terms arranged in a hierarchical structure. Your project has them as system fields and may also have them as custom dropdown fields in the schema.
In all cases, taxonomies provide a condition dropdown, and then a second dropdown containing the values configured for that taxonomy. Like this:
Taxonomy - example
The above example shows a filter where the taxonomy is a category for product types.
The conditions dropdown menu for taxonomies contains the following options:
is: This condition displays content that is an exact match for the taxonomy node you select from the dropdown.is not: This condition displays content that is not an exact match for the taxonomy node you select from the dropdown.is in: This condition displays all content that matches the multiple taxonomy nodes you select from the dropdown.is not in: This condition displays all content that does not match the multiple taxonomy nodes you select from the dropdown.descendants of: This condition displays content that matches the selected taxonomy node and all nodes below it.
Filtering by relations
Filtering by reference is basically filtering by relation. This filter is dynamic, in the sense that it changes depending on the relational field you select, but in general terms its usage follows three steps:
Updated At and Created At require that you select a date from a calendar and type in a time. Is null and Is not null do not require any additional input.It is not possible to filter by union-type reference fields - those that allow you to reference more than one model in a field.
The references you can select for your filter depend on project configuration. All projects have the default reference filters - we'll look into them in a moment - but they can also have a number of custom ones.
The default reference filters that all projects have are Created by, Updated by, and Published by. They are related to project users and provide the following relational fields that you can select from the dropdown:
IsActive: IsActive checks if the user is active or not. This is a boolean field and, as such, it offers all conditions a boolean field does, and you will be able to select true or false from the values menu.Kind: Kind is an enum field that checks if the creator of a piece of content is a user or a token. As most enum fields, it offers all conditions an enum field does, and you will be able to select one of the following values from the values menu:
MEMBER: The content was created / updated by a user.PAT: The content was created / updated by a token.PUBLIC: The content was created / updated by the public API.WEBHOOK: The content was created / updated by a webhook.APP_TOKEN: The content was created / updated by an app.Picture: This checks for pictures of the related users. This is a string field and, as such, it offers all conditions a string field does, and allows you to enter text to apply that condition to.Name: This checks for names of the related users. This is a string field and, as such, it offers all conditions a string field does, and allows you to enter text to apply that condition to.Updated At: This checks for date and time of update of a content entry. This is a DateTime field and, as such, it offers all conditions a DateTime field does, and allows you to select a date and time from a calendar picker.Created At: This checks for date and time of creation of a content entry. This is a DateTime field and, as such, it offers all conditions a DateTime field does, and allows you to select a date and time from a calendar picker.ID: This checks user IDs. This is a string field and, as such, it offers all conditions a string field does, and allows you to enter text to apply that condition to.The DateTime field contains date/time information at UTC, which would look something like this 2007-12-03T10:15:30Z.
This field type offers the following conditions:
is: This condition returns exact matches to the date and time selected, including milliseconds. Considering this filter won't provide results unless the information provided is exact, it is recommended to stick to less than and greater than conditions for date & time.is null: If your project has custom fields for date & time, and these fields are not required, then they may not always have a value assigned to them. If this is the case, using the is null filter returns all content entries where that custom date & time field does not have a value.is not null: This condition returns all content entries that have a value assigned to a date and time field.is not: This condition returns all entries where the date & time is not the one you provide.less than: This condition returns all entries where the date & time is earlier than the one you provide.less than or equal to: This condition returns all entries where the date & time is earlier than or equal to the one you provide.greater than: This condition returns all entries where the date & time is later than the one you provide.greater than or equal to: This condition returns all entries where the date & time is later than or equal to the one you provide.An example of this that you can find in every project are the Created at and Updated at filters.