Skip to main content

Submission messages

Updated this week

Submission messages allow you to communicate directly within a submission. They help you collaborate internally, request clarification from researchers, and keep all discussion related to a finding in one place.

βš™οΈRoles: All roles.
πŸ’‘Note: Users with read-only access can post internal messages only.

Posting a message

  1. Go to Submissions and open the submission you want to comment on.

  2. Scroll to the message section of the submission.

  3. Write your message in the input field.

  4. Choose whether the message should be internal (default) or external.

    1. Internal messages: visible to all company users and triagers with submission access.

    2. External messages: visible to all company, triagers and researchers with submission access. (Highlighted in blue 🟦)

  5. Click Send to post the message.

Mentioning users in massages

You can mention specific users in a message by typing the @ symbol followed by their username. Mentioned users receive a notification, helping you draw attention to questions, follow-ups, or required actions.
​

Mentions respect message visibility. In internal messages, you can mention company users and triage who have access to the submission. In external messages, you can also mention the researcher who submitted the finding and their collaborators.

πŸ’‘Note: User groups can't be mentioned in messages.

Message states and notifications

When a new message is posted on a submission, the submission automatically receives a New Message label in the submission overview. This makes it easy for anyone with access to the submission to identify items that require attention. To support timely follow-up, assignees also receive email notifications when messages are added by researchers, triagers, or team members.

The platform supports marking messages as read at an individual level. You can mark one or more messages as read by selecting them in the submission overview and using the available bulk action.

πŸ’‘Note: Messages can't be marked as unread and can't be marked as read by the entire company. Each user’s read status is tracked individually.

Best practices

  • Use internal messages for coordination and decision-making within your team.

  • Use external messages when communicating directly with researchers about findings or retests.

  • Mention users sparingly to keep notifications relevant and actionable.

  • Keep discussions focused on the submission to maintain a clear audit trail.

Related articles

Did this answer your question?