DEV Community

Cover image for Claude Projects: Set Up a Shared Team Knowledge Base Step by Step
epifive
epifive

Posted on Originally published at epifive.com

Claude Projects: Set Up a Shared Team Knowledge Base Step by Step

A Claude Project is a self-contained workspace with its own chat history, a set of uploaded files (project knowledge) and a set of written rules (project instructions). To build a team knowledge base, you create a project, upload your reference documents, write instructions that tell Claude how to use them, and share the project with the right people on a Team or Enterprise plan.

This guide uses the button and menu names from Anthropic's help center as of 2026-11-17, and it adds a structure for choosing what to upload and how to keep it current.

Who this is for and what you will have

This is for team leads, IT admins and operations staff who answer the same questions repeatedly: how to request access, what the refund policy is, how to run the month-end checklist. By the end you will have a shared project that answers from your own documents, with instructions that keep answers consistent, and a short maintenance routine.

If you are still choosing between tools, read ChatGPT Custom GPTs vs Claude Projects for sharing team knowledge first. For prompts to try once the project exists, see 25 Claude prompts for work.

Prerequisites

Need Detail
Claude account Projects are available on all plans, including free. Free users can create a maximum of five projects.
Team or Enterprise plan Required to share a project with other people.
Admin setting An owner can turn off "Share projects". If it is off, the Share menu shows "Project sharing is turned off by your administrator."
Source documents Current, owned by your team, and safe to share with everyone who will have access.

Check your documents before uploading anything. Anyone with Can view access can see project contents, knowledge and instructions, so do not upload salary tables, credentials or customer personal data unless every member is allowed to see them.

Plan the knowledge before you click anything

A knowledge base fails more often from poor content than from poor settings. Decide the scope first.

Pick one purpose per project

Make one project per job, such as "IT helpdesk answers" or "Sales proposal rules." A project that mixes HR policy, engineering runbooks and pricing gives Claude more material to confuse and gives you a harder sharing decision, because the audiences differ.

Choose the source files

Good candidates are policies, standard operating procedures, product FAQs, style guides and templates. Prefer one authoritative file per topic. If two documents disagree, Claude has no way to know which one you consider correct, so remove or reconcile one before uploading.

Name files so they explain themselves

Use names such as expense-policy-2026.pdf rather than final_v3.pdf. A date or version in the name helps you spot stale material later.

Step 1: Create the project

  1. Hover over the left side of your account and click Projects, or go to claude.ai/projects.
  2. Click + New Project in the upper right corner.
  3. Enter a name and description. The help center states Claude does not have access to these, so they are labels for people only.
  4. On Team or Enterprise plans, choose visibility: Keep it private or Share with your broader organization.
  5. On Enterprise plans that require tags (beta), set a value for each required tag.

If you are unsure, choose private first, test the answers yourself, then widen access.

Step 2: Add project knowledge

  1. On the project's main page, click the + button on the right side.
  2. Upload documents, text files or code snippets.

The help center page we read does not list supported file types or size limits, so check the upload dialog for what it accepts rather than assuming. On paid plans, Claude automatically enables RAG mode when project knowledge approaches the context window limit. Anthropic describes this as expanding capacity by up to 10x while keeping response quality.

What RAG mode means for you

When knowledge is small enough, Claude can work with it directly in context. When it grows, RAG mode retrieves the relevant parts for each question. In practice, a clear file structure and descriptive headings inside your documents help, because each section can then stand on its own.

Step 3: Write project instructions

  1. Click Set project instructions.
  2. Enter your instructions and click Save instructions.

The instructions apply to all chats in the project. Use them for rules that rarely change, not for facts that belong in a file. Here is a general template to adjust to your own documents:

You are the internal helpdesk assistant for our team.

Answer using only the files in this project's knowledge.
If the answer is not in the knowledge, say you could not find it
and tell the user to contact the owner of the relevant document.

Format:
- Start with a one-sentence answer.
- Then give numbered steps if the task has steps.
- Finish with "Source:" and the file name you used.

Do not guess policy numbers, dates or amounts.
Enter fullscreen mode Exit fullscreen mode

The "answer only from the files" and "name the source file" rules do two jobs: they reduce guessing, and they let a reader check the answer against the document.

Step 4: Share the project

Sharing needs a Team or Enterprise plan, unless an admin has turned it off.

  1. Open the project and click Share project, to the right of the project name.
  2. Add members by name or email, or paste a list of emails.
  3. Choose Can view or Can edit for each member.
  4. Click Share.

Pick the right role

Role What members can do
Can view See project contents, knowledge and instructions, and chat in the project, but not edit it.
Can edit Change instructions and knowledge, update member settings, and add project tags (beta, Enterprise only).

Give most people Can view. Keep Can edit for the two or three people who own the content, so that changes to instructions are deliberate.

General access

In the Share menu, the visibility setting appears under General access, with the options "Everyone at [your organization]" and "Only people invited." Public means everyone in your organization can view and use the project; private means only invited members can.

Changing and removing access

To change a role, open the sharing menu and select a new role. To remove access, click the member's current role and select Remove access. One help page says the project creator does this, and another says a member with Can edit can also remove others. Test with a spare account before relying on either, and give Can edit sparingly.

Step 5: Test before announcing

Open a new chat inside the project and ask ten real questions from your inbox or ticket history. For each answer check three things: is it correct, does it name the right source file, and does it decline when the answer is not in the knowledge?

Try at least two questions you know are not covered. If Claude invents an answer, tighten the "say you could not find it" line in the instructions and test again.

Memory inside projects

Per the help center, memory is on by default for Free, Pro, Max and Ultra plans on web, Claude Desktop and Claude Mobile; on Team and Enterprise plans, owners control it. Each project has its own memory. Claude uses project memory plus your account memory from chats outside projects, but not memory from other projects.

To keep a project's memory separate, turn off Use account memory under Memory on the project's page. To turn off memory for one chat, turn off Memory in the + menu before the first message. For a shared helpdesk project, consider whether personal memory should influence answers at all.

Keep the knowledge current

A knowledge base is a maintained product. A light routine is enough:

  1. Name an owner for each file.
  2. Review the files every quarter, and immediately when a policy changes.
  3. Replace the file instead of adding a second version next to it.
  4. Re-run your ten test questions after each change.

When a project is no longer needed, open it, click the ... button in the upper right corner and confirm to archive it. Archiving keeps members, permissions and knowledge intact, and archived projects appear at the bottom of your list. You cannot delete an archived project until you unarchive it. To delete, click ... on the project, select Delete, then click Yes, delete.

Troubleshooting

Symptom Likely cause Fix
No Share project button Free or Pro plan, or sharing disabled Use a Team or Enterprise plan; ask an owner to enable "Share projects".
"Project sharing is turned off by your administrator." Admin setting An owner must turn sharing back on; on Enterprise it can be off for specific roles.
Project is visible only to you Visibility set to Keep it private Use Share and change General access to "Everyone at [your organization]".
Answers contradict a document Two conflicting files Remove the outdated file and re-test.
Claude ignores the project files Question not covered, or instructions too loose Add the missing document; require a source file name in the answer.
Cannot create another project Free plan limit of five Archive or delete an unused project, or move to a paid plan.
Shared chat shows old messages Chat sharing is separate from project sharing Use Update next to "New messages since last shared".

Chats in projects are private by default. Sharing a project does not share each member's chats; chat sharing uses the Share button in the upper-right corner of a chat.

Checklist

  • One purpose per project, with a named content owner.
  • Only documents that every member may see.
  • Instructions that say: answer from the files, name the source, admit gaps.
  • Can view for most members, Can edit for owners only.
  • Ten real test questions, including two the files cannot answer.
  • A quarterly review date in the calendar.

What we checked

  • Opened Anthropic's "What are projects?" help article on 2026-11-17: Projects are available on all plans, free users can create a maximum of five, RAG mode is for paid plans, and sharing is Team and Enterprise only.
  • Opened "How can I create and manage projects?" on 2026-11-17 and copied the button labels: Projects, + New Project, Set project instructions, Save instructions, Share project, Share, Remove access, Delete, Yes, delete.
  • Cross-checked the role names (Can view, Can edit) between the "What are projects?" article and the project visibility and sharing article; both agree.
  • Found one inconsistency: the creation article says the project creator removes access, while the sharing article says a member with Can edit can too. The article tells you to test it rather than picking one.
  • Confirmed the admin message "Project sharing is turned off by your administrator." appears in the sharing article.
  • The instruction template is original, not vendor output, and we did not run it against a live project.
  • Not checked hands-on: no Claude account or Team plan was used, and supported file types and size limits were not on the pages we read. Steps follow Anthropic's documentation as of 2026-11-17.

Last tested: 2026-11-17

References


This guide was researched and drafted with AI assistance and checked against the vendor documentation listed in its References. Read the maintained version and related guides on EpiFive.

Top comments (0)