Readers can subscribe to your changelog on your portal and get the entries you publish by email. They confirm their address before anything is sent, and you choose for each entry whether it's emailed.
How readers subscribe
On a public portal, the Changelog page has a Get updates by email box, and so does the Get updates card beside each feedback board. You can't add subscribers yourself.
The reader enters their email address and chooses Subscribe. If they're signed in, their address is filled in.
They get an email asking them to confirm, with a Get updates by email button.
The link opens a page on your portal, where they choose Get updates by email once more. The page then says they get your updates by email.
A confirmation link works once, for 24 hours, and only the latest one a reader was sent. If it has run out, they ask again on the changelog. Nothing is emailed to an address until it's confirmed.
A signed-in reader who already gets your changelog sees where it goes instead of the box, with Manage, which opens their Account settings. There they can also turn The changelog on or off without confirming by email, once their address is confirmed. See Choose which emails a portal sends you.
Email an entry
In the entry's sidebar, under How it's announced, Email subscribers is ticked to start with. Its note says how many people would get it now, such as "48 people subscribed on your portal's changelog." Untick it to publish without emailing.
When you choose Publish, Tuti says who will be emailed before you confirm.
Each entry is emailed once, the first time it's published with Email subscribers. If you unpublish it and publish it again, it only goes to subscribers it hadn't reached yet.
It goes to the people who had confirmed by the time you published it. People who subscribe later get your next entry.
Published without emailing? Unpublish it, tick Email subscribers and publish it again.
The email has the entry's title as its subject, after your project's name, and the whole entry with its cover image, a See the update button and an Unsubscribe link. It comes from your project's name. Once you've set up your own email address, it comes from your domain.
After publishing, How it's announced says how it's going: Being emailed to subscribers: N still to go. while it sends, then Emailed to N subscribers.
In a new project's first week, Tuti limits how many emails it sends each day, so a long list can take more than a day. The rest go out by themselves.
When an entry isn't emailed
Your portal is private: private portals don't have the box, and their changelog isn't emailed to anyone. Email subscribers says "Your portal is private: its changelog isn't emailed." Making the portal private also stops a send that's under way. Private portals are on the Business plan; see Make your portal private.
Nobody has subscribed: Email subscribers can't be ticked, and says "Nobody has subscribed yet: people subscribe on your portal's changelog."
A reader turned off all your emails: if they turned on Email me nothing from your project in their Account settings, or unsubscribed from all of your project's emails, that wins, subscription or not. If they subscribe again, the email they get offers to turn your emails back on.
Your project's emails are paused: nothing is sent until they're resumed, then it goes. See When emails to your users wait or are paused.
Sample entries, from Add sample content, are never emailed.
Unsubscribe
Every changelog email has an Unsubscribe link. It opens a page on your portal with an Unsubscribe button, which ends the subscription at once. To get the changelog again, the reader subscribes on the changelog and confirms again. Signed-in readers can also turn off The changelog in their Account settings.