What Claude Visibility can't see
The limits of Claude's activity export: plans, surfaces, content, devices, and people who never used Claude.
Written By The Lemhi Product Team
Last updated 10 days ago
For anyone reading a client's Claude activity, or explaining it to the client. These are the six limits listed under What Claude Visibility can't see on the Claude tab, with what each one means in practice.
Claude Team or Enterprise is required
Pro and individual plans can't send activity. Claude's monitoring export is a Team and Enterprise feature.
Chat on claude.ai in a web browser isn't included
Claude desktop and Cowork are included. Desktop chat is included only when Chat and Cowork unified is on in the client's Claude admin settings. A person who only chats in a browser tab doesn't appear. The client's Claude admin can turn on the unified setting, as covered in Set up Claude monitoring for Lemhi.
Lemhi doesn't collect what people type or what Claude replies
Lemhi counts prompts, models, tool uses and estimated cost. Depending on how the client's devices are set up, Claude's export can carry that text; Lemhi doesn't collect it. Claude's export does always include each person's email address, which Lemhi uses to match people to the client's employee list.
Claude Code isn't covered yet
Anthropic's monitoring for Cowork doesn't include Claude Code sessions. A developer working in Claude Code doesn't show up in these views.
Activity is shown by person, not by computer
Claude can't tell Lemhi which computer was used, so the views group activity by the person's Claude account. You can't tie Claude use to a specific device from here.
Only people who used Claude in the period appear
Someone with a Claude seat who never used it, or didn't use it in the period you picked, can't be seen. Claude Visibility can't show how many seats the client pays for or which ones sit unused.
Related
Was this helpful?
Still need help? Ask the team