Knowledge Bases Feature Is Not Enabled: What It Means

If Claude tells you the knowledge bases feature is not enabled, it means your account cannot use that capability right now — not that you broke something. The gating is usually your plan, your workspace admin, or a feature that has not reached your account yet. Projects knowledge is the workaround that works today.

Plan gating and Projects knowledge behavior verified 31 July 2026 against Anthropic's Projects help article.

Let me be upfront about something before we go further, because it matters more than a tidy answer would. I could not find an official Anthropic help article or documentation page that describes this exact string. Everything below separates what is documented from what is reasonable inference. If a page ever promises you a precise menu path for this message, be suspicious — I could not verify one, and neither could you. This reflects real hands-on time with the feature, not just its documentation.

What a knowledge base actually means in Claude

It is durable context you attach once so Claude reads your documents in every chat. In Claude that capability ships as project knowledge, with retrieval-backed expansion of up to 10x reserved for paid plans.

Strip away the jargon and a knowledge base is simple: it is durable context you attach once so Claude can reference your documents in every conversation, instead of you re-pasting them each time.

The consumer-facing version of this already exists and is fully documented — it is called project knowledge. Inside a Project, you upload files and Claude reads from them across all chats in that Project. Anthropic's help center describes Projects as self-contained workspaces with their own chat histories and knowledge base, and notes that enhanced project knowledge using retrieval (RAG) is available only on paid plans — Pro, Max, Team and Enterprise — where it can expand capacity by up to 10x when your content approaches the context limit. That paid-plan gating is the single most useful fact here: on a free account you can still use Projects, but you do not get the expanded retrieval, which is exactly the kind of tier difference that surfaces as a feature being unavailable.

So the concept is not missing from Claude. If you want the deeper tour of how attached context behaves, our guide to Claude Projects covers the mechanics. It is worth separating this from Claude's memory, which is a different thing — memory carries small facts between chats, while a knowledge base is a body of documents you deliberately attach. Knowing that distinction matters, because plenty of people who hit the knowledge bases feature is not enabled message actually wanted memory, or wanted Projects, and were already able to use both.

Why the knowledge bases feature is not enabled for you

Four gates produce this message: your plan tier, an organization-level admin toggle, using a surface where the capability does not exist, or a staged rollout that has not reached your account. Only the admin toggle is fully documented.

Here is the honest structure of the problem. Claude surfaces a "not enabled" message when the client knows a capability exists but your account is not cleared to use it. That pattern is common across the product. What I cannot tell you with authority is which specific gate is closing on you, because the gating for this differs by plan and changes over time.

There are four plausible causes, and they are worth understanding as a set rather than guessing at one:

1. Your plan does not include it. Anthropic gates capabilities by tier constantly, and paid tiers get retrieval features that free accounts do not.
2. Your workspace admin has not turned it on. This is documented behavior for business plans: an Owner can toggle a feature on or off for an entire organization, and when a feature is off at the org level, no role can grant it back to you.
3. You are on a surface that does not have it. Project knowledge lives in the Claude web and desktop apps. A capability you saw described somewhere may not exist on mobile, in the API, or in a specific integration.
4. It has not rolled out to your account yet. Anthropic ships features gradually, and staged rollouts routinely produce exactly this class of message for accounts outside the current cohort.

Cause 2 is the most documented and the most actionable, so start there if you are on a business plan. Anthropic's guide to role-based permissions on Enterprise plans is explicit that organization-level toggles override everything below them. If you are on Claude Team or Claude Enterprise, your admin is genuinely the authority here — not support, and certainly not a blog post.

One thing I can rule out: the model is not the cause. Whether you are on Claude Opus 5, currently the newest model in the lineup, or an older one, the knowledge bases feature is not enabled message is an account and entitlement signal, not a model capability signal. Switching models will not clear it.

Cause, check, and fix — the short table

Check your plan name in Settings, ask whether other members of your workspace see the same message, retry in the desktop web app, and ask a colleague on your tier. Each check maps to one of the four gates.

Use this to work out which of the four gates is producing the knowledge bases feature is not enabled message for your account.

Notice what the table does not contain: a named admin toggle called "Knowledge Bases." I will not invent one. If your admin console has such a switch, it will be visible to your admin in their admin settings, and they can tell you in under a minute — which is faster and more reliable than anything I could guess.

What to actually do, in order

Confirm your actual plan, then ask your workspace admin if you are on Team or Enterprise, then fall back to a Project, then open a support ticket with your plan, surface, and a screenshot. Do not upgrade first.

Work through this sequence rather than jumping to an upgrade. The whole thing takes about 10 minutes.

• Confirm your plan first. Open your account settings and read the plan name. People are wrong about this surprisingly often, especially on seats provisioned by an employer. Our breakdown of the Claude AI subscription tiers helps you match what you have against what you expected.
• If you are on Team or Enterprise, ask your admin before anything else. They control feature availability at the org level. Send them the exact message text. This single step resolves the most cases, because admin-gated capabilities look identical to missing capabilities from your seat.
• Try the equivalent that already works. Create a Project, upload your documents, and use that. This is the point of the next section.
• Contact support if you believe it should be on. If your admin confirms nothing is blocked and your plan should include it, that is a legitimate support ticket. Include your plan, your surface, and a screenshot.

Set your expectations honestly at this point: none of these steps guarantee that the knowledge bases feature is not enabled message goes away. If it is a rollout gate or a capability your tier does not carry, no sequence of clicks changes that. What the steps do is tell you which wall you are hitting, which is what lets you stop wasting time.

The workaround that works today

Create a Project, upload your reference material into its knowledge, write project instructions, and start every related chat inside it. That delivers the outcome most people actually wanted, and it is documented and available now.

For most people who land here after seeing that the knowledge bases feature is not enabled, the actual goal is not a specific menu item — it is "I want Claude to know my stuff without me pasting it every time." Projects already deliver that outcome, and they are documented, stable, and available now.

The pattern is straightforward. Create a Project for a coherent body of work — for example, a client account, a codebase, or a research area. Upload the reference material into its knowledge. Write project instructions describing how Claude should use it. Then start every related chat inside that Project. Claude reads the attached documents as context on each conversation, which is functionally the "Claude knows my stuff" result you were after.

In our own daily work with Claude, we lean on Projects for exactly this and have learned the hard way that discipline beats volume: the Projects we trust most are the ones we deliberately kept small. When we let a Project balloon with every tangentially related document, Claude's answers got vaguer, not sharper, and we ended up pruning it back. A few practical notes. Keep the knowledge focused; a Project stuffed with 40 loosely related PDFs produces worse answers than one with 8 relevant ones. Watch file sizes, since attachment ceilings are real — see our notes on Claude's upload limits if a document refuses to attach. And on Team and Enterprise, Projects can be shared with colleagues, which covers most of what people want an org-wide knowledge base for anyway; the Claude for Business overview goes deeper on the collaboration side.

Being realistic about unreleased capabilities

Clients routinely ship strings and UI before the server-side entitlement exists, which is why no help article matches this message. Do not upgrade chasing an unverified tier requirement; your admin and Anthropic support are the only authoritative sources.

There is a broader lesson worth naming. Modern apps ship UI and strings ahead of availability. A message like this often means a feature exists in the client build but is gated server-side — which is precisely why the knowledge bases feature is not enabled message can appear without any corresponding help article. The string ships before the documentation does.

That has two consequences for you. First, do not upgrade a plan chasing a capability whose tier requirements you cannot verify on the official pricing or help pages. Second, treat your admin and Anthropic support as the only authoritative sources for your specific account. Anyone confidently describing the exact toggle path is likely reconstructing it from a screenshot they cannot verify either.