'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Remove Microsoft Loop Access After Removing a Mention
Question details
The user wants to revoke access for a person who was previously mentioned on a Microsoft Loop page, but deleting the mention did not remove their permissions.
- Product
- Microsoft Loop
- Device & OS
- not provided
- Scenario
- Trying to manage page access and revoke permissions after removing a user's @mention in a Loop workspace.
- Observed behavior
- The mentioned person retains access even after the mention is removed, and Loop incorrectly displays a 'not the content owner' error when attempting to manually adjust permissions.
Ensure you are logged into the correct Microsoft 365 account and verify whether you initially created the Loop page or workspace, as owners typically have full permission control.
Contact Your Microsoft 365 Admin for Backend Support
If you receive a 'not the content owner' error, it is a known backend syncing issue that requires administrative intervention.
Because the permission persists after removing the mention, this is a backend access-management issue within Microsoft Loop. Only your Microsoft 365 Administrator can open a support ticket to have Microsoft engineers review the service logs and clear the stuck permission.
Locate your organization's Microsoft 365 admin, which is usually your IT support department or system administrator.
Ask the administrator to log into the Microsoft 365 admin center and navigate to the 'Help & support' panel.
Provide your admin with the specific Microsoft Loop page URL, the name of the user whose access will not detach, and a screenshot of the 'not the content owner' error so they can submit it to Microsoft Support.
Manually Remove Access via the Loop Share Menu
Attempt to manually remove the user's direct access or sharing link before escalating to IT support.
Looking for a Simpler Way to Collaborate? Try WPS Office
If complex permission settings and backend errors in Microsoft Loop are slowing down your team, consider switching to WPS Office. It provides lightweight, highly compatible, and easy-to-manage document collaboration tools without the hassle.
- 1. Install WPS Office: Download and install WPS Office from the official website.
- 2. Sign In to WPS Cloud: Sign in or create a free WPS account to access cloud collaboration features.
- 3. Manage Permissions Easily: Upload your existing documents to WPS Cloud for easy link-sharing and straightforward permission controls.
Frequently Asked Questions
Why does removing an @mention in Loop not revoke access?
When you @mention someone in Microsoft Loop, the system grants them direct access to the page to ensure they can see the context. Deleting the text of the mention does not automatically trigger a permission revocation in the backend, meaning their access remains active until manually removed.
Why does Microsoft Loop say I am not the content owner?
This error can occur due to a backend synchronization issue between Microsoft Loop and SharePoint/OneDrive. Even if you created the page, the system might fail to recognize your permissions, requiring a Microsoft 365 admin to reset the access logs.
Can I prevent users from getting permanent access when mentioned?
Currently, mentioning a user in a restricted Loop component automatically grants them access so they can view it. To share information without granting permanent editing rights, consider sharing a view-only link via the 'Share' menu instead of using the @mention feature.
