Short answer
A sales team knowledge base inside the CRM keeps policies, scripts and instructions next to the deals they apply to. List the policies the team needs, build a folder tree no deeper than four levels, set access for each folder, write in drafts before publishing, and keep it tidy with search and the trash.
- Folder depth: up to four levels
- Access levels: read, edit, manage
- Removed items: stay in the trash for restore
On this page
When does a sales team need a knowledge base inside the CRM#
A small B2B sales team needs a knowledge base inside the CRM as soon as the rules of the work are more numerous than the head of sales can repeat aloud. This guide belongs to the topic on building a B2B sales pipeline that predicts revenue and covers the part that keeps the rules in reach of every rep.
- The discount policy sits in a document service, the call script in a chat note and the stage rules in a spreadsheet, so a new rep asks the head the same questions every week.
- A rep checks the policy in one tab and the deal in another, and often works from memory.
- The head edits a policy and nobody knows which copy is current.
- Some documents, such as the bonus rules of the heads, must stay closed to the rest of the team.
How to build a sales team knowledge base in five steps#
A sales knowledge base takes shape in five steps: decide which policies the team needs, build the folder tree, set access, write in drafts and keep it tidy. Each step has one rule, and the order matters, because access is easier to set on a tree that already exists.
Decide which policies the sales team needs
Walk through one deal from the first call to the handover and write down every question a rep asks the head on the way. Each question that repeats becomes one article: how to qualify an inquiry, which discount needs approval, what a quote must contain, what the next team receives after a win.
Start with six to eight articles. The rules that gate a deal at each stage, such as the ones in the template for stage exit criteria, come first, because the team opens them most often.
Build the folder tree around what the rep is doing
Name folders after the moment of the deal, for example Before the call, During the deal and After the win. A rep who needs the discount policy thinks of the moment, and rarely of the author of the policy.
Keep the tree shallow. Folders go up to four levels, and two or three cover a small team. Put the articles you open most often at the top of a folder, since the order is yours to arrange.
Set access for each folder
Decide who reads, who edits and who manages each folder. Start with everyone reading the sales folders, the head and one deputy editing them, and a closed folder for documents meant for the heads only.
A person with the manage level also gives access to others, so give it to the head of sales and to nobody else. Reps rarely need more than reading, and the guide on CRM roles that keep cost private shows how to split the rest of the team.
Write in drafts and publish by moving the article
Write a new article in your own drafts, where only you see it, and move it to its folder when it is ready. A reader never meets a half-written policy, and the head never edits it in public.
Review the policies on a schedule. When the rules change, set a task for the owner of the article, as in the guide to tasks and calendar for sales reps, so that the change does not wait for someone to remember.
Search, edit and remove with the trash as a safety net
Teach the team to search before they ask. A rep types a word from the policy into the search field and reads the article, so questions to the head shrink to the cases the policy does not cover.
Remove outdated articles without fear: a removed folder goes to the trash with everything inside it and comes back whole. Run the weekly review from the same place, as described in the guide on getting sales reps to use the CRM.
Which sales policy goes into which folder and who reads it#
A table of policies, folders and access settles most arguments before they start. The rows below are an example for a team of six reps, a head of sales and a deputy. Change them to match your own structure. Rules for a deal that the rep checks while working the card, as in the guide on the deal card and the kanban board, belong in the folder named after the stage.
| Policy | Folder | Who reads | Who edits |
|---|---|---|---|
| Qualification questions and call script | Before the call | All reps | Head of sales, deputy |
| Stage rules and required fields | During the deal | All reps | Head of sales |
| Discount and quote approval policy | During the deal / Pricing | Reps with the manager role | Head of sales |
| Handover to the delivery team | After the win | All reps | Head of sales, deputy |
| Onboarding plan for a new rep | Team | All reps | Deputy |
| Bonus rules of the heads | Heads only (closed folder) | Head of sales, deputy | Head of sales |
The setup has three folders at the first level and one extra level for pricing, which is well inside the limit of four. Only the closed folder has its own access list. The other folders take their access from the nearest folder above them.
Which mistakes to avoid when you build a sales knowledge base#
- Copying every document from the old service on the first day buries the useful pages, so move the six to eight policies the team asks about and add the rest on request.
- Naming folders after people or departments sends the rep looking for an author, so name them after the moment of the deal.
- Giving everyone the right to edit turns the policy into a collection of private versions, so keep the edit level for the head and a deputy.
- Closing a folder and forgetting the people who need it leaves the head locked out of a document, so check the folder through the eyes of each role after you set it.
- Leaving an outdated article in place makes the team distrust the whole base, so remove it and rely on the trash if someone needs it back.
How the knowledge base works in Krokul#
Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. The Knowledge base item sits in the Team section of the menu next to Files, and it works on every plan, including the free one. The tree holds folders up to four levels deep, and the articles inside are text with headings, lists, checklists, tables and links. Pictures and attached files are not part of an article.
Access is set on folders, at three levels: reads, edits and manages. A row names a person, a team, a role (manager, agent or viewer) or the rest of the staff. The access of a folder replaces the access of the folder above it, and when several rows apply to one person the highest level wins. A new company starts with everyone reading and administrators managing everything, and a person with the viewer role never goes above reading. Someone without access to a closed folder does not see it in the tree or in search.
A person who manages a folder opens its access window and can switch it to a view through the eyes of a colleague, which shows what that person gets. The window also offers a return to the access of the folder above. Articles that you write in your drafts stay private until you move them into a folder where you have the edit level. Dragging in the tree sets the order, and a move of a folder needs the manage level.

An article saves itself a second after you stop typing. When a colleague is typing in the same article right now, the page shows the name of the editor. This is a notice, and the article stays open for the second person. If two people save from the same version, the later save is declined with the name of the author and a button to refresh, and nothing is overwritten silently. After the refresh, the unsaved edits of the person whose save was declined are discarded. The top search field finds articles by title and text together with clients and deals (search across Krokul records) and returns only what the person may read.
A removed article or folder moves to the trash of the knowledge base, which an administrator sees in full and everyone else sees only for what they removed. Before a folder is removed, Krokul says how many articles go with it. A restored folder returns with its articles and its access, and goes to the top level when the folder above it is gone. The rules for required fields on pipeline stages live in the pipeline settings, and the knowledge base keeps the explanations that go with them.
Frequently asked questions#
How many folder levels can a sales knowledge base have?
Krokul allows up to four levels of folders, with articles at any of them. A small sales team usually needs two or three levels.
Can I keep a folder closed to part of the team?
Yes, by giving the folder its own access list. People who are not on the list do not see the folder in the tree or in search, and a viewer never goes above reading.
What happens when two people edit one article?
The second person sees who is editing, and a conflicting save is declined with the author and a refresh button. Krokul does not overwrite a colleague’s change silently.
Can I get back an article I removed by mistake?
Yes, from the trash of the knowledge base. A restored folder comes back with its articles and its access.
Which plan includes the knowledge base?
Every plan, including the free one. Krokul does not tie the Knowledge base item to a tariff.