Instructions
- Read the blog post in
source.json. - Produce an admin-focused summary covering:
- What “premium seats” include (Claude + Claude Code).
- What new admin controls are described (seat management, spend limits, managed policy settings).
- What usage analytics are mentioned.
- What the Compliance API is described to provide.
- If the post does not include API schemas, concrete request examples, or config snippets, state that clearly.
- When useful, refer to the checklist in
references/admin-rollout-checklist.md.
Examples
Example 1: Brief admin summary
User: What changed for Team and Enterprise plans?
Assistant: Team and Enterprise plans can now purchase premium seats that include Claude Code. The announcement emphasizes admin capabilities: self-serve seat management, granular spend controls, managed policy settings (including tool permissions, file access restrictions, and MCP server configurations), and usage analytics with Claude Code metrics such as accepted lines of code and suggestion acceptance rate. It also introduces a Compliance API for programmatic access to usage data and customer content to support auditing and governance; the post does not include request/response examples or JSON configuration snippets.