How to trigger notifications on loop

Question

We use loop to track statuses of projects across our team. Last year we used a loop component within Microsoft Teams which automatically sent an email to my boss any time something was added or updated. This year we switched to a loop stand alone work space however she does not recieve notifications when something new is added. As a work around, we have been tagging her in the notes section which will automatically send an email that she has been mentioned but it says "author fail" and she can't see the note when it is sent to her email. Is there anything I can do to fix this?

Answer 1

Dear @Carbone Daniella, 

Good day, and I appreciate the clear explanation of your concern.   

Currently, standalone Loop workspaces focus email notifications around @mentions rather than sending updates for every edit, unlike when Loop content was used in Teams. 

When a recipient sees an “author fail” message, it usually means the notification was delivered successfully, but access needs to be granted so the linked Loop content can open properly. 

Below are the recommended steps to address this behavior: 

Step 1: Confirm your manager has direct access to the Loop workspace and page 

Open the Loop workspace where your project tracking content is stored. 

Use the Share option in the top right corner of the Loop workspace. 

Add your manager’s account directly rather than relying on inherited or indirect access. 

Ask her to open the Loop workspace and the specific page in a browser to confirm access before testing @mentions again. 

This step is essential because @mention notifications only work if the recipient already has permission to view the content. 

Step 2: Verify the sharing scope of the Loop component before mentioning 

If you are using @mention inside a specific Loop component such as a table or paragraph, make sure the component itself is shared correctly. 

Click the component title or open the component sharing or permission settings. 

Set the access scope to include your manager, for example: Allowing people in your organization with the link or explicitly adding her under a specific people permission. 

After updating permissions, mention her again in the component. 

If the component’s sharing scope does not include the recipient, the link in the email will not open even though the email is delivered. 

Note: The @mention email serves as a pointer to the content. The full and most up‑to‑date information is only visible after opening the Loop link. Email notifications are not designed to display the edited content itself. 

• If email notifications are required for frequent updates (recommended): 

If your manager needs reliable notifications, consider keeping the project tracker as a Loop component embedded in a Teams chat or channel so you can use @mentions to trigger notifications. The same Loop component will remain synced across Teams and the Loop workspace, so you can still organize it in the workspace for reference. 

I completely understand how these limitations in Standalone Loop can feel disruptive. It’s not just about aesthetics; these differences can genuinely affect how smoothly you work and navigate your day. 

I’m really sorry, I know this isn’t the outcome you were hoping for. 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. If you prefer, I can also submit this great idea on your behalf. Just let me know, and I’ll post it for you and share the link once it’s published. I’m here to help ensure your feedback gets the attention it deserves. 

Additionally, as other users have raised similar concerns and may not be aware of where to share their feedback, I hope this response helps clarify the situation and suggests a potential next step. Highlighting this information can make it more visible to others in the community who may be facing the same issue, making it easier for them to find guidance and contribute their feedback as well. 

Thank you again for your time and for raising this important usability concern. 

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any 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. 

Answer 2

Loop notifications and @mention behavior are controlled by the app where the Loop component is used and by how sharing is configured. From the available information:

• When a person is @mentioned inside a Loop component, they receive an email notification with a link to the component. This is the expected way to notify someone of new or updated content in Loop.
• The email contains a link back to the Loop component; the content itself is not fully embedded in the email. The recipient must open the link to see the latest content.

In the current documentation, there is no supported way to:

• Automatically send an email on every change in a standalone Loop workspace without using @mentions, or
• Change the notification so that the full updated note is visible directly in the email instead of via the link.

For the “author fail” behavior in the email body, no specific fix or configuration is documented in the provided material. The supported pattern is:

1. Ensure the boss has access to the Loop workspace/page and the specific component (shared with the correct account and permissions).
2. Continue using @mentions inside the Loop component so that an email notification with a working link is sent.
3. Have the boss open the Loop component from the email link to view the content directly in Loop.

If this behavior is not acceptable, the only documented path to influence product behavior is to submit feedback from within Loop (Help > Give feedback) so the scenario can be considered for future improvements.

---

References:

• Use Loop components in Outlook
• Use a screen reader with Loop components in a chat in Microsoft Teams
• First things to know about Loop components in Microsoft Teams
• Use Loop components in Word for the web
• Planner" is no longer showing up as a Microsoft App in Loop - Microsoft Q&A
• Why does Microsoft Loop only show male images for 'manager' when adding an icon to a page? - Microsoft Q&A
• Cannot be added to TEAMS CHANNELS - Microsoft Q&A
• Who's Following Me? - Microsoft Q&A
• I want to choose which email to send from - Microsoft Q&A