Buttondown gives you two independent controls for keeping a newsletter private:
- Private mode controls who can subscribe to your newsletter.
- Archive visibility controls who can read your published issues on the web.
They're independent — you can turn either one on without touching the other, and they cover different use cases. The rest of this page walks through each in turn.
Private mode
By default, Buttondown newsletters allow public subscriptions. Anyone can sign up by visiting your newsletter's public page and completing the subscription form. To learn more about adding subscribers, read Building your subscriber base.
However, you may wish to keep your newsletter private. For example, if you're sending a newsletter to a small group of friends or colleagues, or if you're using Buttondown to send internal updates to your team at work, you probably don't want just anyone to be able to subscribe to it.
Enabling private mode
- Navigate to the Subscribing settings page.
- Click to enable the "Private mode" toggle. A warning appears.
- Click I understand and then click Save changes.
When private mode is enabled, your newsletter will not allow public subscriptions, even from a form endpoint. Instead, only subscribers you have added from the Buttondown dashboard or the API will receive your newsletter.
Private mode only affects subscription signups. Your web archive stays publicly visible unless you also change the archive visibility setting described below.
Archive visibility
The archive visibility setting lives on the Archives settings page and controls who can read your published issues on the web. It has four options:
- Public — anyone on the web can browse your archive. This is the default for new newsletters.
- Subscribers only — only confirmed subscribers can see your archive. Non-subscribers visiting an archive URL see a sign-in gate; they enter their email address and we send a magic link if their address is on your subscriber list.
- Paid subscribers only — only paid subscribers can see your archive.
- Disabled — the archive is turned off entirely. Visiting an archive URL returns 404.
Individual emails can override this newsletter-level setting on a per-email basis, so you can publish a single public issue from an otherwise subscriber-only archive (or vice versa).
Archive visibility only affects web reading. It has no effect on who can subscribe — that's what private mode is for.
Combining the two
Because private mode and archive visibility are independent, you can pick the combination that fits your use case:
- Closed community — private mode on, archive visibility "Subscribers only." Only invited subscribers can join, and only subscribers can read past issues.
- Invite-only audience, public back catalog — private mode on, archive visibility "Public." Existing content is browsable on the web (useful for sharing and SEO), but new subscribers have to be added by you.
- Open signups, gated back catalog — private mode off, archive visibility "Subscribers only." Anyone can subscribe, but only subscribers can read past issues.
- Fully public — private mode off, archive visibility "Public." The default for new newsletters.