TEAMS Loop Page : Owner & Creator of Page Cannot Edit

2026-05-20T16:11:52.02+00:00

In a Teams, I added a private Channel only for me to access (to do some testing before publishing to the whole team), I open a new Page (Loop) but I cannot edit it: it stays blank and I cannot do anything about it. Message: "You currently have permission to view this, not edit it."

I checked on the Sharepoint site: same issue.

I have all permissions.

I deleted the Teams cache: no success.

In my OneDrive settings, "Limited-access user permission lockdown mode" is inactive.

I open the Loop component in browser: "Read-Only You can view this, but it can't be changed." Go to 'Share' / Loop Component... select share it to everyone in my organisation and give "Can Edit" right. Copy the link in browser: same, can only view.

In the other channels, not private, this does not seem to happen: when creating a page, or opening an existing page, I can edit it.

So why cannot edit any page in this private channel?

Thank you for any help.

Microsoft Teams | Microsoft Teams for business | Teams and channels | Private channels
0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2026-05-20T18:54:21.0933333+00:00

    Hi @Boyer, Jean Paul [EMR/FCTL/PRM/LEIC],

    Thank you for providing such detailed information, it really helps clarify the situation. 

    Based on what you’ve described, this behavior is not expected. Microsoft documentation indicates that Pages and Loop components are supported in private channels, and users with access should be able to edit and collaborate on them.

    Private channels use a separate SharePoint site, where membership is automatically synced from Teams and cannot be managed independently. Because of this, any issue with provisioning or synchronization between Teams and SharePoint can impact access and editing capabilities.

    Given that editing works in standard channels but not in this private channel, the issue is most likely related to one of the following:

    • A membership or synchronization issue between the private channel and its SharePoint site
    • A provisioning issue with the private channel site
    • A tenant-level setting or policy configuration affecting Loop components

    For reference:

    Here are the recommended next steps you can follow:

    Loop functionality in Teams depends on tenant-level configuration. You may want to ask your IT administrator to verify that the required setting Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $true is enabled in your environment. If this setting is disabled or not fully applied, Loop components may appear as read-only even when permissions seem to be correctly configured.

    For more information: Manage Loop in your organization | Microsoft Learn

    If the issue continues, I recommend asking your IT admin to open a support ticket through the Microsoft 365 Admin Center by following the steps here: Get support - Microsoft 365 admin | Microsoft Learn

    This will allow Microsoft support engineers to investigate more deeply by:

    • Checking the private channel SharePoint site provisioning and sync status
    • Verifying backend permissions and membership mapping
    • Reviewing tenant-level settings (including Loop/Fluid configuration)
    • Identifying any service-side issues.

    If you’re unsure who your IT admin is, you can find guidance here: How do I find my Microsoft 365 admin? - Microsoft Support

    I hope this information helps you move forward. If you have any questions or need further clarification, please feel free to reach out. I’ll be glad to assist.

    Thank you for your understanding, and I look forward to continuing to support you.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".        

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.