Hi @CYZ,
Thank you for sharing that context and for exploring other avenues. I completely understand your reasoning. While the "one post per question" model would technically solve the notification issue, it comes at the cost of the very user experience you’re trying to create. It would fragment the Q&A from the main discussion, defeating the primary benefit of using a single, consolidated Loop component.
Your expectation for component-level notifications is perfectly valid. Ideally, notifications would be configurable for the component itself, alerting everyone who has access to it regardless of whether they are in Teams, Outlook, or another tool. The way you’ve highlighted the need for "alerting everyone who has access" is not only insightful but also reflects a deep understanding of user needs.
This brings us to the core technical constraint: the Teams notification system is tied to the "container" (the chat message or channel post).
Feedback like yours is truly valuable and helps shape the future of the platform. I have shared your feedback internally, and I also strongly encourage you to submit it directly to the product team. Your detailed scenario provides a powerful use case for why this functionality is needed. You can do this via the "Feedback" > "Suggest a feature" option in Teams.
Thank you again for your patience and your insightful feedback on this.
If my response has helped clarify the situation or guided you toward a possible next step, please consider marking it as the “Accepted Answer” to my answer. Doing so will help pin the post to the top, making it easier for others in the community to find and support your feedback.
Thank you once again for your time, engagement, and for being a valued part of the community.