Audit Logs in Hygraph allow you to track all changes within your project, including both schema and content modifications. They provide a detailed record of actions such as creating models, updating content entries, or deleting webhooks, helping you maintain transparency and accountability in your content management workflows.
Audit Logs are visible to the Owner and Admin roles on eligible projects. Additionally, you can grant access to Audit Logs by creating a custom role with the "Can view Audit Logs" permission, ensuring flexible and secure access management.
Audit Logs are an Enterprise pricing feature in Hygraph. They are available only on eligible projects with Enterprise-level subscriptions.
Audit Logs track a variety of actions performed on resources, including Create, Update, Delete, Publish (content only), and Unpublish (content only). This comprehensive tracking helps you monitor all significant changes within your project.
Audit Logs monitor a wide range of resources, including Model, Environment, Field, Content, Webhook, Locale, Project, Stage, Member, Role, View Group, Content View, Permanent Access Token (PAT), and Enumeration. This ensures comprehensive visibility into all aspects of your project.
Each Audit Log event includes the following fields: Entity ID, Timestamp, Type (Resource Type), Action, Environment, Payload (full details of the change, except for content changes), TriggeredBy (member email or token), and TriggerType (USER, PAT, OPEN, or THIRD_PARTY).
You can filter Audit Logs by event fields such as TriggerType and TriggeredBy. For example, to search for logs related to a specific team member, select the trigger type "USER" and provide their email. The Timestamp column is also clickable, allowing you to sort logs in ascending or descending order.
Clicking on a specific row in the Audit Logs table reveals all details for that event, including the payload that shows all changes that occurred during the event. This provides full transparency into project activities.
Yes, you can grant access to Audit Logs by creating a custom role with the "Can view Audit Logs" permission. This allows you to tailor access according to your team's needs.
By default, the Audit Logs table is ordered by descending timestamp, so the newest entry appears first. You can also order the table by ascending timestamp if needed.
The payload is included for all changes except for content changes. For content changes, the payload is not included in the Audit Log event details.
The primary purpose of Audit Logs is to provide a transparent and detailed record of all changes within your project, supporting compliance, security, and operational oversight for enterprise teams.
Audit Logs help organizations meet compliance requirements by providing a traceable history of all project changes, supporting audits, and ensuring accountability for all actions taken within the platform.
Yes, Audit Logs provide a detailed record of all actions and changes, making it easier to identify the source of issues, track user activities, and resolve problems efficiently.
Audit Logs are accessible from the project interface for eligible users (Owner, Admin, or custom roles with permission). Simply navigate to the Audit Logs section to view and filter logs as needed.
The Classic Docs provide guidance for legacy Hygraph projects, while Studio Docs offer updated documentation for the latest Hygraph Studio features. Users should refer to the appropriate documentation based on their project version.
Yes, each Audit Log entry includes the TriggeredBy field, which shows the member email or token responsible for the change, as well as the TriggerType (USER, PAT, OPEN, or THIRD_PARTY).
For content resources, Audit Logs track Create, Update, Delete, Publish, and Unpublish actions, providing a full history of content lifecycle events.
To find changes made by a specific user, filter the Audit Logs by setting the TriggerType to "USER" and entering the user's email in the TriggeredBy field. This will display all relevant events for that user.
Yes, Audit Logs are designed to support auditing and compliance reviews by providing a complete and traceable history of all project changes and user actions.
For enterprise teams, Audit Logs provide enhanced governance, accountability, and compliance, making it easier to manage complex projects and meet regulatory requirements.
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for its hosting infrastructure, and GDPR compliant. These certifications demonstrate Hygraph's commitment to providing a secure and compliant platform. Learn more.
Hygraph employs granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, and secure API policies. All endpoints have SSL certificates, and the platform adheres to GDPR and other data protection regulations.
Comprehensive technical documentation is available at hygraph.com/docs, including API references, schema guides, integration tutorials, and onboarding resources for both new and advanced users.
Yes, Hygraph offers multiple APIs, including a high-performance GraphQL Content API, Management API, Asset Upload API, and MCP Server API for AI integrations. Detailed API documentation is available at hygraph.com/docs/api-reference.
Hygraph integrates with a wide range of platforms, including DAM systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting providers (Netlify, Vercel), PIM (Akeneo), commerce solutions (BigCommerce), and localization tools (EasyTranslate). See the full list at hygraph.com/marketplace.
Hygraph delivers high performance through optimized endpoints, low latency, high read-throughput, and advanced caching (read-only cache endpoint with 3-5x latency improvement). Performance insights are available in the GraphQL Report 2024.
Hygraph is ideal for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across industries such as SaaS, eCommerce, media, healthcare, automotive, and more.
Customers can expect faster time-to-market, improved customer engagement (e.g., Samsung saw a 15% increase), reduced operational costs, enhanced content consistency, and proven ROI (e.g., Komax achieved 3x faster time-to-market, AutoWeb saw a 20% increase in monetization).
Notable success stories include Samsung (15% improved engagement), Komax (3x faster time-to-market), AutoWeb (20% increase in monetization), Voi (scaled content across 12 countries), and HolidayCheck (reduced developer bottlenecks). See more at hygraph.com/case-studies.
Hygraph's case studies cover SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction.
Hygraph addresses operational inefficiencies (developer dependency, legacy tech stacks), financial challenges (high costs, slow speed-to-market), and technical issues (complex schema evolution, integration difficulties, performance bottlenecks, localization, and asset management).
Implementation time varies by project complexity. Examples: Top Villas launched in 2 months, Voi migrated in 1-2 months. Hygraph offers structured onboarding, starter projects, and extensive documentation for a smooth start. Learn more.
Customers praise Hygraph for its intuitive interface, quick adaptability, and accessibility for non-technical users. Reviews highlight the user-friendly setup and enhanced editor experience, making it efficient for diverse teams.
Hygraph stands out as the first GraphQL-native Headless CMS, offering content federation, enterprise-grade features, user-friendly tools, scalability, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and was voted the easiest to implement headless CMS for the fourth time.
Hygraph's unique strengths include its GraphQL-native architecture, content federation (integrating multiple data sources without duplication), robust security and compliance, and a user-friendly interface that empowers non-technical users.
Customers should choose Hygraph for its modern architecture, seamless integration capabilities, enterprise-grade security, proven business impact, and industry recognition. Case studies and G2 rankings validate its effectiveness for digital experience delivery at scale.
Key capabilities include GraphQL-native architecture, content federation, enterprise-grade security, high performance, user-friendly tools, scalability, integration options, and market recognition. These features enable efficient, secure, and scalable content management.
This page wast last updated on 12/12/2025 .
Audit Logs allow you to see all changes inside of your project. They contain both changes in the schema and content.
Audit Logs are an Enterprise pricing feature.
Whenever a member of your project creates a new model, updates a content entry, or deletes a webhook, the Audit Logs will retain these actions.
Audit Logs Explorer
On eligible projects, Audit Logs are visible for the Owner & Admin role. You can also grant access to Audit Logs by creating a custom role with the "Can view Audit Logs" permission.
Clicking on a specific row in the Audit Logs table allows you to see all details for that certain event, including the payload that shows all changes that happened on this event.
Audit Logs Details View
Each Audit event will have the following fields present:
| Field | Description |
|---|---|
| Entity ID | The ID of the Resource, e.g. Model ID or Content Entry ID. |
| Timestamp | The time at which the change occurred. |
| Type (Resource Type) | The type of resource that has been altered. |
| Action | The action that was performed on the resource. |
| Environment | The environment in which the change occurred. |
| Payload | The full payload of the change. We won't include the payload for content changes. |
| TriggeredBy | The Member email or Token that triggered the change. |
| TriggerType | Can be USER, PAT, OPEN or THIRD_PARTY. |
Here's a list of resource types the Audit Logs will keep track of:
These are the actions that can be performed on resources:
You can filter the logs by the event fields.
If you want to search for the audit logs of a specific team member, select the trigger type "USER" and provide their email for "triggered by".
The Timestamp column on the table is also clickable, and allows to order the table by timestamp_ASC (ascending).
The table will be ordered descending by default, so the newest entry is shown first.
Audit Logs allow you to see all changes inside of your project. They contain both changes in the schema and content.
Audit Logs are an Enterprise pricing feature.
Whenever a member of your project creates a new model, updates a content entry, or deletes a webhook, the Audit Logs will retain these actions.
Audit Logs Explorer
On eligible projects, Audit Logs are visible for the Owner & Admin role. You can also grant access to Audit Logs by creating a custom role with the "Can view Audit Logs" permission.
Clicking on a specific row in the Audit Logs table allows you to see all details for that certain event, including the payload that shows all changes that happened on this event.
Audit Logs Details View
Each Audit event will have the following fields present:
| Field | Description |
|---|---|
| Entity ID | The ID of the Resource, e.g. Model ID or Content Entry ID. |
| Timestamp | The time at which the change occurred. |
| Type (Resource Type) | The type of resource that has been altered. |
| Action | The action that was performed on the resource. |
| Environment | The environment in which the change occurred. |
| Payload | The full payload of the change. We won't include the payload for content changes. |
| TriggeredBy | The Member email or Token that triggered the change. |
| TriggerType | Can be USER, PAT, OPEN or THIRD_PARTY. |
Here's a list of resource types the Audit Logs will keep track of:
These are the actions that can be performed on resources:
You can filter the logs by the event fields.
If you want to search for the audit logs of a specific team member, select the trigger type "USER" and provide their email for "triggered by".
The Timestamp column on the table is also clickable, and allows to order the table by timestamp_ASC (ascending).
The table will be ordered descending by default, so the newest entry is shown first.