Someone teaching another person how to do something on their computer

Before AI Searches Your Files, Check Who Can Open Them

Before an AI assistant helps staff search company information, there is a more useful question than which licence to buy: who can already open the files it might find?

For Australian business owners and IT managers considering Microsoft 365 Copilot, a permissions review connects the AI rollout to an existing business responsibility. The aim is to make useful information available to the right people, while correcting access that no longer has a business reason.

Access and discoverability are different

Microsoft explains that Copilot can only reference content the user is authorised to access. That does not establish whether those permissions are appropriate. A file shared too widely can remain a problem even when a tool follows its access rules correctly.

Consider a hypothetical pricing workbook stored in a project site that all employees can access. The commercial team may assume that only account managers know where it is. Easier discovery could expose that mistaken assumption. The issue to resolve is the permitted audience, rather than relying on a document being difficult to find.

Start with one business use case

Choose a specific job, such as helping a service team find approved product guidance. Identify the people doing that job, the information they need and the person responsible for deciding what they should see.

Keep two lists: information required for the job, and information that must remain outside its scope. For the service team, current product instructions might belong on the first list. Draft commercial terms and personnel records would normally require a different audience and a separate reason for access.

A narrow use case makes the first review manageable. It does not make the rest of the environment safe by default. Ask IT to establish what the selected product can reach under each pilot user's identity, including content outside the team's preferred library.

Ask the information owner to approve the audience

IT can inspect a permission entry. It cannot always determine whether a former project participant still needs the underlying information. Pair a technical reviewer with a business owner who understands the documents.

For each relevant site or library, record:

  • Purpose: what work the content supports.
  • Owner: who approves access and keeps the content current.
  • Audience: which teams, individuals and external collaborators need access.
  • Exceptions: separately shared folders or files that need closer inspection.
  • Action: what will change, who will change it and when it will be checked.

Review group membership and sharing links alongside the site audience. A reassuring group name is not evidence that its members are correct. If ownership is unclear, resolve it before treating the content as approved for wider use.

Fix access without breaking legitimate work

Prioritise the areas where inappropriate access would cause the greatest harm. Agree changes with their owners, document the current arrangement and test the replacement with people who still need to do the work. Removing broad access without checking dependencies can interrupt collaboration and encourage staff to create unmanaged copies.

Temporary discovery controls can help while a review proceeds. Microsoft's Restricted Content Discovery guidance describes limiting selected SharePoint sites in organisation-wide search and Copilot discovery. It does not change permissions or prevent an already authorised user from opening content directly. It also does not cover every search experience or OneDrive site.

Treat that distinction as a decision point. If someone should not be able to open a file, address access itself. If a site needs review before wider discovery, assess whether a temporary restriction fits. Check licensing, prerequisites and propagation time with your administrator. Excessive restrictions can also make useful search results incomplete.

Test the boundary, then record the decision

Use approved test accounts and harmless sample documents to check the intended audience. Include someone who should have access and someone who should not. Test direct access as well as the search or assistant experience, and allow relevant changes to take effect before assessing the result.

A document missing from one AI answer does not prove that access is blocked. Check the underlying permissions and direct access result. Equally, confirm that authorised people can still find the information needed for their work.

Record the scope tested, the expected result, the evidence and any remaining gaps. Decide whether to proceed within the reviewed scope, narrow the rollout or defer it while access issues are resolved. Set another review when roles, collaborators or source libraries change.

Connect AI readiness with everyday IT management

Zarbtech's approach is to connect the proposed AI task with its information owners and support arrangements. Our Managed AI services include workflow assessment, appropriate permissions and scoped testing. Our Cloud Services support the implementation and maintenance of Microsoft cloud environments.

If you are planning AI search across business documents, bring one use case and its source libraries to a conversation with Zarbtech about your AI readiness. Agreeing who should see what is a practical first step towards a useful, controlled rollout.

Other articles

Thumbnail for Zarbtech at EDUtech Asia 2026: AI, Education and Regional Connections

13 Nov 26

Zarbtech at EDUtech Asia 2026: AI, Education and Regional Connections

Our team and customers visited EDUtech Asia 2026 to explore AI developments, meet new people and consider the…

Thumbnail for Before You Install an AI Tool, Check Where It Came From

09 Nov 26

Before You Install an AI Tool, Check Where It Came From

A recent malicious AI-branded extension shows why product names are only the start. Check installation sources, permissions and…