What Claude Visibility shows and how it works
What Claude Visibility shows for a client, how Claude's OpenTelemetry export feeds it, what it needs, and who does each part.
Written By The Lemhi Product Team
Last updated 10 days ago
Claude Visibility shows how a client's people use Claude: who is active, how many prompts they send, which models they use, which tools and connectors Claude runs for them, and what that use would cost at API prices. It lives on the client's AI Usage page, on the Claude tab. This article is for the MSP admin, technician or vCIO deciding whether to turn it on for a client.
What you see
Details are in Read the Claude activity views.
How the data gets to Lemhi
OpenTelemetry (OTel) is an open standard for sending activity data from an app to a monitoring tool. OTLP is the protocol it uses to send that data over the network. Any OTel-compatible tool can receive it, Lemhi included.
Claude has a monitoring export built on OpenTelemetry. When the client's Claude admin enters an OTLP endpoint in Claude's admin settings, Claude sends an event each time someone submits a prompt, a tool runs, or Claude calls a model. Per Anthropic's documentation, those events carry the model used, token counts, an estimated cost in US dollars, the tool name and whether it succeeded, and the person's account and email. Nothing is sent until an admin enters an endpoint.
For Claude Visibility, the endpoint is Lemhi's, and the client's monitoring key in the OTLP headers tells Lemhi which client the activity belongs to.
What Lemhi does with it:
Counts prompts, people, models, tool uses and estimated cost. Counts roll up hourly.
Matches each person's email to the client's employee list to show a name and department. With no single match, the email shows.
Doesn't collect what people type or what Claude replies. Anthropic's export can carry prompt and response text when the client's devices are set to capture it.
Claude's export always includes each person's email address and the paths of the folders connected to a session, whatever the client's content settings. The full list of limits is in What Claude Visibility can't see.
What you need
The client has Claude Team or Enterprise.
The client's Claude admin, who can change Claude's admin settings.
The Tenant Admin role in Engage, to connect Claude, see the People view, and regenerate or revoke the configuration.
Claude Visibility doesn't need a Microsoft 365 link. It works for a client with no GDAP connection.
Who does what
One destination per Claude organization
Claude sends activity to one destination per organization. Entering Lemhi's endpoint replaces any existing one. If the client or your MSP already sends Claude monitoring to another tool, that tool stops receiving it once Lemhi's endpoint is saved.
Check with the client's Claude admin before you send the steps. If the OTLP endpoint field in Claude's Monitoring settings already holds a value, decide with the client which destination to keep.
Next
Connect a client's Claude organization
Related
Was this helpful?
Still need help? Ask the team