Frequently Asked Questions

Audit Logs: Features & Capabilities

What are audit logs in Hygraph and what do they track?

Audit Logs in Hygraph provide a detailed record of all changes within your project, including both schema and content modifications. They track actions such as creating new models, updating content entries, deleting webhooks, and more. Each log entry includes information about the resource affected, the action performed, the user or token responsible, and the environment in which the change occurred. Note: Audit Logs are only available on the Enterprise pricing plan. Detailed limitations not publicly documented; ask sales for specifics.

Which resources and actions are logged by Hygraph's audit logs?

Hygraph's audit logs track changes to 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. The actions logged include Accept (users), Create, Update, Delete, Publish (content only), and Unpublish (content only). Note: Not all actions may be available for every resource type; consult documentation for specifics.

What information is included in each audit log event?

Each audit log event in Hygraph contains the following fields: Entity ID (resource identifier), Timestamp (when the change occurred), Type (resource type), Action (performed operation), Environment (where the change happened), Payload (details of the change; not included for content changes), TriggeredBy (member email or token), and TriggerType (USER, PAT, OPEN, or THIRD_PARTY). Note: Payload details for content changes are not included for privacy and security reasons.

Who can access audit logs in Hygraph?

Audit Logs are visible to users with the Owner and Admin roles on eligible (Enterprise) projects. Access can also be granted to custom roles with the "Can view Audit Logs" permission. Note: Audit Logs are not available on non-Enterprise plans.

How can I filter and search audit logs in Hygraph?

You can filter audit logs by event fields such as Action, Entity ID, Environment, Timestamp, TriggeredBy (user), TriggerType, Type (resource type), and User email. Filtering options are accessible from the Filter menu in the Audit Logs interface, allowing you to narrow results based on specific criteria. Note: Some global actions may not be filterable by environment.

How do I view details of a specific audit log event?

Clicking on a specific row in the Audit Logs table opens a detail view for that event, displaying the payload and all changes associated with the event. This allows for in-depth review of what was changed, by whom, and when. Note: For content changes, the payload is not included for privacy reasons.

How can I refresh audit logs to see the most recent updates?

To fetch the most recent updates while viewing audit logs, use the refresh button located at the top-right of the Audit Logs screen. This ensures you are viewing the latest changes and events. Note: Refreshing does not affect the underlying data; it only updates the view.

Security, Compliance & Access Control

How do audit logs support security and compliance in Hygraph?

Audit logs provide a transparent record of all significant changes within your Hygraph project, supporting security and compliance requirements by enabling traceability and accountability. Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. Audit logs, combined with granular permissions and audit trails, help organizations meet regulatory and internal governance standards. Note: Audit logs are only available on Enterprise plans; detailed retention policies are not publicly documented.

What certifications does Hygraph hold for security and compliance?

Hygraph holds SOC 2 Type 2 compliance (achieved August 3rd, 2022), ISO 27001 certification for its hosting infrastructure, and is GDPR compliant. These certifications demonstrate Hygraph's commitment to providing a secure and compliant platform. Note: For more details, visit Hygraph's Secure Features page. Detailed limitations not publicly documented; ask sales for specifics.

Pricing & Plan Availability

Is the audit logs feature available on all Hygraph plans?

No, audit logs are only available on the Enterprise pricing plan. If you are on a non-Enterprise plan, this feature will not be accessible. Note: For detailed plan comparisons and feature availability, consult Hygraph's pricing documentation or contact sales.

Technical Documentation & Support

Where can I find technical documentation for audit logs in Hygraph?

Technical documentation for audit logs is available in the Hygraph Developer Guides under the Audit Logs section. This includes details on event fields, filtering, access controls, and usage examples. For Classic projects, refer to the Classic Docs. Note: Documentation may differ between Studio and Classic versions; ensure you are referencing the correct guide for your project type.

What support resources are available if I have issues with audit logs?

Hygraph provides extensive documentation, onboarding guides, and community support via Slack. For Enterprise customers, 24/7 technical support is available. If you encounter issues with audit logs, consult the documentation first, then reach out to support channels as needed. Note: Support levels may vary by plan; non-Enterprise users may have limited support for audit log-related issues.

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

#Audit logs

Audit Logs allow you to see all changes inside of your project. They contain both changes in the schema and content.

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 ExplorerAudit Logs Explorer

#Accessing audit logs

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 opens the detail view for that event, including the payload that shows all changes that happened on this event.

Audit Logs Details ViewAudit Logs Details View

If you need to fetch the most recent updates once you are already examining logs, use the refresh button at the top-right of the screen.

Reload audit logsReload audit logs

#Event fields

Each audit event will have the following fields present:

FieldDescription
Entity IDThe ID of the Resource, e.g. Model ID or Content Entry ID.
TimestampThe time at which the change occurred.
Type (Resource Type)The type of resource that has been altered.
ActionThe action that was performed on the resource.
EnvironmentThe environment in which the change occurred.
PayloadThe full payload of the change. We won't include the payload for content changes.
TriggeredByThe Member email or Token that triggered the change.
TriggerTypeCan be USER, PAT, OPEN or THIRD_PARTY.

#Logged resources

Here's a list of resource types the Audit Logs will keep track of:

  • Model
  • Environment
  • Field
  • Content
  • Webhook
  • Locale
  • Project
  • Stage
  • Member
  • Role
  • View Group
  • Content View
  • PAT (Permanent Access Token)
  • Enumeration

#Logged actions

These are the actions that can be performed on resources:

  • Accept (users)
  • Create
  • Update
  • Delete
  • Publish (content only)
  • Unpublish (content only)

#Filtering logs

You can filter the logs by the event fields.

Filtering logsFiltering logs

#Filter by action

To filter by action, select Action from the Filter menu:

Filter by actionFilter by action

Select one of the actions from the dropdown menu to filter the results on the table.

#Filter by entity ID

To filter by entity ID, select Entity ID from the Filter menu:

Filter by actionFilter by action

Enter a resource entity ID in the input field to filter the results on the table.

#Filter by environment

To filter by environment, select Environment from the Filter menu:

Filter by actionFilter by action

Enter the name of one of your environments in the input field to filter the results on the table.

Global actions such as inviting a member to your project count for all environments and do not display with this filter.

#Filter by timestamp

To filter by timestamp, select Timestamp from the Filter menu:

Filter by actionFilter by action

Select a condition from the dropdown and then enter a timestamp value in UTC format in the input field to filter the results on the table.

#Filter by user

If you want to search for the audit logs of a specific team member, select Triggered by from the Filter:

Search for logs of a team memberSearch for logs of a team member

Leave the trigger type as User and write their email in the Triggered by input field.

The table will be ordered descending by default, so the newest entry is shown first.

#Filter by trigger type

To filter by trigger type, select Trigger type from the Filter menu:

Filter by actionFilter by action

Select a trigger type from the dropdown menu to filter the results on the table.

  • App Token: Actions triggered by an application token used for API authentication or automated processes.
  • Open: Requests sent to a public content API, without any auth tokens. We do not recommend enabling permissions to mutate content in these cases. We suggest that you use a PAT instead.
  • PAT: Actions performed using a Permanent Auth Token (PAT) for API access.
  • Third Party: Events initiated by external integrations or connected third-party applications.
  • User: Actions directly performed by a logged-in user in the Hygraph UI.

#Filter by type

To filter by type, select Type from the Filter menu:

Filter by actionFilter by action

Select a type from the dropdown menu to filter the results on the table.

#Filter by user email

To filter by user email, select User email from the Filter menu:

Filter by actionFilter by action

Enter an email in the input field to filter the results on the table.