← Back to changelog
Steffen Reuther
November 17, 2026
Read-access audit logs
Langfuse can now record reads of traces, observations, scores, sessions and experiments as audit events, so you can review who accessed sensitive data.
Audit logs can record who read your data, not only who changed it. With read-access logging on, Langfuse records an access event when a user or API key opens, lists, searches, exports or downloads traces, observations, scores, sessions or experiments. This covers the Langfuse UI and the public API routes and MCP tools.
Each event records:
- the user or API key and their role;
- the route and request parameters;
- the number of rows returned and the ids of the returned rows;
- whether the read succeeded or was denied;
- the client IP address and user agent.
Access events appear in the audit log viewer and its export, next to change events.
How to turn it on
- Langfuse Cloud Enterprise: go to Organization settings → Audit Logs and turn on Access Logging. On Langfuse Cloud HIPAA it is always on.
- Self-hosted Enterprise: use the same organization setting, or set
LANGFUSE_AUDIT_LOG_ACCESS_EVENTS=enforcedon the web container to record reads in every organization. This needs Langfusev4.82.0or later, and an Enterprise or Government license key.
Was this page helpful?