Skip to content
This repository was archived by the owner on Dec 29, 2025. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/concepts/communication.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,14 @@ There are two main types of communications in meshStack:

2. **Action Required**: Automates assignment of actionable tasks including security reviews, access validation, and metadata accuracy checks. These tasks ensure compliance and accountability by embedding ownership directly into workflows, providing stakeholders with real-time visibility into progress and reducing manual tracking overhead. You can also assign a due date to the action required communication to ensure timely completion.

## Skip Email Notifications

When creating a communication in meshStack, you can control how it's delivered to recipients.
Communications are always visible in meshPanel in the workspace receiving the communication.
All users responsible for the communication's target object, for example a building block, will receive an email notification about the new communication.

The "skip email notifications" option allows you to instruct meshStack to skip sending this email.

## Related Resources

- [How to Maintain Security Contacts with meshStack](../guides/developer-engagement/how-to-provide-security-contact.md)
Expand Down