RLX Social Actions

Extracted ownership for reactions, bookmarks, saved posts, and thread, forum, and category watches with core compatibility wrappers.

Community builds that need RLX Social Actions without forcing it into every install.

RLX Social Actions can run as its own Community 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 Social Actions 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 Notifications, RLX Activity, RLX Analytics, RLX Support, and RLX Newsletter, RLX Social Actions 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 Social Actions commonly pairs with RLX Notifications, RLX Activity, RLX Analytics, RLX Support, RLX Newsletter. Active pairings depend on the package, customer workflow, and installed add-ons.

RLX Social Actions should be launched with its real data model and public routes in mind. Optional integrations: rlx-notifications, rlx-activity, rlx-analytics.

RLX Social Actions has a $44.85 Everyday 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.

Each action behaves as a simple toggle: members can add or remove it from the content they are allowed to view. Existing forum permissions remain authoritative, so saving or watching an item does not grant access to restricted content. Administrators receive an aggregate activity view for understanding adoption without changing members' choices.

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.