How do I share a Loop Workspace for View only?

Hi @Tarang Patel, 

Welcome to Microsoft Q&A forum. 

Thank you for taking the time to share your experience and thoughts regarding Microsoft Loop. I truly appreciate your detailed feedback. 

Currently, Microsoft Loop does not support view-only permissions for workspaces or pages. Access to a workspace currently includes edit rights by design. Loop was created with the goal of active collaboration, so everyone invited to a workspace can edit and contribute content.  

I completely understand your point, being able to share a workspace widely for viewing without granting edit permissions would be extremely useful in various situations. This feature would allow creators to protect the integrity of their content while still enabling broader knowledge sharing across teams. 

As a forum moderator, I hope you understand that I don’t have the ability to modify or escalate product issues directly. However, I strongly recommend submitting your feedback through the Loop · Community. This is the most effective way to ensure your voice reaches the product team and can be considered for future improvements. 

Once you've submitted your feedback, feel free to share the link here in the comments. I’ll be happy to upvote it to help bring more visibility.  

Additionally, since many other users have expressed similar concerns but may not know where to submit feedback, if my response has helped you better understand the situation and guided you toward a possible next step, please mark it as the “Accepted Answer.” Your action will help pin this post to the top, making it easier for others in the community who are experiencing the same issue to find your feedback and support it.   

Thank you again for sharing your concerns and for being part of our community. 

If the answer is helpful, click "Accept Answer" and vote positively. If you have more questions about this answer, 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. 

Hey Chris,

Thank you for the feedback. I have no doubt that I am not the only one making this request. I can't imagine this wasn't considered by the Loop product team. It seems odd to me that only the "read-only" feature of CRUD was not implemented, and the much wider create/update rules for co-creation were. I wonder why that would be the case?