Skip to content
Letterhead Letterhead Letterhead Help Center
Admin Tools

Approvals

Edit in CMS

If your newsletter goes through a second pair of eyes before it goes out, such as an editor’s sign-off or legal clearance, Approvals lets Letterhead enforce it. A rule can also set the bar a newsletter has to clear, such as how easy it is to read or how many broken links it may have. Until a newsletter meets its rule, it can’t be scheduled or sent, whichever browser or device someone uses. See What isn’t covered below for the few kinds of sends approvals leave alone.

Approvals lives in your company settings: open Settings, then Approvals. It has two tabs, Rules and Reviewers. Company administrators manage both.

A reviewer group is a named set of people from your team, such as Legal or Editors, whose sign-off you can require. One person can be in several groups.

  1. On the Reviewers tab, choose Create reviewer group.
  2. Give the group a name and, if you like, a description of what it signs off on.
  3. Choose its members from your company team, and select Save group.

Deleting a reviewer group asks you to confirm. You can’t delete a group while an enforced rule requires it, and you can’t remove members from a group if that would leave it with fewer people than an enforced rule asks to sign off. If either change doesn’t go through, change or remove that requirement first.

A rule says what a newsletter needs before it can be scheduled, and which newsletters it applies to.

  1. On the Rules tab, choose Create a rule and give it a name, such as Legal sign-off.
  2. Under Newsletters, choose the newsletters it applies to. A newsletter follows one rule at a time, so newsletters already under another rule show as locked. Take a newsletter off its current rule before adding it to a new one. A rule can also have no newsletters at all, which is how you stop applying it without deleting it.
  3. Turn on Require review to ask for sign-offs, then add a requirement such as at least one approval from Legal. Every requirement must be met, and a requirement can’t ask for more approvals than its group has people; Letterhead won’t save it. If you haven’t added any reviewers yet, Manage reviewers takes you to the Reviewers tab, saving the rule first.
  4. Under Quality checks, turn on any you want and set the bar for each:
    • Readability — the readability score is at least the number you choose, out of 100. Higher is easier to read.
    • Email weight — the email is no heavier than the size you choose. Gmail clips emails past roughly 102KB.
    • Broken links — no more than the number of broken links you choose. Only available on newsletters where the link scan is on.
    • Bounce risk — bounce risk is low. Only available on newsletters where that check is on.
  5. Choose Enforced or Not enforced:
    • Enforced — newsletters can’t be scheduled or sent until they meet every requirement and check.
    • Not enforced — the checklist shows in the composer, but nobody is stopped. A new rule starts here, so you can try it out first.
  6. Decide whether company administrators can schedule without meeting the rule (see below). This is on for a new rule.
  7. Select Save.

Each rule shows as a card on the Rules tab, with whether it’s enforced, its requirements and checks, and how many newsletters it covers. Use the card’s menu to edit, duplicate or delete it. Deleting an enforced rule asks you to confirm, because anyone on its newsletters can then schedule without it. If Letterhead can’t save a rule, it tells you why, and closing a rule with unsaved changes asks you to confirm first.

On a newsletter with a rule, the schedule sidebar’s Before You Can Schedule checklist includes the rule: one line for each review requirement and each quality check, such as Get 1 approval from Legal or Readability at least 60. A line is ticked off once it’s met. Everyone sees the same results.

While anything on an enforced rule is unmet, Schedule and Send now are unavailable, and pointing at Schedule tells you why. A company administrator on a rule that allows bypass keeps both, behind a confirmation (see below). Under the matching check in Checked For You, a line names the rule’s bar while it isn’t met. A check whose scan is still running counts as unmet and says it’s waiting on the scan; once the scan finishes and passes, the hold clears on its own. The quality checks measure newsletters written in the HTML editor the same way as ones built in the composer.

On a rule that isn’t enforced, the checklist shows the same lines, with a note that they don’t block scheduling.

Select Request beside a review line, such as Get 1 approval from Legal, and Letterhead asks everyone in that reviewer group to review the newsletter, in one click, up to 20 people. You aren’t asked to review your own newsletter, and anyone in the group who has already approved it isn’t asked again. If there’s nobody left to ask, Letterhead tells you. To ask particular people instead, use Request review at the foot of the checklist.

A reviewer signs off with Approve in the newsletter’s review panel. Only people in the required reviewer group count toward a requirement.

A sign-off covers the version the reviewer saw. If the newsletter’s content or subject line changes after someone approves it, that approval no longer counts and the requirement comes back. Changing the send time or other details doesn’t affect it.

For a newsletter written in the HTML editor, only a change to the subject line cancels a sign-off. Editing the HTML body after someone approves it leaves their approval standing. The quality checks are still measured again before it goes out, unless a company administrator scheduled it past the rule; then a body edit doesn’t hold it either.

Unless you turn it off on the rule, a company administrator can schedule a newsletter that doesn’t meet an enforced rule. Channel administrators and contributors can’t. Letterhead asks a company administrator to confirm before scheduling or sending past it. The bypass is recorded, with who did it, when, and what wasn’t met, only once the newsletter has actually been scheduled, and it’s shown on the newsletter.

Some sends are never held by approvals: resends to non-openers, notification emails, A/B test versions, and transactional emails.

Everything else is held, however it’s sent. While an enforced rule is unmet, an automation’s newsletter is created as a draft instead of being sent, and it can be scheduled once it meets the rule. A newsletter is checked again at send time, so content edited after scheduling can’t go out unapproved. That includes a newsletter a company administrator scheduled past the rule: if it’s edited afterwards, it’s held. For a newsletter written in the HTML editor, see Editing after a sign-off above for what counts as an edit. Sending through the API is held too, and creating a newsletter that is already scheduled on a newsletter with an enforced rule is refused: create it as a draft, then schedule it once it meets the rule.

Still can’t find what you need? Contact support.