How to Limit Guest Permissions on a Teams-Connected SharePoint Site
Question details
The user needs to restrict guest access on a SharePoint team site connected to Microsoft Teams to prevent external users from inheriting broad editing capabilities.

- Product
- Microsoft SharePoint and Microsoft Teams
- Device & OS
- not provided
- Scenario
- A guest invited to a Microsoft Teams team automatically inherits member-level access to the connected SharePoint site, granting them unintended abilities to edit content and site components.
- Observed behavior
- The guest maintains full member permissions because the broader access granted by the Microsoft 365 group overrides any custom restrictive permissions applied directly in SharePoint.
Ensure you have Site Owner privileges on the SharePoint site and Owner status in the connected Microsoft Team to manage group memberships and modify site-level access settings.
Remove Guests from the Teams Group and Share Specific Content Directly
Prevent guests from inheriting broad editing permissions by removing them from the Microsoft 365 Members group and sharing only the required files or folders.
SharePoint permissions are cumulative. Because the site inherits access from the Microsoft 365 group connected to Teams, a guest in the Teams Members group will always have member-level access. A restrictive custom permission level on SharePoint cannot override this broader access.
Open Microsoft Teams, click the three dots (...) next to your team name, and select 'Manage team'. Under the 'Members' tab, locate the guest and click the 'X' to remove them from the group.
Open the associated SharePoint team site and navigate to the specific Document Library, file, or folder that you want the guest to access.
Select the file or folder, click the 'Share' button, and enter the guest's email address. Click the settings gear icon to specify the permission level (e.g., 'Can view'), apply the changes, and click 'Send'.

Clear User Permissions and Assign to a Custom SharePoint Group
Completely remove a guest's existing permissions from the site directory and place them into a restricted, SharePoint-only custom group.
Set Up a Dedicated Communication or Client Site
Create an entirely separate SharePoint site specifically for external sharing to guarantee a strict separation between internal team files and guest content.
Manage Your Team's Documents Securely with WPS Office
While managing SharePoint and Teams permissions can become highly complex, WPS Office offers a lightweight, free alternative for creating, editing, and sharing your documents securely. Enjoy powerful office tools with highly customizable file-sharing links, making team collaboration straightforward without the headache of complex group permission structures.
- 1. Download and install: Download WPS Office for free from the official website and install it on your device.
- 2. Open your files: Easily open your existing Microsoft Office documents without worrying about formatting issues.
- 3. Share securely: Use WPS Office's built-in sharing capabilities to generate secure links with precise access controls, bypassing complex server-level permissions.

Frequently Asked Questions
Why does my SharePoint guest have full edit permissions?
When a SharePoint site is connected to Microsoft Teams, any guest added to the Team is automatically added to the underlying Microsoft 365 Members group. This group grants member-level access (which includes edit permissions) across the entire connected SharePoint site by default.
Can I restrict a guest's access to just one folder on a Teams-connected site?
Yes, but they must not be a member of the overarching Microsoft 365 Team. Remove the guest from the Teams Members group first, then go to the specific folder in SharePoint, click Share, and send a targeted link granting only View or Edit access to that specific folder.
Do restrictive SharePoint permissions override Microsoft 365 group permissions?
No. SharePoint permissions are cumulative. If a user is granted broad access via the Microsoft 365 Members group, assigning a custom restrictive permission level to them directly on the site will not override or limit the broader access they have inherited from the group.




