An employee asks an AI assistant for the company's travel policy. The answer also draws on an old personnel file stored in the same shared workspace. The assistant may have followed the system's permissions exactly. The problem is that the employee should never have had access to that file.
This is a hypothetical example, but it exposes a concrete decision for Norwegian management teams: which information should each role be able to retrieve before AI makes it easier to find? Buying an assistant does not settle who should see customer contracts, salary discussions or board papers.
The opportunity is substantial. Employees can find an approved procedure without interrupting a colleague and locate useful knowledge across projects. The aim should be to make that knowledge easier to use while correcting access that has become too broad.
Existing access can still be the wrong access
Microsoft's current documentation says Copilot can summarise or reference content the user is authorised to access. That describes how the product respects configured access. It does not establish that the company's permissions reflect employees' actual responsibilities.
A project group may still include former participants. A folder may inherit access from a larger workspace. A broadly shared link may have outlived the task it was created for. Those are possible weaknesses to investigate, not evidence that Copilot bypasses permissions.
The Norwegian concern is well established. In its November 2024 sandbox report with NTNU, Datatilsynet explained that Copilot could make previously obscure information easy to retrieve without giving the user new access. The report concerns a university and the product as it was then. It is useful evidence of the access problem, not a current product manual or a blanket legal verdict on Norwegian businesses.
Decide who needs the information
Consider a hypothetical Norwegian service company introducing AI search for employees. Its shared workspace contains a travel policy, customer project files and material from an old recruitment process. The office manager wants staff to find everyday guidance themselves. The project manager needs relevant customer documents. Recruitment assessments belong with the people responsible for that process.
Begin with those distinctions. The person responsible for each document area should identify the intended readers and explain why they need access. IT or the service provider should then check the actual groups, links and inherited permissions. A folder name such as “HR” does not demonstrate that it is restricted.
Separate common guidance from individual cases. Employees may need to read the reimbursement rules without seeing another person's expense claim or correspondence about an exception. A small AS does not need an elaborate classification programme to make that first distinction. It needs someone who can decide and someone who can implement the decision.
Removing access indiscriminately has a cost too. If a project team loses the current specification, work may stop or move into email attachments. Check that the intended users can still do their jobs. For useful knowledge that can be shared more widely, prepare an approved general version instead of opening the confidential source to everyone.
A search restriction is not a lock
Microsoft provides Restricted Content Discovery for SharePoint as a temporary way to limit content appearing in organisation-wide search and Copilot discovery. It leaves access permissions unchanged: users with access can still open the content directly. It does not cover OneDrive, and updates take time to propagate. Licensing and configuration requirements must be checked for the company's environment.
Use such a control for its stated scope while correcting the underlying access. Do not report “removed from AI search” as “no longer accessible”. Microsoft's deployment guidance distinguishes interim protection from fixing excessive access and assigning ownership.
Ask the provider to demonstrate the particular product and configuration being purchased. A custom assistant or a connector to another system needs its own assessment. A statement about Copilot's permissions does not prove that a separate integration preserves them.
Test with the employee's role, not the administrator's
For the service company, use an approved test environment and synthetic documents without real personnel or customer information. Give each test document a distinctive harmless phrase so its appearance can be traced. Configure representative access and have the relevant owners approve the expected results before testing.
Run the same tasks through an ordinary employee account, a project member account and an authorised HR account. An administrator's successful demonstration says little about the boundaries between those roles.
| Test | Expected result to verify |
|---|---|
| Find the general travel policy | Ordinary employees receive the current approved guidance |
| Ask about a synthetic personnel case | A role outside HR receives neither the case details nor a revealing extract |
| Open the personnel document's direct link | The same role is denied access at the source |
| Retrieve an assigned project document | The project member can obtain the information needed for the work |
| Remove a test user's project membership | New retrieval respects the revised access after the documented update process |
These are proposed checks, not a certified test suite. A failed search alone proves little: the assistant may simply have missed the document. Inspect the source permissions as well as the answer, source links and any extracts. Repeat representative questions in Bokmål and the other languages employees use, without treating language variation as the access control.
Record the role, document area, intended access, actual result, configuration and time of the test. Keep any evidence containing sensitive information in restricted storage. Do not spread a real disclosure by pasting it into a general support channel. If live information has reached the wrong people, follow the company's incident process and assess the consequences separately.
Include role changes and copied answers
Access changes do not automatically undo information already received. Ask what happens to an existing answer, a saved conversation or an exported document after a user leaves a project. Do not assume that revoking source access recalls every copy. Check the actual retention and sharing behaviour, and define how employees should handle derived material.
Make the review part of ordinary changes: someone joins or leaves a project, a customer engagement ends, a folder is moved or a new connector is enabled. Assign a responsible person for each important document area and agree when access will be reviewed. Otherwise, a clean pilot can gradually acquire the same old weaknesses.
Expand where both usefulness and access are demonstrated
Management should approve the initial document areas, resolve ownership and fund necessary corrections. For a small company, that may mean one well-maintained library of common procedures first. A larger business may need separate decisions for project, finance and personnel information. The guide to internal AI use in Norway addresses the wider assessment of data use and suppliers.
Where confidential information is material to the business, the board should ask which areas remain unresolved, what testing showed and whether management has resources to fix them. Directors should oversee the exposure and progress rather than administer individual groups.
At the next meeting with the IT provider, choose one useful document area and one area that must remain restricted. Ask for a demonstration of both successful retrieval and denied access, followed by the remaining gaps and a named owner. That is a more useful basis for expansion than the number of licences activated. Connect the result to the decision to move from pilot to ordinary operation.
Sources checked on 19 October 2026. This is an evergreen analysis, not a new breach report or product launch. The service company, personnel case and tests are hypothetical; the proposed method is the author's recommendation. Product controls can change. Access testing alone does not establish legal compliance. The illustration is AI-generated.