Blog Post
Copilot Pages & Notebooks, Microsoft Loop: IT Admin Update – December 2025
The only feature I’ve been waiting for since 2024 is Read-only members, and seeing it paused makes me genuinely disappointed. In our organization, we rely heavily on Loop for knowledge base management, and having too many members with editing rights is extremely risky. The edit lock is helpful, but it doesn’t solve the issue if a user still has permissions to modify content.
Similarly, in a structured organization, the limit on nested pages becomes a serious obstacle. Eventually, you’re forced to create multiple Loop projects, which quickly becomes unmanageable since there’s no effective way to organize them.
I’ve noticed many users across forums requesting these two features. At first, I thought it was just me, but it’s clearly a widespread need. From our perspective, they seem simple to implement (though we understand there may be complexities behind the scenes). Still, I don’t understand why they were paused.
I sincerely hope these features can be release soon. They would make a huge difference for organizations like ours.
- TomGullbergMar 17, 2026Copper Contributor
Hi, just wondering if you have explored the possibility of changing role for users to "Reader" in the SPO admin portal? Not ideal for overall governance but could be a solution for certain Workspaces with few users
- dubalimaMar 10, 2026Copper Contributor
Same here - I'm desperately trying to move away from Notion and consolidate everything in Loop, but the lack of "read-only" access to Loop Workspaces has been a huge downfall.
Does this comment count as "feedback volume"?
Now I'm trying to convince my HR to move all content to Loop, but I cannot provide a safe way for my team to access content while maintaining editing governance. And we all know that "sharing individual pages as read-only" helps (thanks for it, by the way), but obviously does not scale.