Loop component not editable in Teams app but editable in browser

Question

Loop component not editable in Teams app but editable in browser

ASloan 0

When I share a loop component in a Teams Meeting chat it is not editable by my team members. Even after I update the permissions settings to anyone at the organization can edit. If they open it in the browser, they can edit the loop. However in the app, they are not able to. Is there a setting I'm missing to grant them access in Teams?

0 comments

3 answers

Your answer

Answer 1

For work or school Teams, Loop components are expected to be editable inline, so browser editing combined with failed desktop editing points to the Teams client rather than another file-permission setting.^1^

Refresh the affected Teams clients

Have each affected member perform these steps:

In Teams, select Settings and more (…) → Settings → About Teams and record the version.
If an update is offered, select Update → Update and restart Teams. Teams normally updates automatically while idle, but an available update can be installed immediately.^2^
After Teams reopens, return to the original meeting chat, click directly inside the component, and try typing.
If it remains read-only, sign out of Teams, completely quit the application, reopen it, and sign in again. This refreshes the client session rather than changing the already-working Loop permission.^3^
If that does not resolve it, clear the Teams cache using Microsoft’s platform-specific cache procedure, then reopen Teams. As a final client repair, uninstall and reinstall Teams.^4^

Continue using Open in browser while testing; edits made there update the same .loop file stored in OneDrive.^5^

Check the account type

The expected behavior differs by edition:

Teams work or school: Everyone in the chat should be able to edit the component inline. A valid OneDrive license is required for the Loop collaboration option; if one was assigned recently, restart Teams.^1^
Teams Free/personal: A Loop component can appear as a link that opens in a browser rather than rendering inline. That is documented behavior for the personal edition.^6^

Administrator checks if every desktop user is affected

Do not change the sharing link again; successful browser editing establishes that those users already have edit access. Also, Loop admin controls govern creation and Teams integration but do not restrict access to existing Loop files.^7^

An administrator should instead verify that Teams Loop integration is enabled tenant-wide:

For Loop components in Teams chats and private meetings:
Set-SPOTenant -IsLoopEnabled $true
For collaborative meeting notes and applicable channel experiences:
Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $true

Teams integration uses these SharePoint tenant properties; Cloud Policy alone does not control the relevant Teams experiences.^7^

If the component renders interactively for some users but not others, a tenant-wide disabled setting is less likely. Compare the affected and unaffected users’ Teams version, platform, account type, and OneDrive licensing.

Escalation

There is no documented general condition under which work/school Teams should be browser-editable but intentionally read-only in the desktop client. If updating and resetting Teams does not fix it, open a Microsoft 365 support request and include:

Teams versions from affected and unaffected devices
Operating systems
Whether Teams for the web permits inline editing
Whether all Loop components or only that meeting’s component are affected
Meeting type: private, channel, or recurring
Confirmation that the same users can edit the file in the browser

References

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

Chris-D 2,700 Independent Advisor

Hi ASloan,

Thank you for providing the details of your situation.

Since your team members can edit the Loop component when opening it in a browser, the sharing permissions appear to be working correctly. The issue may instead be related to the Teams app, the participants’ account type, or an organizational policy affecting Loop components in Teams.

To help narrow this down, could you please confirm the following?

Are the affected team members internal users in the same organization, or are they guest or external users?
Does the issue occur in the Teams desktop app, the Teams mobile app, or both?
Can the affected users edit Loop components in a regular one-to-one or group chat outside the meeting chat?
Are all affected users signed in to Teams with the same organizational account that has permission to access the component?

In the meantime, you may ask the affected users to update Teams to the latest version, sign out and back in, and then test the component again. They can also try clearing the Teams cache or using Teams on the web to determine whether the issue is specific to the desktop client.

Please feel free to share the information in the comment below. Once I have it, I'll be better positioned to guide you through the next steps.

I look forward to hearing your thoughts.

Note: Follow the steps in the forum documentation to enable email notifications if you want to receive email notifications related to this topic.

ASloan 0 Reputation points

2026-11-10T17:07:52.2833333+00:00
Thank you!

They are all members of the organization

In the desktop app

They can edit if other team members create the loop, just not me

All members are signed into the same organizational account
Chris-D 2,700 Reputation points Independent Advisor

2026-11-10T17:28:11.8633333+00:00
Hi ASloan,

Thank you for confirming these details.

Since all affected users are members of the same organization and they can edit Loop components created by other team members, this does not appear to be a general Teams or organization-wide Loop policy issue.

Loop components created in Teams are stored as .loop files in the creator’s OneDrive. As the issue only affects components created by you, it may be related to the sharing configuration of the Loop files in your OneDrive or how the Teams desktop app is processing access to those files.

Here are some steps you can try:

Create a new Loop component in a regular Teams group chat and check whether the other members can edit it directly in the Teams desktop app.

Ask one affected member to open the same chat in Teams on the web and test whether the component is editable there.

In OneDrive, locate the affected .loop file, open Manage access, and confirm that the members have Can edit permission. If possible, remove the existing sharing link, create a new organization-wide editing link, and share the component again.

Sign out of the Teams desktop app, close Teams completely, reopen it, and sign back in.

If a newly created component is still editable in the browser but not in the Teams desktop app, while components created by other users work normally, this may indicate a client-side issue affecting components owned by your account. In that case, please report the issue through Settings and more > Feedback > Report a problem in Teams and ask your Microsoft 365 administrator to open a support request with Microsoft Support from the Microsoft 365 admin center.

For detailed guidance on how to open a support ticket with Microsoft Support, please refer to: Get support - Microsoft 365 admin | Microsoft Learn

In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support

I hope this can be resolved for you soon.