Comments and Approval

Temway brings review into the email editor. From a single Review drawer you can leave threaded comments, @mention teammates for input, and request an optional sign-off. Everything stays attached to the email you’re reviewing, so feedback never gets lost in a separate chat thread.

Opening the Review drawer

In the editor header, the Comments button is your entry point. It carries two signals at a glance:

A red count badge showing how many comments are still unresolved.
A small colored dot reflecting the current approval status — gray when no review has been requested, yellow when one is in progress, green when approved, orange when changes have been requested.

Click it to open the Review drawer on the right side of the screen.

How the drawer is organized

The drawer is a single chronological feed of everything that’s happened in the review — comments and approval events interleaved, oldest to newest, like a conversation. A segmented control at the top lets you switch between two views:

Open — unresolved comment threads plus all approval activity.
Resolved — comment threads that have been marked resolved (an archive of finished conversations).

The approval status sits in a pinned banner at the top of the drawer, separate from the feed.

Leaving comments

Anyone on the team can comment — including viewers, not just editors.
Two-level threads — you post a top-level comment, and each one can have one level of replies. Reply-to-reply isn’t allowed, which keeps discussions tidy and on track.
Edit and delete — you can edit your own comments at any time. You can delete your own, and admins can delete anyone’s.
@mentions — type @ in the comment box to pick a teammate. Mentioned teammates get an email notification (this is the review feature’s only notification channel), so use @mentions when you want someone to actually see your note.

Resolving and reopening

Any team member can mark a top-level comment as resolved — it moves to the Resolved view and the unresolved count in the header drops. Resolving works on whole threads, not individual replies, so you close out an entire topic at once.

Resolved threads aren’t deleted — anyone can reopen one if the conversation needs to continue.

Requesting approval

Approval is a lightweight advisory status that lives in the banner at the top of the drawer. It moves through four states:

No review requested — the default. Nothing’s been asked for yet.
In review — an editor has requested a sign-off.
Approved — an editor has signed off.
Changes requested — an editor has asked for revisions.

Editors (and above) see contextual actions in the banner:

Request approval — moves the email to In review. You can re-request at any time, from any state — useful after a Changes requested verdict once you’ve addressed the feedback.
Approve — available only while the email is In review. Marks it Approved.
Request change — available only while the email is In review. Marks it Changes requested and surfaces the hint “Address the feedback below, then request approval again.”

Every approval action appears as a small colored row in the feed — “Name approved · 2h ago*” — so the review history reads as a single timeline alongside the comments.

Commenting and deciding in one action

When you’re an editor, the comment composer at the bottom of the drawer offers a Comment & … split. It lets you post a comment and make an approval decision at the same time — for example, leaving specific revision notes while simultaneously requesting changes, or thanking a teammate while approving. It’s the same two actions as the banner, just combined with a written note.

Approval never blocks publishing

This is the most important thing to understand: approval is advisory only. You can publish an email regardless of its approval status — In review, Changes requested, or no review at all.

Think of it as a team signal and a record of who signed off, not a gate. If your workflow needs a hard “must be approved before send” rule, set that expectation with your team rather than relying on the badge — Temway won’t stop you from publishing.

Why this matters

Feedback stays in context — comments live on the email, not in a side channel.
The right people see it — @mentions route notifications to exactly who needs to weigh in.
A clear review history — the feed shows who said what, who approved, and when, in one place.
No workflow lock-in — because approval never gates publishing, the review process bends to how your team actually works instead of forcing a rigid sign-off chain.

Next steps

Set up your team so the right people can be mentioned and asked to review.
Understand how approval interacts with version history when you publish.
Send a polished draft with exporting and HTML.