Loading tutorials…
Loading tutorials…
Claude Team unlocks shared Projects, no-train data privacy, and admin controls. Setup is more nuanced than the marketing pages suggest. This is the practical walkthrough.
Who this is forAdmins setting up Claude for marketing teams of 3-50 people. Whether you need Pro ($20/mo solo), Team ($30/user/mo), or Enterprise (custom) depends on your specific needs.
What you'll need
Step 1
Pro solo, Team for 2-50 users, Enterprise for 50+ OR strict compliance.
Pro ($20/mo, single user): full features for one person. Projects, Artifacts, 200K context.
Team ($30/user/mo, 2-50 users): shared Projects within workspace, no training on data by default, admin console, member management.
Enterprise (custom pricing, typically $60-100/user/mo): unlimited users, SSO/SAML, audit logs, custom data retention (1-365 days), higher rate limits, priority support.
Team is right for: marketing teams 3-50, no SSO required, standard data privacy needs.
Enterprise is right for: 50+ users, SSO required, regulatory compliance (financial, healthcare), custom retention required.
Most growth-stage marketing teams land on Team. Pick Enterprise only when you have a specific Enterprise-only requirement.
Step 2
claude.ai → Settings → Workspace → Upgrade to Team. Add seats, payment, workspace name.
If you are on Pro and ready to add team members, upgrade. Or start fresh as Team.
Go to claude.ai/team. Click "Upgrade to Team."
Choose monthly or annual billing. Annual saves ~15%.
Add initial seats (you can adjust later — minimum 5 seats on Team).
Set up payment method.
Name your workspace: your company name (e.g., "EverestX Marketing").
You are now the workspace admin.
Step 3
Workspace settings → set member permissions, default Project visibility, data retention.
Click your avatar → Workspace settings.
Member permissions: who can create Projects, invite members, manage billing. Default: Members can create Projects + invite (Admins can configure).
Default Project visibility: "Workspace" (shared with all members) vs "Personal" (private to creator). For marketing teams, default to "Workspace" — encourages sharing.
Data retention: default 30 days. Adjust based on your data governance policy.
Models: choose which models the workspace can use. Sonnet 4.7 is default. Some teams restrict Opus access for cost control.
Step 4
Workspace settings → Members → Invite. Send via email. Each is $30/mo seat.
In Workspace settings → Members → "+ Invite Members."
Enter email addresses. Use work emails (firstname@yourdomain.com), not personal Gmails.
Assign role: Admin (can change settings + billing) or Member (uses Claude but cannot change workspace).
Send invites. Members receive email; they accept and are added.
Each member = one seat. Billing updates accordingly.
Step 5
Create 5-7 marketing Projects with "Workspace" visibility. Team uses these as the canonical workflows.
Build Projects for: Blog Writing, Email Sequences, Ad Copy, Research Synthesis, Voice Coach, Social Posts, SEO Briefs.
For each, set visibility to "Workspace" in Project settings.
Members can access via Projects sidebar.
Document each Project in a Notion/Confluence page: purpose, when to use, expected output.
Iterate over time based on team feedback. Each Project improves quarterly.
Step 6
Document what data can be pasted into Claude. Even with no-training, common-sense rules matter.
Team and Enterprise do NOT train on your data. But manage what gets pasted.
Document: paste — marketing copy, ideas, briefs, anonymized data. Do NOT paste — customer PII, passwords, payment data, source code (unless explicitly approved).
Share the norms doc with all team members.
For Enterprise: enable audit logs (Workspace settings → Security → Audit Logs).
Annual training reminder on AI privacy norms.
Step 7
Monthly: review active members. Reclaim unused seats. Add seats for power users.
Workspace settings → Members → shows last-active dates.
Members not used Claude in 30 days: reach out. Training need? Wrong tool?
Heavy users consistently hitting limits: consider Enterprise OR add another seat.
Quarterly: reclaim seats unused for 60+ days. Saves $30/mo per seat reclaimed.
Track ROI: what marketing work does Claude enable that previously required hiring or hours? Make value visible to leadership.
Common mistakes
Picking Team when Enterprise was needed
What goes wrong: Set up Team for 30 users. Six months later, compliance requires SSO + audit logs. Migrate to Enterprise mid-flight, losing Projects and shared knowledge.
How to avoid: Assess compliance needs BEFORE picking tier. If you need SSO, audit logs, custom retention, Enterprise from day one. Migration is painful.
Using personal Gmails for member invites
What goes wrong: When an employee leaves, their personal Gmail-bound seat goes with them. You lose their Projects, history, and shared context.
How to avoid: Invite with work emails. SSO if Enterprise. When employees leave, you control the email and account.
No data privacy norms
What goes wrong: Team members paste customer PII, financials, source code. Even on Team/Enterprise, this expands attack surface and may violate compliance.
How to avoid: Document data norms BEFORE rolling out. What to paste, what not to. Annual refresher.
Projects accumulate without governance
What goes wrong: Team builds 50 Projects over a year. No documentation, no naming convention, no quality control. Library becomes junk drawer.
How to avoid: Naming convention from day one. Documentation page listing all Projects. Quarterly audit + cull.
Paying for unused seats
What goes wrong: $30/mo per seat. 10 unused = $300/mo = $3,600/year wasted.
How to avoid: Quarterly seat review. Reclaim unused 60+ days. Add back when needed.
Recap
Done — what's next
How to use Claude Projects for marketing workflows
Read the next tutorial
Hand it off
Claude Team setup is more nuanced than the marketing pages suggest. A specialist can advise on tier choice, set up the workspace, and build the initial Project library. From $14-16/hr — most Team setup engagements land at $300-700.
See specialist rates
No. Both Team and Enterprise have data training OFF by default. Pro and Free DO train by default unless you opt out in settings.
Yes. Pro users can be invited to a Team workspace. Personal Pro remains separate. For full consolidation, invite to Team and have them downgrade Pro.
5 seats minimum on Team plan. Most teams start at 5-10 and scale to 10-30 over 6-12 months.
Yes. Enterprise supports SAML SSO with major providers (Okta, Azure AD, Google Workspace). All members authenticate via your IdP.
Default 30 days. Admins can adjust in Workspace settings (7-180 days on Team, customizable on Enterprise).
Claude for Marketing
Claude Projects are how you stop re-explaining your brand voice every conversation. Set up once, every chat in the project starts with full context. The leverage move for serious Claude users.
Claude for Marketing
Voice is what makes content recognizable as YOU. Voice drift is what makes content interchangeable. Claude is the strongest tool for locking voice across teams. This is the workflow.
Claude for Marketing
Two LLMs, two personalities. ChatGPT is the generalist + ecosystem. Claude is the writer + reasoner. The senior-marketer pattern is using both strategically.
ChatGPT for Marketing
ChatGPT Team and Enterprise unlock shared GPTs, no-train data privacy, and admin controls. Setup is more nuanced than the marketing pages suggest. This is the practical walkthrough.