Skip to content

AR Digital / Daily AI

Claude project or simple conversation: when to create a project and how to share it with your team

Claude project or simple conversation: when to create a project, what it keeps in memory and how to share it with your team without exposing your files.

Radu UleaFounder of AR Digital

7 min read

  • Written with AI
  • 3 sources cited

Many teams open a new conversation for every request and paste the same documents again every day. A Claude project solves this problem, provided you know what it keeps, what it shares and what it does not share.

Daily AI. Today, a tip for teams that use Claude. If you paste the same documents and the same instructions every day, create a project. A project keeps a knowledge base and instructions that serve all of its conversations. It is open to all accounts, with at most five projects on the free plan. On Team and Enterprise plans, you can share it as read-only or editable, and your conversations stay private. Two habits before you start. For a sensitive file, keep the project’s memory separate from your account’s. And to cut off a former colleague’s access, archiving the project is not enough: you have to remove them from sharing. The detail is just below.

In short: keep the simple conversation for a one-off question. Create a project as soon as a subject keeps coming back with the same documents and the same instructions: client file, recurring offer, internal procedure. On Team and Enterprise plans, share the project as read-only or editable, with your conversations staying private.

The problem at the office

Take the office manager at an accounting firm. Every morning, she opens Claude, pastes the reminder letter template, restates the house tone, attaches the price list, then asks her question. The next day, she starts again. Her colleague does the same on his side, with an older version of the price list.

This is not a tool problem, it is a filing problem. An isolated conversation knows nothing of what was said elsewhere, except what the account’s memory may have kept if it is turned on. For work that keeps coming back, Claude offers another container: the project. Anthropic describes it as a self-contained workspace, with its own conversation history and its own knowledge base, where you drop documents and instructions that serve all the conversations in the project.

Projects are open to all accounts, including free ones, with a limit of five projects on the free plan, according to Anthropic’s help page on projects, consulted on 18 November 2026.

The options at a glance

Option What it is for Plan required Limit to know about
Simple conversation A one-off question, a quick draft All No documents or instructions shared with your other conversations
Private project A recurring subject: client file, procedure, standard offer All (five projects at most on the free plan) The project’s conversations do not share their content, apart from what the project’s memory keeps: whatever must serve everywhere goes into the knowledge base
Shared project Knowledge common to the team: templates, house rules, documentation Team or Enterprise Owners can turn sharing off: individual access already granted stays, but projects open to the whole organisation become private again; your conversations stay private
Project with many documents A large document base Paid plans RAG mode extends capacity by up to ten times when the base nears the context limit

Sources: Anthropic help pages on projects, creating and managing projects, and visibility and sharing, consulted on 18 November 2026.

Which one for which task

Stay in a simple conversation when the request fits in one exchange: rephrasing an email, summarising an article, finding an Excel formula. Creating a project for that adds filing without bringing anything.

Create a project as soon as three signs appear: you paste the same documents, you repeat the same instructions, and the subject will last several weeks. In the project, two areas matter. The knowledge base receives the reference documents: templates, prices, procedures. The project instructions set the expected behaviour for all conversations, for example a formal tone or the viewpoint of a specific profession. The context sheet we recommended in October fits naturally in these instructions.

One detail changes the way you work: according to the help page on managing projects, context is not shared from one conversation to another in a project, unless it is added to the knowledge base. A decision made on Tuesday in one conversation is therefore not necessarily known on Wednesday in another: the project’s memory may keep a trace of it, but with no guarantee. If it needs to be used, add that decision to the base.

Share the project on Team and Enterprise plans when the whole team needs to start from the same documents. Two levels exist. With read access, the member sees the content, the base and the instructions, and can chat in the project without changing it. With edit access, they can change the instructions and the base, and manage members. The creator can also make the project visible to the whole organisation, if the organisation’s owners (Owner or Primary Owner) have not turned off public projects. A reassuring point, stated by the help page on project visibility: even in a public project, your conversations stay private as long as you do not share them.

Finally, be aware that Anthropic is rolling out a new version of projects in stages, in beta, first in Claude Code for some Pro, Max and Ultra subscribers; other subscribers on these plans already see their existing projects migrated, with no loss of content. Chat, Cowork and the Team and Enterprise plans will follow later, according to the help page on projects. The menus you see may therefore change over the coming months.

The trap to avoid

The trap cannot be seen: it is memory. Each project has its own memory. In a project, Claude draws on that project’s memory and on the memory of your conversations outside projects, never on that of other projects. But the help page also states that new memories saved in a project can be carried into your conversations outside projects if your memory is turned on.

For a sensitive file, a dispute or a recruitment for example, turn off the “Use account memory” option in the Memory section of the project page: its memory then stays completely separate. On Team and Enterprise plans, it is the organisation’s owners (Owners) who decide whether memory is available.

Second habit: archiving a project removes access for no one. Members, their rights and the knowledge base are kept. To cut off a former colleague’s access, the creator or a member with edit access removes that person in the sharing settings; if the project is open to the whole organisation, you also need to limit access to invited people only. And before dropping a client document into a project, check that you are working from a work account and not a personal one.

Our take

The project is one of the most useful and least used features of Claude in the SMEs we train. A team that organises its work into three or four well-named projects gains above all in consistency: everyone starts from the same templates. The real work is deciding who edits the base, and saying so.

Going further with your team

A trained team does three things differently. It names one person in charge of each shared project, the only one, with the project’s creator, to have edit rights. It dates each document dropped in and removes outdated versions, so that Claude never answers with the old price list. And it separates sensitive projects from the account’s memory from the moment they are created.

If you also connect your tools, reread the Claude connector settings before opening a project to the whole organisation. This is the type of organisation we put in place in workshops, on your own files.

Frequently asked questions

Can I have a Claude project on the free plan?

Yes. Projects are open to all accounts, including free ones, with a limit of five projects on the free plan. Sharing with colleagues is reserved for Team and Enterprise plans.

Do my colleagues see my conversations in a shared project?

No. Sharing gives access to the project’s content, its knowledge base and its instructions. Your conversations stay private unless you choose to share them.

Does Claude remember the content of other conversations in the same project?

Not reliably. Context is not shared between the conversations of a project, unless it is added to the knowledge base. The project does, however, have its own memory, which can be turned on or kept separate from the account’s.

Is archiving a project enough to remove a former colleague’s access?

No. Archiving keeps the members, their rights and the knowledge base. You need to remove the person in the project’s sharing settings and, if the project is open to the whole organisation, switch it back to invitation-only access.

ShareLinkedInBy email

Radu UleaFounder of AR Digital

Founder of AR Digital, a web and digital marketing agency in Luxembourg. He helps SME owners with their website, visibility, advertising and move to artificial intelligence, and writes the Daily AI edition every working day. LinkedIn

Every working dayAR Digital / Daily AI

Get Daily AI every working day.

One piece of AI news, what it changes for your business and what to do, in your inbox in the morning. Free, no commitment.

Free, one email per working day, unsubscribe in one click. The email edition is currently sent in French. An email asks you to confirm your address.

AR Digital / Contact

Let’s talk about your project.

Thirty minutes, by video call or at the agency, to understand what you need and tell you frankly what we would do, at what price and with what funding. No commitment.

Radu Ulea, founder of AR Digital

Radu Ulea

Founder, AR Digital

“We tell you what works, what doesn’t, and what it costs. Then we do it.”

hello@ardigital.eu