Who reviews a draft
See which people get each automation and sequence draft in For review, who can see it, and who can send it.
Available on Pro, Growth and Enterprise
Every draft in For review goes to specific reviewers, never to everyone in the workspace. This page explains who they are, who else can see a draft, and who can send it.
Who can use it
Section titled “Who can use it”For review is on Pro, Growth and Enterprise. Owners, admins and members can review drafts; Viewers can’t.
Earlier plans can differ. Check your workspace’s available features.
Automation email drafts
Section titled “Automation email drafts”An automation email draft goes to the workspace member it was drafted as: the sender its step names. It doesn’t go to everyone who can see the run.
- A run acting as a specific user always drafts as that user.
- A run acting as the workspace drafts as the sender its step names. If the step names no sender, the run creates no draft rather than sending it to nobody or everybody.
The sender determines whose review list receives the draft. The run’s identity also determines who can see it: a run acting as a specific member uses that member as sender, while a workspace run needs a named sender. See Build an automation.
Only the owner of the sending mailbox can send an automation email draft. Other reviewers, such as admins, can see it but can’t send it on that person’s behalf.
Sequence drafts
Section titled “Sequence drafts”Sequence drafts go to:
- the person whose account the message will send from
- the sequence’s creator
- any extra reviewers set on the sequence
See Build a sequence.
Who can see an automation draft
Section titled “Who can see an automation draft”An automation draft is visible only to people who can see the run that created it.
- A run that acted as a specific user produces drafts that only that user and workspace admins can see.
- A run that acted as the workspace produces drafts visible across the workspace.
Test runs and redrafts
Section titled “Test runs and redrafts”- An automation test run creates real drafts in For review, just like a live run.
- A sequence test run sends nothing and leaves no drafts.
- Drafts from different automation runs stay separate. If the same run and step redrafts an email from the same sender to the same recipients, the new draft replaces the earlier one.
Troubleshooting
Section titled “Troubleshooting”For review is empty but the automation ran
Section titled “For review is empty but the automation ran”For review shows No items for review. The draft went to someone else, or it was never created. An automation email draft goes only to the member it was drafted as, and a workspace run whose step names no sender creates no draft. Open the run to see which sender the step used, and ask the agent in chat to set the right sender. See Runs and held runs.
An admin can see a draft but can’t send it
Section titled “An admin can see a draft but can’t send it”The draft sends from another member’s mailbox. Only that mailbox’s owner can send it. Ask them to approve it, or change the sender in the automation.
Common questions
Section titled “Common questions”Who gets an automation’s email draft? The member it was drafted as, which is the sender its step names. A run acting as a specific user always drafts as that user.
Can an admin send a draft from someone else’s mailbox? No. Admins can see the draft, but only the owner of the sending mailbox can send it.
Do all reviewers have to approve a sequence draft? No. Only one reviewer needs to act, and the draft then leaves For review for everyone.
Does an empty For review mean the automation did nothing? No. It means nothing is waiting on you. The draft may have gone to another member, or the step had no sender.