LifeRaft OSTM
← All add-ons

Community & Site Tools

RLX Disclaimer

Reusable project disclaimer blocks for forum-tab footers, site footers, and compatible widget regions, with optional pages or modal details.

PreviewVersion 0.1.1

This add-on is in the preview stage. Ask about its current scope and availability before planning your build.

Product images coming soonA closer look at RLX Disclaimer.

What it does

Features at a glance

  • Reusable project disclaimer blocks for forum-tab footers, site footers, and compatible widget regions, with optional pages or modal details

Built for your workflow

Who it’s for

  • Community & Site Tools projects that need this focused capability
  • Owners who want to activate only the workflows their site needs

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 Disclaimer and review its add-on settings
  2. Reusable project disclaimer blocks for forum-tab footers, site footers, and compatible widget regions, with optional pages or modal details
  3. Add the records, content, media, or rules this module manages

Before you choose

Common questions

What does RLX Disclaimer do?

Reusable project disclaimer blocks for forum-tab footers, site footers, and compatible widget regions, with optional pages or modal details.

What does RLX Disclaimer need to run?

RLX Disclaimer 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 Disclaimer for deployment?

Preview module: available for evaluation and scoped deployments while runtime evidence and product polish continue to mature.

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 Disclaimer part of your build.

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

Let’s talk