Jasper AI Knowledge Base: How to Set It Up and Use It
How-to — — by Mahmoud Zalt
Add brand facts to Jasper's Knowledge Base, connect Google Drive or SharePoint, and understand the five-item cap and the URL caching rule.
Brand Voice controls how Jasper sounds. The Knowledge Base controls what it is allowed to say. If your drafts read beautifully and describe a product you do not sell, this is the setting you have not filled in.
Jasper describes it as the container in your workspace that holds the facts of your business, covering products, pricing, company values, market positioning, target audiences and brand identity. The mechanism is worth understanding, because it explains most of the gotchas further down.
According to Jasper's documentation, it chunks the data you upload, finds the relevant pieces at generation time, and uses those chunks as content for the output. It is not reading your whole document every time, which is exactly why what you upload and how you name it matters.
How do you add something to the Jasper Knowledge Base?
You add one asset at a time through the Jasper IQ section of the sidebar. The whole flow is six clicks and takes under a minute per item once you have the file ready.
Creating a Knowledge Base entry
- Open the Knowledge Base — Go to the Jasper IQ section on the left side of your home page and choose Knowledge Base.
- Start a new asset — Click + Add knowledge.
- Upload the content — Jasper accepts text, audio, image, video, documents and URLs. Their documentation lists formats including .mp4, .mov, .mp3 and .jpeg, and says hovering over the asset type in the uploader shows the full supported list.
- Name it — Give the Knowledge Asset a name. Treat this as a retrieval label, not a filename, because it is how you and your team will find it later.
- Tag it — Tags are optional. Jasper supports custom tags so you can organise assets around your own workflow rather than a fixed taxonomy.
- Set visibility — Choose private to you or public to your workspace.
- Save it — Click Add to Knowledge Base. Jasper notes that video files can take longer to process, up to around ten minutes depending on file size, so upload those before you need them.
Where does the knowledge actually get used?
Nowhere automatically. An uploaded asset sits in the library until you attach it, and Jasper's documentation names three places you do that.
- In Chat, by clicking the ... button.
- In an agent, through that agent's settings. Jasper notes this applies to that asset only.
- In a project, through Project settings, which applies to every asset in the project. This is the one to use if you are producing more than a single piece.
One exception is worth knowing. Jasper's documentation for Jasper Studio, the no-code builder for custom agents, says you can attach up to ten Knowledge Base items as permanent context that users can view but not edit or remove. If a fixed reference set matters for a repeated job, a Studio agent is where it goes.
Can you connect Google Drive or SharePoint?
Yes, and this is the better route if your source material already lives in a shared folder. Jasper's own write-up on Knowledge Base connectors names two: Google Drive, covering personal drives, shared folders and shared drives, and Microsoft SharePoint.
The documented flow is to open Knowledge Base settings, click Add to Knowledge Base and pick the connector, authenticate with your Google or Microsoft account, choose the folders you want, and confirm to start the first sync. Jasper says new files, edits, renames and deletions then flow through automatically.
On permissions, Jasper states it requests read access to the selected folders so it can pull in and monitor documents, that your files stay in your drive, and that it indexes rather than moves or modifies them. Worth reading in their own words before you connect a folder containing anything sensitive.
The URL rule almost nobody knows
This is the single most useful thing in Jasper's Knowledge Base documentation, and it is buried near the bottom of the page.
The practical consequence is a real one. If you launched a price change this morning and your pricing page is a URL asset, do not assume today's generation knows about it. Paste the new copy in as a text asset for anything time-sensitive.
There is a related editing limitation. Jasper says the creator of an asset can click the ... to its right and select Edit, that text uploads can be edited, that documents can be downloaded but not edited, and that URL uploads can be neither downloaded nor edited. Text assets are therefore the flexible choice for anything you expect to revise.
What should you actually put in there?
Jasper's own suggestions are pillars and values, white papers, your marketing site, content briefs and product information. Their Jasper IQ guidance recommends starting with five items and prioritising your most-referenced brand materials, such as product overviews, messaging guides and FAQs.
That is sound advice, with one addition from experience. The highest-value document is usually the one that does not exist yet: a single page of the claims you are allowed to make, the numbers you are allowed to quote, and the words you never use. Writing that page takes an afternoon and improves output in every tool you own.
| Detail | What the documentation says |
|---|---|
| Where it lives | Knowledge Base, inside the Jasper IQ section of the left sidebar |
| Content types | Text, audio, image, video, documents and URLs |
| Attach limit per generation | Up to 5 knowledge or source materials in Agents and Chat |
| Custom agent context | Up to 10 Knowledge Base items attached in Jasper Studio |
| Connectors | Google Drive and Microsoft SharePoint |
| URL freshness | No scheduled refresh, page may be cached up to two days old |
| Editing | Text editable, documents downloadable only, URLs neither |
| Plan limits | Pro lists 5 Knowledge Assets, Business lists unlimited |
One inconsistency to flag honestly: Jasper's Knowledge Base page lists those per-plan asset counts, while its Jasper IQ overview page states that Jasper IQ is available on Business plans. We could not resolve which governs a given account, so confirm with Jasper before you build a workflow on it.
Uploading facts versus having a colleague who knows them
The Knowledge Base is a genuinely good idea and Jasper implements it thoughtfully, particularly the connector sync and the honesty about URL caching. If you are using Jasper, fill it in properly.
The part that stays manual is the choosing. Every generation, someone picks which five documents are relevant, and that someone is you. When we built Sistava, we moved that decision to the other side. You hire an AI Employee, tell it what you want handled, and it works out which of its knowledge applies, asks you when it is unsure, and then does the task rather than returning a draft.
Either way, the preparation transfers. A clean set of source documents makes any tool better, and the work of writing down what your company actually claims is worth doing regardless of where you paste it afterwards.
If you only change one habit after reading this, make it naming your assets for retrieval rather than for storage. Under pressure you will pick the five that look right, and the names are the only thing guiding that choice.
Frequently asked questions
FAQ
How many Knowledge Base items can Jasper use in one generation?
Jasper's documentation states you can include up to 5 pieces of knowledge or source materials to guide content and accuracy in Agents and Chat. Jasper Studio agents are documented separately as supporting up to ten attached items as fixed context.
What file types does the Jasper Knowledge Base accept?
It accepts text, audio, image, video, documents and URLs. Jasper names .mp4, .mov, .mp3 and .jpeg among the accepted types and says hovering over the asset type in the uploader shows the full list of supported formats.
Does Jasper keep URL knowledge assets up to date?
Not on a schedule. Jasper's documentation says it accesses a URL item at the moment it is used in a generation, and that the returned page can be a cached version up to two days old. For anything time-sensitive, paste the content in as a text asset instead.
Can you connect Jasper to Google Drive or SharePoint?
Yes. Jasper's write-up on Knowledge Base connectors names Google Drive, including personal drives, shared folders and shared drives, and Microsoft SharePoint. You authenticate, pick folders, and confirm to start the first sync, after which new files, edits, renames and deletions flow through.
Can you edit a Knowledge Asset after uploading it?
Partly. Jasper says the creator can open the ... menu to the right of an asset and select Edit. Text uploads can be edited, documents can be downloaded but not edited, and URL uploads can be neither downloaded nor edited.
Who can see and change Knowledge Base assets in a workspace?
You choose whether each asset is private to you or public to the workspace when you create it. Jasper states that all users can create, update and delete the Knowledge Assets they created, unless the workspace permission settings say otherwise.
How many Knowledge Assets do you get per plan?
Jasper's Knowledge Base page lists 5 Knowledge Assets on Pro and unlimited on Business. Their Jasper IQ overview page separately states that Jasper IQ is available on Business plans, so confirm what applies to your account.
Sources
- Jasper Help Center, Knowledge Base, the creation steps, attach limits, editing rules and URL caching behaviour
- Jasper Help Center, Jasper IQ, the recommended five-item starting point and stated plan availability
- Jasper Help Center, Jasper Studio, the ten-item context attachment for custom agents
- Jasper blog, how to use Knowledge Base connectors, the Google Drive and SharePoint setup flow and permissions
- Jasper, Knowledge Base product page, the vendor description of syncing and agent access
Fill in five items, name them so the right ones are obvious under pressure, and remember that URL assets can lag by up to two days. That handful of habits removes most of the invented facts people blame on the model.