LifeRaft OSTM
← All add-ons

Community

RLX Chat

App-style member chat with spaces, DMs, permission-aware entity channels, unread state, presence, message tools, reactions, pinned messages, and chat-to-thread/support/docs conversion.

ProductionVersion 1.6.0
Product images coming soonA closer look at RLX Chat.

What it does

Features at a glance

  • Admin-managed spaces and settings
  • Public member chat route with space navigation and live polling
  • Optional chat-native DMs using the same message tools as rooms
  • Edit, delete, pin, reaction, reply/thread preview, and conversion controls
  • Presence, typing, active member rail, and pinned message rail
  • Conversion actions for forum threads, RLX Support tickets, and RLX Knowledge Base drafts

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.

Optional connections

From setup to everyday use

A straightforward starting point

  1. Create spaces from Admin > Chat
  2. Enable DMs, member rail, and conversion settings from add-on settings as needed
  3. Keep only useful spaces active to avoid fragmenting discussion

Before you choose

Common questions

What does RLX Chat do?

App-style member chat with spaces, DMs, permission-aware entity channels, unread state, presence, message tools, reactions, pinned messages, and chat-to-thread/support/docs conversion.

What does RLX Chat need to run?

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

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

Let’s talk