Guide›Security & compliance
Security & complianceIntermediate7 min

Audit logs

Every action taken in a Myndlab project — builds, deploys, setting changes, team member actions — is recorded in the audit log for compliance and incident review.

What is logged

The audit log captures a complete record of actions that affect your project's state or security posture. Logged event categories include:

1
Build events
Build started, build succeeded, build failed — including the prompt text, credit cost, and build duration.
2
Deploy events
Deploy initiated, deploy completed, deploy rolled back, preview URL changed.
3
Setting changes
Any change to project settings — environment variables added or removed (values are redacted), custom domain changes, plan upgrades or downgrades.
4
SSO logins
Successful and failed SSO authentication attempts, including the identity provider used and the user's IP address.
5
Team member actions
Team member invited, accepted, removed, role changed.
6
API key lifecycle
API key created, API key last used (date only), API key revoked.
7
Credit purchases
Credit top-up amount, payment method last four digits, invoice ID.

Who can access logs

Audit log access is restricted to team members with the Admin role. Editors and Viewers cannot view, filter, or export audit logs. This restriction cannot be changed.

The project owner always has Admin access and therefore always has audit log access, regardless of any SSO role mapping configuration.

Accessing logs

1
Open Project Settings
Click the gear icon in the top-right corner of the Build screen.
2
Go to Security
Select the "Security" tab in the settings sidebar.
3
Open Audit log
Click "Audit log" in the Security section. The log loads the most recent 100 events by default, newest first.

Each log entry shows: timestamp (UTC), actor (email address and display name), event type, affected resource, and a JSON detail payload with any additional context specific to the event type.

Filtering and searching

The audit log panel supports several filter options to narrow a large log to the events you care about:

1
Date range
Set a start and end date. The picker defaults to the last 30 days.
2
Actor
Filter by a specific team member's email address.
3
Event type
Select one or more event categories from the dropdown (e.g. build_failed, team_member_removed).
4
Free-text search
Search across event descriptions and JSON detail payloads. Useful for tracking down a specific build ID or IP address.

Filter state is preserved in the URL, so you can bookmark or share a filtered view with another admin.

Exporting logs

To export, apply the filters you need, then click the Export CSV button in the top-right of the audit log panel. The export includes every event matching the current filters — not just the 100 shown on screen.

The CSV format is:

text
timestamp_utc, event_type, actor_email, actor_display_name, resource_type, resource_id, detail_json

For automated export pipelines, use the Audit log API endpoint instead (available on Business and Enterprise plans):

bash
curl -H "Authorization: Bearer $MYNDLAB_API_KEY" \
  "https://api.myndlab.com/v1/projects/{project_id}/audit-logs?from=2026-01-01&to=2026-05-25"

Log retention

Log retention depends on your plan:

1
Free
90 days of audit log history.
2
Pro
1 year of audit log history.
3
Business
1 year of audit log history.
4
Enterprise
Unlimited retention. Logs are stored in Myndlab's GDPR-compliant EU infrastructure and can optionally be forwarded to your own storage.

Logs beyond the retention window are permanently deleted and cannot be recovered. If you need longer retention on a lower plan, export logs regularly and store them in your own system.

Using logs for ISO 27001 / 9001 evidence

Audit logs are a core evidence artefact for ISO 27001 (information security) and ISO 9001 (quality management) audits. Myndlab's audit log covers several controls directly:

1
Access control (ISO 27001 A.9)
SSO login events and team member role changes provide evidence that access is controlled and reviewed.
2
Operations security (ISO 27001 A.12)
Build and deploy events provide a tamper-evident record of all changes to the production environment.
3
Cryptographic controls — API keys (ISO 27001 A.10)
API key creation and revocation events demonstrate key lifecycle management.
ℹ
Note.Myndlab holds ISO 9001 and ISO 27001 certifications (certificate numbers 07020001075 and 07020001076, valid until May 2029). Audit logs are a key part of maintaining these controls. You can request a copy of Myndlab's certificates for your supplier due-diligence pack by emailing compliance@myndlab.com.

Automated log forwarding

Enterprise plan projects can forward audit log events in real time to an external destination as they occur, rather than relying on periodic CSV exports.

1
Webhook forwarding
Provide an HTTPS endpoint. Myndlab will POST each audit event as a JSON payload within seconds of it occurring. The request is signed with an HMAC-SHA256 signature so you can verify authenticity.
2
SIEM integration
Pre-built connectors are available for Splunk, Datadog, and Microsoft Sentinel. Configure them in Project Settings › Security › Log forwarding.

To configure log forwarding, go to Project Settings › Security › Log forwarding and follow the setup wizard for your chosen destination.