Comments & Mentions
Comments & Mentions allow project members to discuss database designs, provide feedback, and communicate directly within a project.
Instead of using external messaging tools, conversations remain connected to the project, making discussions easier to track and review.
Before you begin
Before using comments, ensure that you have:
- Joined a Workspace
- Access to a Project
- Permission to view or edit the project
[!NOTE] Only authorized project members can view and participate in project discussions.
What are Comments?
Comments allow team members to:
- Discuss database designs
- Ask questions
- Suggest improvements
- Review changes
- Record important decisions
Comments help keep project communication organized and accessible.
What are Mentions?
Mentions notify specific project members about a discussion.
Use mentions when you need:
- Feedback from a teammate
- Design approval
- Technical review
- Assistance with a database issue
Mentions help direct conversations to the appropriate collaborators.
Add a comment
To leave a comment:
- Open a Project.
- Navigate to the discussion or supported object.
- Select Add Comment.
- Enter your message.
- Submit the comment.
The comment becomes visible to other project members.
Mention a member
To mention a collaborator:
- Start writing a comment.
- Type @ followed by the member’s name.
- Select the appropriate member.
- Submit the comment.
The mentioned member is notified according to the project’s notification settings.
Comment information
Each comment may include:
| Property | Description |
|---|---|
| Author | Member who created the comment |
| Content | Comment message |
| Created | Date and time of creation |
| Edited | Last update time (if edited) |
| Mentions | Referenced project members |
Best practices
- Keep comments focused on the current discussion.
- Use mentions only when action or feedback is needed.
- Record important design decisions in comments.
- Be clear and respectful when providing feedback.
[!TIP] Comments are most valuable when they explain why a design decision was made, not just what changed.