Skip to main content
Denada’s comment system lets you and your team discuss specific parts of a template without leaving the editor. You can have threaded conversations, tag teammates, and even collect feedback from external reviewers through a shared preview link.

​
Adding comments

To leave a comment on a template:
  1. Switch to the Comments tab in the right sidebar.
  2. Click Add comment.
  3. Type your message.
  4. Select which block or section of the email your comment refers to by clicking on it in the preview.
  5. Submit the comment.
Your comment appears in the sidebar alongside a highlight on the referenced block, making it easy for others to see exactly what you are talking about.

​
Threaded discussions

Each comment supports threaded replies. Click on an existing comment to expand it and add a response. This keeps conversations organized — one thread per topic instead of a single flat list.

​
@mentions

Tag a teammate in a comment by typing @ followed by their name. They will receive a notification so they know to take a look. This is useful for calling attention to a specific change or asking someone to review a section.

​
Public vs. private comments

Denada has two distinct comment systems, and they are treated differently:

​
Private comments

Private comments are created by your team inside the Denada editor. They are only visible to logged-in members of your Denada team — external reviewers never see them.
  • Private comments are the default when you add a comment in the editor.
  • Use them for internal feedback, design discussions, and notes to teammates.
  • You can change a private comment to public from the … menu next to the comment.

​
Public comments

Public comments come from the published preview page. When you publish a template to the web and share the link, anyone viewing that page can leave comments — no Denada account required.
  • Public comments are always visible to everyone, including external reviewers.
  • They appear with a different visual style in the sidebar so you can tell them apart from private comments at a glance.
  • You can make a public comment private from the … menu if you want to hide it from the published page.
  • If your project has variations, reviewers can switch between them from the Options menu on the published page and leave comments on each variation individually. Comments are filtered by variation so feedback stays tied to the right version.
Use private comments for internal iteration with your team, and share the published link when you are ready for external stakeholder feedback via public comments.

​
Resolving comments

Once feedback has been addressed, resolve the comment to keep the sidebar clean:
  1. Click the … menu next to the comment.
  2. Choose Resolve.
Resolved comments are hidden from the main view but are not deleted. You can view resolved comments by toggling the filter if you need to revisit past discussions.

​
Other comment actions

From the … menu on any comment, you can also:
  • Change location — move the comment to reference a different block.
  • Delete — permanently remove the comment.
  • Mark as unread — flag the comment so it appears as new again.

​
Denada acts on comments

Denada reads comments in the editor and can act on them. If it understands a comment as an actionable request, it will suggest changes to the template based on what was said. You’ll see a View suggested changes link below the comment — click it to see what Denada proposes, then Accept or Cancel just like any other proposed change. This means comments double as instructions. A teammate can leave a comment like “Remove the eyebrows” or “Make the CTA more urgent,” and Denada will generate the change for you to review.
Comment-driven suggestions are only available in the editor, not on the published web preview. Public comments from external reviewers will not trigger suggested changes automatically — but you can act on them yourself through chat.
You can share a read-only preview of your template with people outside your team — clients, stakeholders, or anyone who needs to review the work.
  1. Click the Share button in the editor toolbar.
  2. Copy the Preview link.
  3. Send it to your reviewers.
Reviewers who open the link can:
  • View the template exactly as it will render.
  • Leave public comments on specific blocks.
  • Participate in threaded discussions on existing public comments.
They do not need a Denada account to comment.
Public comments left by external reviewers are visible to your entire team inside the editor. Use them as a lightweight approval workflow — reviewers comment, your team resolves.

​
Best practices

  • Keep comments focused. One topic per comment thread makes it easier to resolve feedback systematically.
  • Use @mentions for action items. Tagging a person makes it clear who is responsible for the next step.
  • Resolve as you go. Clearing resolved comments keeps the sidebar useful and up to date.
  • Set visibility intentionally. Default to private for internal notes and switch to public only when you want external reviewers to see the discussion.