ChecklistClaude Team deployment

The steps to deploy Claude Team at a law firm.

Six phases, from workspace creation to post-launch follow-up. Checkboxes are saved in your browser: return at any time without losing your progress.

Compiled from academy.claude.com and support.claude.com

0 / 27

Create the workspace

Go to claude.ai/login with a professional email address. A Team plan requires at least 2 members and excludes @gmail, @yahoo and @hotmail addresses.

Create the Team organisationUse a professional email at claude.ai/login and select the Team plan. Choose monthly or annual billing. If you already have a Pro/Max account, use claude.ai/upgrade to create the organisation without losing your personal account.

Configure allowed domainsSettings › Organization: add the firm’s email domain or domains so only your colleagues can join.

Define administrator rolesThree levels: Primary Owner (you), Owner (co-admins), Member (users). Appoint at least one backup Owner.

Security and admin settings

Note: on a Team plan, Cowork is enabled by default for the entire organisation. Granular group controls are reserved for Enterprise. It is all or nothing.

Check Cowork settingsSettings › Cowork: cloud sessions enabled by default, integrated browser rolling out, auto-approve on. Disable what is unsuitable.

Configure network capabilitiesOrganization settings › Capabilities: web search and web fetch are active by default. Disable if necessary (for example, for sensitive data). Also check network egress rules.

Check the data policyTeam has no configurable retention (reserved for Enterprise). Your data is not used to train Claude. Make the firm aware of incognito chats for sensitive topics.

Configure user feedbackChoose whether user feedback (thumbs up/down) is shared with Anthropic.

Invite and provision users

On a Team plan, invitations are sent manually through the admin console. No SCIM/JIT (reserved for Enterprise).

Choose seat typesTwo options per user: Chat only (web interface + Cowork) or Chat + Code (adds Claude Code in the terminal). Identify who needs Code (developers, data, automated litigation) and who will stay on Chat.

Buy the required seatsSettings › Organization › Members. Provision the right mix of Chat / Chat+Code. On a usage-based model, note that the Claude Code spending limit defaults to $0.

Send invitationsInvite each member by email from the admin console. Prepare the address list beforehand.

Set the organisation’s custom instructionsSettings › Custom Instructions: add default instructions for the whole firm (response language, tone, practice rules, required notices). Users can supplement them, not bypass them.

Configure spending limits (if usage-based)Set a reasonable spending cap per user to avoid surprises on Chat + Code seats.

Prepare a first-login guideInvitation link, login steps, desktop app installation (macOS/Windows), and how to choose ‘Claude account with subscription’ if Claude Code is enabled.

Connectors and tools

Connectors work in two stages: the admin enables the connector for the organisation, then each user authorises their own account through OAuth.

Enable priority connectorsAccording to your firm’s tools: Google Drive, Slack, GitHub, Microsoft 365, Notion. Start with those already used daily.

Choose skills/plugins governanceThree options: Admin Curated (you pre-approve everything), Guided Creation (users create, you approve), Fully Open (full autonomy). Guided Creation is the balance recommended by the academy.

Configure the plugin marketplace (optional)If you have specific plugins to deploy, pre-approve them in the marketplace and define distribution policies.

Create 2 to 3 pilot ProjectsProjects are at the heart of Claude Team: shared context, reference documents and custom instructions per project. Create them for priority use cases (drafting, analysis, serial litigation).

Test a complete workflowBefore deployment, a user (you or a champion) completes a task from start to finish with a connector and a Project. Check that everything works.

Launch and onboarding

Academy targets: 70% weekly active users, 25+ messages per user per week, 3 hours saved per person per week. Measure through the admin dashboard (Analytics).

Identify 2 to 3 championsGive them early access, talking points and a dedicated channel (Slack/Teams) for first-line support.

Send the launch announcementInclude: why Claude, the invitation link, installation guide, first training session date and who to contact for problems.

Schedule the ‘101’ session (30 to 60 min)Cover interface navigation, effective prompts, Projects and Artifacts. Each participant should complete a real task during the session.

Share Claude Academy resourcesRecommended courses: Claude 101 (2 h 30, 13 lessons), Introduction to Claude Cowork (2 h 30, 14 lessons), AI Fluency: Framework & Foundations (4 h).

Set up weekly office hours30-minute drop-in sessions during the first 4 to 8 weeks. Champions lead, with IT present for access problems.

Post-deployment follow-up

Check adoption at day 7Admin dashboard › Analytics: active user count and message volume. Follow up with people who have not logged in.

Collect initial feedbackShort survey at day 7: what have you tried? What worked? Where are you stuck? Aim for satisfaction of 4.0+/5.0.

Share the first success storiesHighlight 2 to 3 successful use cases at the firm. Concrete successes accelerate adoption.

Schedule the one-month reviewNatural progression recommended by Anthropic: basic features (Projects, Artifacts, Connectors), then Intelligence (Research), then Integrations (Skills, advanced Cowork).

✱

Key resources

Official Team guide ↗

Team plan setup and support

Cowork admin guide ↗

Cowork deployment

Scaling Cowork ↗

Champions, governance and metrics

Claude for Work ↗

Professional tutorial collection