# How to control who reads company procedures: folder access by role and team

https://krokul.com/en/blog/wiki-folder-access-by-role/ · Krokul Team · Updated 2026-11-18

Payroll, price lists and manager checklists should not sit in the same place as the warehouse rules everyone needs. This guide shows how to give each folder of company procedures its own readers, editors and managers, and how to check the result.

**Short answer.** Knowledge base access control by folder works in three levels: read, edit and manage. List folders by who may open them, grant each folder to people, teams, roles or the rest of the staff, and give a closed folder its own list, which replaces the inherited one. Then view the folder as a colleague before you tell the team.

## When a knowledge base needs folder access rules

A company of 10 to 40 people starts with one shared place for procedures and soon writes things that are not for everyone. The guide on [connecting AI agents and other tools to a CRM safely](https://krokul.com/en/blog/topics/crm-ai-agents-integrations/) treats access as a property of every channel, and a team knowledge base inside the CRM needs the same discipline. The guide on [safe AI access to CRM data](https://krokul.com/en/blog/ai-assistant-safe-crm-access/) applies the same thinking to keys and assistants. Typical signs that rules are due:

- The pay scale, the bonus rules or the notes on a dismissal sit in a document that anyone with a link can open.
- Discount limits and margin thresholds are written for managers, and a new support agent has just read them.
- The warehouse team edits its own procedures, and nobody else should rewrite them by accident.
- A contractor joins a project and needs the onboarding folder only.

## How to set folder access in five steps

Folder access works when you decide the groups first and the clicks second. Five steps keep the setup small: sort the folders, pick the subject type for each rule, set the rule on the highest folder where it changes, name a manager and view the result as the employee.

### 1. Sort the folders by who may open them

Write the folder tree on one page and put one of three marks next to each folder: everyone reads, a group reads, a few people read. Most folders end up with the first mark, and that is a good sign.

Keep the tree shallow. Four levels of folders are the limit in Krokul, and a rule is easier to reason about when a closed folder holds the whole subject.

### 2. Pick the subject type for each rule

A person suits an exception, such as the finance director who reads the payroll folder. For a department pick a team, and remember that a team with sub-teams passes its access to their members. Every manager at once is a job for a role. The rest of the staff row covers the default.

Prefer teams and roles to long lists of names, because a new colleague then gets the right access on the day of joining.

### 3. Set the rule on the highest folder where it changes

A folder with its own list uses that list and ignores everything above it. The list replaces the inherited one and adds nothing to it, so a closed folder must name every group that still needs to read it, including the managers.

Set the rule once on the parent, and the subfolders and the pages inside follow it until a subfolder gets a list of its own.

### 4. Name who manages each closed folder

Manage is the level that changes access, moves and deletes the folder. Give it to the head of the subject, and the author of the last page needs only Edit. When one person has two rows, for example as a team member and as a role, the higher level applies.

Keep at least one named manager on every closed folder, so that a change of access does not wait for an administrator.

### 5. View the folder as the employee before you announce it

Pick two or three colleagues who differ in role and team and look at the folder through their eyes. The check shows which folders and pages each of them sees and at which level.

Repeat the check after every change of teams or roles, because access follows them.

## What read, edit and manage allow

A level answers one question, what a person may do with the folder and the pages in it. The three levels grow from one to the next, so a person with Manage can also edit and read.

- **Read** — The person opens the folder and its pages and cannot change them.
- **Edit** — The person writes and changes pages in the folder and creates new ones.
- **Manage** — The person does all of the above and also sets who has access to the folder, moves it and deletes it.
- **Own access** — A list of people, teams and roles set on one folder; it replaces the list inherited from the parent.

## Example: which folder goes to whom

The table is an example for a company with a warehouse, a sales team and a finance director. The default row describes a new knowledge base, where the rest of the staff reads everything. Adjust the names to your teams. The guide on roles that keep cost and margin private uses the same logic for numbers in the CRM.

Example: folder, who gets access and at which level:

| Folder | Who | Level |
|---|---|---|
| Company rules (the root) | The rest of the staff | Read |
| Warehouse procedures | Warehouse team | Edit |
| Warehouse procedures | Head of the warehouse | Manage |
| Warehouse procedures | The rest of the staff | Read |
| Discounts and price rules | Sales team | Read |
| Discounts and price rules | Head of sales | Manage |
| Payroll and bonuses | Finance director | Manage |
| Payroll and bonuses | HR specialist | Edit |

Look at the last two rows. Nobody outside the two named people and the administrators sees the payroll folder at all, because its list does not contain the rest of the staff. The discount folder is open to the sales team and closed to everyone else for the same reason.

## Which access mistakes to avoid

- Setting a list on a subfolder and expecting the parent list to still work. The own list replaces the parent one, so name every group again.
- Granting access to a long list of names. People change roles, and a rule on a team or a role stays correct without a visit to the folder.
- Giving Manage to many people. Each of them can change who reads the folder, so keep it to the head of the subject.
- Putting a sensitive page in a shared folder and hoping that the title is enough. Access sits on folders, and a page takes the access of its folder, so move the page to a closed folder.
- Announcing a new rule without viewing the folder as a colleague. One check shows a team that lost access by accident.

## Access audit checklist for the knowledge base

Run this list once a quarter and after every reorganisation. It takes a few minutes and finds the rules that drifted. A separate guide shows how to [read the audit log of a CRM](https://krokul.com/en/blog/crm-audit-log/) when the question is who changed a deal or a setting.

- Every closed folder has a named manager, and no more than two or three.
- Every closed folder lists teams and roles, and names appear only for exceptions.
- The payroll, price and personnel folders are viewed as an ordinary employee and as a new colleague, and both see nothing there.
- The rest of the staff has no access to a folder that must stay closed.
- People who left the company or changed teams are removed from the teams that give access.
- Folders with the same subject are in one place, so one rule covers them.

## How Krokul sets access on knowledge base folders

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. Its knowledge base lives under Knowledge base in the menu, and access is set on folders. In the folder menu an administrator or anyone with Manage picks Access, and the dialog lists who reads, edits and manages the folder. A folder that has a list of its own carries a lock icon in the tree.

The rules in the dialog are the ones from the method above. You add a person, a team or a role from one list, and set Reads, Edits or Manages for each. Teams may have sub-teams, and access given to a team reaches the members of its sub-teams. The role list offers manager, agent and viewer, and a viewer never rises above Reads even when the folder says Edits. The row for the rest of the staff can be set to No access, and then the folder is closed to everyone not named. A new knowledge base starts with the rest of the staff reading everything, and only administrators change that root rule.

The closest folder with its own list decides, and its list replaces the inherited one. If a person has several rows, for instance through a team and through a role, the highest level applies. Administrators see and manage everything. A folder cannot be left without someone to manage it: an administrator always can, and anyone else who saves a list without Manage for themselves gets a refusal, and returning to the inherited access asks for confirmation when it would cost the person their own Manage.

A person without access does not see the folder in the tree or in the search, and opening it by a direct address gives the same answer as for a folder that does not exist. The server computes the level in every request of the knowledge base, so the screen and the answer agree, and API keys have no access to the knowledge base. The View as an employee mode in the same dialog lists the folders and pages that a chosen colleague sees and the level of each. It is open to those who manage the folder, and for the whole knowledge base to administrators. Personal drafts are visible to their author only.

![Hours report of a demo company with cost, revenue and margin per client and cost per person](https://krokul.com/img/en/blog/wiki-folder-access-by-role-hours-report.webp)

The page on [how Krokul checks permissions on the server](https://krokul.com/en/solutions/security/) describes the wider model, where the server checks permissions on every request.

## Frequently asked questions

### Can I hide one folder from the whole team except two people?

Yes. Give the folder its own list with those two people, set the rest of the staff to No access, and the folder disappears for everyone else, including in search.

### Does a subfolder inherit the access of its parent folder?

Yes, until the subfolder gets a list of its own. Then the own list replaces the inherited one, so name every group that should still read it.

### What happens when a person is in a team and also has a role with another level?

The higher level wins. If the team grants Read and the role grants Edit, the person edits.

### Can an administrator be locked out of a folder?

No. Administrators see and manage every folder, and that is why a closed folder cannot end up without a manager.

### How do I check what a colleague sees before I change access?

Use the View as an employee mode in the access dialog of the folder. It lists the folders and pages that colleague sees and the level of each.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
