Claude Teams Plan Guide: Pricing, Cowork, and Administration

Anthropic's share of enterprise AI spending reached 34.4% in May 2026, quadrupling year-over-year according to the Ramp AI Index. Much of that growth came from teams adopting Claude's mid-tier plan, which slots between individual Pro subscriptions and full Enterprise contracts.

The Claude Team plan is built for groups of 5 to 150 people who need shared access to Claude's models, centralized billing, and security controls without the overhead of a full Enterprise deployment. Every seat gets access to all available Claude models, a 200k token context window, and priority access during peak periods.

The full feature set ships with both seat types. Claude Code handles terminal-based coding and automation. Claude Cowork enables collaborative AI sessions where team members work together with Claude in shared contexts, building on each other's projects and artifacts. Claude Design covers visual work. Beyond the core products, teams get connectors for Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365, and Slack, plus enterprise search that pulls answers from across those connected tools.

Admin features separate the Team plan from individual subscriptions: SSO with SAML support, domain verification and capture, centralized billing with organizational spending caps, and the option to prevent model training on your content by default. These controls matter once you move beyond a handful of people paying individually, because they give IT visibility into who uses what and how much it costs. Account creators must use a business email address. Public domains like @gmail.com and @yahoo.com are not allowed for the primary admin, though you can permit them for other team members later.

The Team plan sits between Pro ($20/month for individuals) and Enterprise (custom pricing, typically starting around $60/user/month). Understanding where each tier fits helps you avoid overpaying or outgrowing your plan within months.

Standard seats cost $20 per month on annual billing ($25 monthly). They work for team members who use Claude regularly but don't push heavy workloads. Think project managers reviewing documents, marketers drafting content, or analysts running occasional research sessions. Standard gives about 1.25x the usage of an individual Pro subscription, with weekly limits that reset per member rather than pooling across the team.

Premium seats run $100 per month on annual billing ($125 monthly). They're built for power users: engineers running Claude Code for hours each day, researchers doing deep analysis across long documents, and content teams producing high volumes of output. Premium provides about 6.25x the usage of Pro, roughly five times what a Standard seat offers. For heavy Claude Code users, Premium often means the difference between a productive afternoon and waiting for a weekly limit to reset.

Enterprise adds the governance layer that regulated industries require: SCIM provisioning, audit logs, compliance APIs, custom data retention, role-based access controls, HIPAA-ready offerings, and dedicated SLAs. Enterprise pricing works differently. The seat fee covers access only, and all usage is billed separately at API rates.

Quick comparison:

• Pro: $20/month, individual only, no admin controls
• Team Standard: $20/month (annual), 5-150 seats, SSO, enterprise search, 1.25x Pro usage
• Team Premium: $100/month (annual), 5-150 seats, same features, 5x Standard usage
• Enterprise: Custom pricing, 50+ users, SCIM, audit logs, compliance, SLAs

If your team is under 50 people and doesn't need audit logs or compliance APIs, the Team plan covers what you'll actually use. If you're in a regulated industry or need SCIM directory sync, start the Enterprise conversation early.

SSO setup on the Team plan takes about 30 minutes if you have your identity provider credentials ready. Claude supports SAML 2.0 through six providers: Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud, and Duo.

Domain verification comes first. Navigate to Organization settings, add your company domain, and create the TXT DNS record that Claude generates. Local propagation usually takes about 10 minutes, though global propagation can take 24 to 48 hours. You need an Owner or Primary Owner role to complete this step.

Connecting your identity provider follows the WorkOS integration flow. Each provider has a dedicated setup guide in the Claude Help Center with provider-specific configuration steps. The general pattern: create an application in your IdP, configure the SAML endpoints Claude provides, map user attributes, and test the connection before rolling out to the full team.

Domain Capture claims your verified domain so new signups from your company email automatically join your workspace instead of creating separate personal accounts. This prevents shadow usage where employees sign up individually and fragment your organization's Claude activity across disconnected accounts. Once enabled, anyone with a matching email domain gets routed to your team workspace on signup.

Provisioning options control how new members get added:

• Invite Only (default): Admins manually send invitations. The most controlled approach, and the right choice if you need to approve each person before they get access.
• Just-in-Time (JIT): Anyone who authenticates through SSO with your domain gets automatically added with a User role. Faster onboarding, but you give up control over who joins.
• SCIM: Full directory sync from your identity provider with automatic role assignment and deprovisioning. Available on Enterprise plans only.

The enforcement toggle lets you require SSO for all logins or leave it optional. Requiring SSO ensures every login goes through your identity provider's security policies, MFA requirements, and conditional access rules. Most teams should enable enforcement once SSO is confirmed working, since it closes the gap where someone could bypass your IdP by logging in with just their email.

Give your Claude team persistent file workspaces

50GB free storage with MCP access for Claude Code, built-in RAG for semantic search, and branded shares for client delivery. No credit card required.

Sign Up Free

Enterprise search gives your team a single place to query across every connected tool without leaving Claude. When an admin enables it, Claude creates a dedicated "Ask Your Org" project with system prompts maintained by Anthropic for organizational knowledge retrieval.

Admin setup takes five steps:

1. Open the "Ask Your Org" option in the sidebar
2. Select "Set up for your org"
3. Choose which connectors to enable (Documents and Chat are recommended, Email is optional)
4. Add any additional tools from your organization's connector directory
5. Customize the project name (formatted as "Ask [Your Company Name]") and add a description

Once configured, the project appears as a starred item for every team member. Each person authenticates with their own credentials for the connected services, which means search results are permission-aware. A team member only sees content they already have access to in the original system.

Supported connectors include Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 (including SharePoint), and Slack. When someone asks a question in the Ask Your Org project, Claude searches across all connected sources and builds a response with source citations. This works particularly well for questions that span multiple tools. Something like "What was the decision on the Q3 pricing change?" might pull from a Slack thread, a Google Doc, and an email chain to assemble a complete answer.

Connector management is layered. Owners enable each connector at the organization level first. Individual members then authenticate with their own accounts for each service they want to search. You can also restrict which connectors are available if certain integrations shouldn't be used organization-wide.

Search activity counts toward each member's standard usage limits. If someone is running enterprise search queries dozens of times a day alongside regular Claude usage, that's a good signal they might benefit from a Premium seat.

The ability to mix Standard and Premium seats within a single Team plan is one of the less obvious advantages over plans that force a single tier for everyone. Match seat type to actual usage rather than job title.

Premium seat candidates are people who would otherwise wait for weekly usage resets:

• Engineers running Claude Code throughout the day for pair programming and code generation
• Researchers conducting multi-hour deep analysis sessions across long documents
• Content teams producing large volumes of output with extended iterative refinement

Standard seat candidates use Claude regularly but in shorter bursts:

• Project managers reviewing summaries and asking follow-up questions
• Executives using the Ask Your Org project for quick company knowledge lookups
• Team members who interact with Claude a few times per day rather than continuously

A practical example: A 10-person team might start with 7 Standard and 3 Premium seats. The three engineers who pair-program with Claude Code all day get Premium. Everyone else starts on Standard. That mix costs $340 per month on annual billing ($140 for Standard plus $200 for Premium) compared to $1,000 per month if everyone had Premium seats.

Reassignment is straightforward. If someone's usage pattern changes, you can upgrade or downgrade their seat type in Organization settings without purchasing a new seat. This flexibility matters during project sprints when someone temporarily needs higher limits, or when a new hire turns out to be a heavier user than expected.

Spending caps add another layer of cost control. Admins can set organizational and individual spending limits so Premium seats don't generate surprise bills. Usage beyond included limits is available through additional credits, but the caps keep monthly costs predictable.

Track usage for the first month before committing to a final seat mix. If your entire team consistently hits Standard limits, moving everyone to Premium is often cheaper than buying additional usage credits on top of Standard seats.

Claude conversations produce outputs that need to live somewhere: code files, research summaries, design specs, analysis reports. The Team plan keeps those within Claude's interface, but most workflows eventually need the output in a shared location where non-Claude-users can access it too.

Local storage works for individual developers pulling code directly into their repos. Google Drive or SharePoint handles document sharing for teams already embedded in those ecosystems. S3 covers programmatic storage for engineering teams building pipelines. Each option works, but none is specifically designed for the pattern where AI-generated output moves between agents, team members, and external stakeholders with version control and access management.

Fast.io provides workspaces built for agentic teams. An engineer's Claude Code session can write output directly to a Fast.io workspace through the MCP server, where files are automatically indexed for semantic search via Intelligence Mode. Another team member can then ask questions about that output through AI chat without downloading anything. The workspace becomes a shared layer between what Claude produces and what the team uses.

For teams that deliver Claude-generated work to clients, Fast.io's branded shares handle the last mile. An agent builds a deliverable, uploads it to a workspace, and the team reviews it before sharing through a branded portal with Send, Receive, or Exchange workflows. The ownership transfer model lets an agent create the workspace structure and hand control to a human when the work is ready.

The free agent plan includes 50GB of storage, 5,000 monthly credits, and 5 workspaces with no credit card required. For a Claude Team evaluating where to store and share AI output, that's enough capacity to test the full workflow before committing budget.