Feature is in private Beta. Reach out to [email protected] for access.
How to restrict access to images and content on a private page?
You can ensure that images and content for Announcements and Roadmap Items on your private LaunchNotes page are not publicly accessible on the internet by enabling Secure Content in your project's Authorization settings. Once on, images are served through LaunchNotes' authenticated pipeline instead of a public CDN — meaning no one can load them without an active signed-in session, even if they have the direct URL. Outbound email and Slack notifications are also trimmed to excerpt-only, with no full body content or embedded images included.
Set-up guide
Open your LaunchNotes workspace and navigate to the project you want to secure.
Go to Authorization (You must be an Admin to have access).
Find the Secure content card.
Flip the toggle on and confirm when prompted.
Allow a few minutes for the changes to propagate across your project.
Considerations
Secure Content is only available on private projects — pages that already require JWT, SSO, or SAML authentication to view. The toggle will be disabled if your page is public.
Your subscribers' on-page experience is unchanged. Once signed in, the page looks and loads exactly as it does today.
Email and Slack notifications will become Excerpt-only. Full body content and embedded images will be removed, and hero images will be replaced with a placeholder. A "Read more" link will drive recipients back to your LaunchNotes page to view the full Announcement.
Images cannot be added to Digests while Secure Content is on. Digests don't have an Excerpt-only. You'll see a tooltip if you attempt to insert one.
Loom and Vidyard embed URLs in an Announcement Hero Section are not excluded from notifications and are not secured by this feature.
Troubleshooting
If the Secure content in announcements on the Authorization page toggle does not appear or is grayed out, confirm that your project has page security enabled (JWT, SSO, or SAML). Secure Content cannot be activated on public projects.
If images still appear to load without authentication shortly after enabling, allow a few additional minutes for propagation to complete.
If notification formatting looks unexpected after enabling, confirm that your email and Slack templates are set up to handle excerpt-only content — full body content will no longer be included.
Contact LaunchNotes support if issues persist: [email protected]
Frequently asked questions
Does it work on public pages?
No. Secure Content is only available on projects that already require a sign-in (JWT, SSO, or SAML). The toggle is disabled on public pages — there's nothing for it to gate.
Will my subscribers notice anything different on the page?
No. Once they're signed in, the page looks and loads identically. They won't see a banner, a different URL, or a different image experience.
Why can't I add images to a Digest when Secure Content is on?
Digests are sent as full email content — there's no "excerpt-only" version of a digest. Allowing images would mean those images go out in the email, which defeats the point of Secure Content. Until we have a digest-excerpt mode, the safer choice is to prevent images from being added.
Why are hero images replaced with a placeholder in emails?
Emails are rendered in the recipient's mail client, with no LaunchNotes session. If we sent the real hero image URL, it would either fail to load (broken image icon) or, worse, succeed and leak. The placeholder gives the email a clean, intentional look while keeping the actual image private.
What about embed widgets?
Embedded media follows the same access rules as the page. If your embed is on a private project, viewers must be signed in for images to load. The exact behavior depends on how your embed authenticates viewers — reach out if you're embedding on a third-party site and want us to walk through your setup.
Is there a performance impact?
Minimal. Image requests now go through LaunchNotes instead of a CDN, which adds a small amount of latency on first load. For most pages this is not noticeable.