RLX Automation

When/then automation rules for forms, support, roadmap, alerts, webhooks, group changes, and audit logs.

Admin-managed content and settings. Public pages with clean presentation. Designed to run as an optional RLX module.

RLX Automation can run as its own Core Extensions workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.

No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Automation should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.

When the customer also owns and activates related modules such as RLX Pages & CMS, RLX Blog, RLX Wiki, RLX FAQ, and RLX Knowledge Base, RLX Automation can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.

RLX Automation commonly pairs with RLX Pages & CMS, RLX Blog, RLX Wiki, RLX FAQ, RLX Knowledge Base. Active pairings depend on the package, customer workflow, and installed add-ons.

RLX Automation should be launched with its real data model and public routes in mind. Routes: RLX Automation is exposed through the routes registered by its add-on entry file when the module is active. During, launch, teams should confirm the public page, admin entry point, empty states, permissions, and navigation placement, match the package being sold. Add screenshots of public pages, admin controls, member workflows, moderation options, and example content types Include a short scenario showing how RLX Automation helps a community owner reduce support load or publish cleaner

RLX Automation has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.

Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.

Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.

Activate RLX Automation and review its add-on settings. Configure the module settings and permissions. Add the records, content, media, or rules this module manages. Review public pages and backend empty states before launch.

No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.