Org-level AI-fluency insight for Team/Enterprise admins (beyond usage volume)

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Sep 9, 2026 · closed Sep 12, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Admin analytics for Team/Enterprise already cover adoption and cost well — active users, chats/messages per user, artifacts created, and (for Claude Code) active developers and session counts. What’s missing is any signal about how effectively people are using Claude, not just how often. As orgs go through AI-skilling transitions, team leads and L&D need a way to see where real capability gaps are. Right now that question gets answered informally, if at all.

Proposed Solution

An opt-in “AI fluency” layer alongside existing usage analytics:
• Short, periodic self-assessment prompts (a lightweight skills rubric) that employees complete voluntarily inside Claude
• Aggregate, team-level rollups for admins only — e.g. “62% of the Platform team feel confident with iterative prompting; 25% want help with agentic workflows” — never an individual score tied to a name
• Optional surfacing of which official Anthropic learning resources a team has completed, rolled up the same way spend and adoption already are
Explicitly out of scope: device or session data, message content, or anything that reads as covert monitoring. This only works if it’s transparent and opt-in — anything that feels like surveillance just pushes people to avoid Claude for real work, defeating the purpose.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Every enterprise customer navigating an AI transition is asking some version of “who on my team actually gets this, and who needs help.” A trustworthy, privacy-respecting way to answer that would be a genuine differentiator for Claude for Enterprise.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗