---
date: 2026-11-17
title: Read-access audit logs
description: Langfuse can now record reads of traces, observations, scores, sessions and experiments as audit events, so you can review who accessed sensitive data.
author: Steffen
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

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](/docs/administration/audit-logs#read-access-coverage).

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=enforced` on the web container to record reads in every organization. This needs Langfuse `v4.82.0` or later, and an Enterprise or Government license key.

- [Read-access audit logs](/docs/administration/audit-logs#read-access)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-11-17-read-access-audit-logs.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.
