How to check sharepoint permissions before turning on microsoft copilot

Summary

This guide helps you troubleshoot and resolve: How to check sharepoint permissions before turning on microsoft copilot. Follow the steps below to fix the issue.

Common Causes

Microsoft Copilot indexes content across your Microsoft 365 tenant, including SharePoint sites, Teams channels, and OneDrive libraries. Because Copilot respects existing permissions, it can only surface information that a user is already allowed to access. However, many small businesses have inherited permission structures that are overly broad or outdated. Before enabling Copilot, it is essential to audit your SharePoint permissions to ensure sensitive information—such as payroll records, director-level documents, or confidential client files—is not accidentally exposed to staff who should not see it. This article walks through how to review and tighten SharePoint permissions as part of your data governance foundation.

Why Permissions Matter Before Enabling Copilot

Copilot can summarise meeting action items, draft client proposals, analyse spreadsheets, and sort project correspondence. While these capabilities improve productivity, they also mean Copilot can retrieve and present content from any SharePoint site or library a user has access to. If your organisation uses "Everyone" or "All Staff" groups with Edit or View permissions on sensitive folders, Copilot may surface that information in response to natural language queries. Reviewing permissions first helps you meet Australian Privacy Act obligations and reduces the risk of accidental data exposure.

Quick Fix Steps

1. Identify SharePoint sites and document libraries containing sensitive data.
2. Review current permissions for each site, library, and folder.
3. Remove broad access groups such as "Everyone" or "All Staff" from sensitive content.
4. Assign permissions based on role or department using Microsoft 365 groups.
5. Test access with a non-admin account before enabling Copilot for your organisation.

Detailed Instructions

Step 1: Review Site Permissions in SharePoint

1. Sign in to the Microsoft 365 admin centre using an administrator account.
2. Open the app launcher and select SharePoint.
3. In the SharePoint admin centre, expand Sites and select Active sites.
4. Select the site you want to review.
5. Click the Permissions tab to view who has access to the site.
6. Look for groups such as Everyone, All Staff, or Organization with access to the site.

Step 2: Check Document Library and Folder Permissions

1. Navigate to the SharePoint site containing the document library.
2. Open the document library.
3. Select the folder or file you want to audit.
4. Click the Information icon (i) in the top-right corner, then select Manage access.
5. Review the Links, Direct access, and Groups sections.
6. Identify any sharing links set to People in your organisation or Anyone.

Step 3: Remove or Restrict Broad Permissions

1. In the Manage access pane, select the group or link you want to modify.
2. Click Stop sharing or Remove direct access as appropriate.
3. For editing links, select Link settings and change the scope to Specific people.
4. Grant access only to the relevant Microsoft 365 group or security group (for example, Finance Team or Directors).
5. Click Apply or Save to confirm changes.

Step 4: Use the SharePoint Admin Centre to Run a Permission Report

1. In the SharePoint admin centre, select Reports from the left-hand menu.
2. Choose Site usage to review site activity and access patterns.
3. For detailed permission auditing, go to the Microsoft Purview compliance portal to search for sensitive content and review who can access it.
4. Label sensitive documents using Sensitivity labels in Microsoft Purview to apply automatic protection.

Step 5: Test Access Before Enabling Copilot

1. Create a test user account that represents a standard staff member (not an administrator).
2. Sign in to SharePoint as the test user.
3. Attempt to access folders and files that should be restricted.
4. Confirm that the test user cannot view payroll, director-level, or other confidential documents.
5. Adjust permissions if the test user can access restricted content.

Troubleshooting

Users Still See Content They Should Not

• Check whether the user is a member of a Microsoft 365 group with site access.
• Review any anonymous or organisation-wide sharing links on the file or folder.
• Confirm that inheritance is not overridden at the folder level without your knowledge.
• Allow up to 24 hours for permission changes to propagate across Microsoft 365 services.

Copilot Does Not Return Expected Results

• Ensure the content has been indexed by Microsoft 365. New or recently moved files may take time to appear in search results.
• Verify that the user has at least View permissions on the site or library.
• Check that Copilot is enabled for the user's licence in the Microsoft 365 admin centre.

Next Steps

Once your SharePoint permissions are reviewed and tightened, you can proceed with enabling Microsoft Copilot for your organisation. Continue to monitor access rights regularly, particularly when staff change roles or when new document libraries are created. If you need assistance auditing your environment or configuring sensitivity labels, Open a Ticket.

If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?