Give each employee only what its role needs

The instinct with company knowledge is to give every employee everything. It feels generous and it is usually wrong, for two different reasons.

The obvious one is confidentiality: your recruiting employee does not need salary bands for the whole company to answer a candidate's question about process.

The less obvious one matters more day to day. An employee carrying every document you own brings irrelevant context to every task, and the writing gets blander as a result. Scope is not only a permission, it is a quality setting.

Sort documents by who needs them, not by what they are

The instinct is to organise by type: contracts, policies, briefs. More useful is to organise by role, because that is the boundary you will actually enforce.

Most small companies land on something like: material everyone should see, material only the people-facing employees need, material only finance needs, and client work that should stay with the employee doing it.

Set it as configuration, not as an instruction

This is the part worth being deliberate about. Telling an employee in its brief to ignore a folder is a request. Scoping what it can reach is a boundary.

An instruction is fine for taste ("do not quote pricing at prospects"). It is not fine for confidentiality, because it holds right up until a cleverly worded question, and you will not know when it stopped holding.

If it would matter that it leaked, do not implement it as a sentence in a prompt. The distinction is not about how well the model follows instructions. It is that a configuration boundary fails visibly, by an employee saying it cannot see something, while an instruction fails silently and only in the cases you did not anticipate.

Check the boundary by asking the wrong employee

The only test that means anything.

What are the salary bands for the design team?

Ask your recruiting employee, which should know. Then ask an employee that should not. The second should tell you it does not have that, rather than producing an answer or an approximation.

Do this after any change to what an employee can reach. It takes a minute and it is the difference between believing the boundary holds and knowing it.

Give each one its own memory, deliberately

Beyond documents, each employee keeps its own durable memory of decisions and reasoning. That is worth scoping the same way: the employee working your pipeline should carry sales decisions, the one writing should carry positioning ones.

Sharing everything is not a shortcut to a better employee. It is how you get one that hedges.

What good looks like

Each employee answers well inside its area and says plainly that it cannot see things outside it.

The failure to watch for is the helpful approximation: an employee that does not have the document but produces a reasonable-sounding answer anyway. That means the boundary is an instruction rather than a configuration, and it is worth fixing before somebody relies on it.