LifeRaft OSTM
← All add-ons

Community

RLX Newsletter

Newsletter subscriptions, member notices, waitlist audience reuse, queued email campaigns, and admin send tracking.

ProductionVersion 1.0.0
Product images coming soonA closer look at RLX Newsletter.

What it does

Features at a glance

  • Subscriber records with status, email, display name, user association, and source tracking
  • Turns scattered community information into managed pages and repeatable content flows
  • Gives owners a stronger reason to keep members inside the RLX site
  • Public newsletter subscribe route. Subscriber records with status, email, display name, user association, and source tracking. Campaign records for subject/body/status and send tracking. Admin subscriber actions

Built for your workflow

Who it’s for

  • Community owners organizing member participation
  • Creators and teams adding focused social workflows

Setup and fit

Compatibility

Requires a valid LifeRaft OS core license and a supported installation.

No additional add-on is listed as a required dependency.

From setup to everyday use

A straightforward starting point

  1. Activate rlx-newsletter
  2. Configure newsletter copy and sender behavior in add-on settings
  3. Collect subscribers from the public newsletter route

Before you choose

Common questions

What does RLX Newsletter do?

Newsletter subscriptions, member notices, waitlist audience reuse, queued email campaigns, and admin send tracking.

What does RLX Newsletter need to run?

RLX Newsletter runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.

How ready is RLX Newsletter for deployment?

Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.

Review the launch checklist
  • Admin setup — Confirm settings, navigation placement, permissions, and any required starter content before launch.
  • Public QA — Review the public page, empty states, mobile layout, and activated/deactivated states.
  • Package QA — Confirm the module fits the selected product package and does not expose unused workflows.
  • Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.

Make RLX Newsletter part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk