---
title: Claude Team Projects Setup for Client Knowledge Bases
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-03-19-impromptu-zoom-meeting-131308678.md
tags:
- claude
- ai-tools
- knowledge-management
- content-marketing
- blogging
- workflow
- sop
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Claude Team Projects Setup for Client Knowledge Bases

Claude's Team Projects feature provides a persistent, shared knowledge base that constrains the AI to client-specific facts, terminology, and guidelines before generating any content. This prevents the factual errors and hallucinations that occur when writers use general-purpose AI sessions without client context.

The pattern emerged from recurring client complaints (Bluepoint, Citrus America) about blog posts containing incorrect product details and prohibited terminology — errors that could have been avoided with a centralized, always-on knowledge layer.

See also: [[wiki/knowledge/content-marketing/blog-production-workflow]] for how Team Projects fit into the full Claude → Surfer → Claude → Google Doc pipeline.

---

## Why Team Projects, Not Personal Projects

Claude offers both personal and team project spaces. **Always use Team Projects for client work.**

- Personal projects are private by default and invisible to colleagues
- Team Projects are accessible to everyone on the Asymmetric Claude account
- You can identify Team Projects by the **building icon** in the sidebar
- Navigate to them via: sidebar → Projects → **Team**

> ⚠️ Karly noted she had been working in personal project folders without realizing they weren't shared. Check your existing client projects and migrate any that are still private.

Mark is researching whether a default-to-team setting exists at the account level — watch for an update in Slack.

---

## Project Structure

Each client should have one Team Project containing two core documents:

### 1. Client Profile
A factual overview of the client's business. Suggested fields:
- What does this client do?
- What is their business model?
- Who are their primary customers?
- Who are their main competitors?
- What geographies do they serve? (e.g., Skollin does **not** operate in Illinois)
- What type of facility/product/service are they? (e.g., Cordwainer is a **memory care** facility, not assisted living)

### 2. Writing Guidance
A rules document covering terminology and content constraints. Suggested fields:
- Words/phrases **never** to use (e.g., for Citrus America: never say "peel oil" standalone; never say "crushing" — use "squeezing")
- Preferred terminology and framing
- Factual constraints (e.g., Bluepoint reverse ATM: no placement fee — revenue comes from transaction volume only)
- Tone and style notes
- Target blog length and structure preferences

Update this document immediately whenever a client flags an error. The goal is to never repeat the same mistake twice.

---

## Supported File Types

Claude can read virtually any file format uploaded to a project:
- PDF (works very well)
- Word documents (.docx)
- Google Docs (via link or export)
- PowerPoint / slides
- Spreadsheets
- Plain text / Markdown

Upload as many relevant documents as useful — strategic frameworks, past strategy call notes, brand guidelines. The tradeoff is that more files = longer initial load time at the start of each session.

---

## Starting a Session Correctly

When you open a client project to begin writing, **always start by prompting Claude to review its context**:

```
Review the files in this project and confirm you're ready to write for [Client Name].
```

Claude will read all uploaded documents and confirm it has internalized the constraints before you begin. You can also ask it to review previous chats in the project for continuity across sessions:

```
Review the files and our previous chats in this project, then confirm you're ready.
```

---

## Project Instructions Field

Each project has an **Instructions** field (separate from uploaded files) that applies globally to every conversation in that project. Use this for standing directives that should never be overridden, such as:

- "Always write in second person"
- "Never mention competitor names"
- "All blog posts should be 1,200–1,500 words"

Instructions are loaded before files and before any user prompt.

---

## Scope Limitation to Be Aware Of

Team Projects are intentionally narrow — Claude in a project context focuses on what's in that project and may give weaker answers to broad strategic questions. If you need open-ended strategy brainstorming, do that in a **regular Claude chat** (not inside a project), then bring the output back into the project for refinement.

---

## Current Setup Status (as of April 2026)

| Client | Profile Created | Writing Guidance Created | Uploaded to Team Project |
|---|---|---|---|
| Citrus America | ✅ (pending Miriam approval) | ✅ (pending Miriam approval) | ⏳ After approval |
| Skollin | ⏳ Melissa creating | ⏳ Melissa creating | ⏳ |
| Didion | ⏳ Melissa creating | ⏳ Melissa creating | ⏳ |

**Owner:** Melissa Cusumano is responsible for creating and uploading profile + guidance docs for all active clients.

---

## Related

- [[wiki/knowledge/content-marketing/blog-production-workflow]]
- [[wiki/knowledge/ai-tools/surfer-seo-integration]]
- [[wiki/knowledge/ai-tools/claude-skills-and-automation]]
- [[wiki/clients/citrus-america/_index]]
- [[wiki/clients/skollin/_index]]