LifeRaft OSTM
← All add-ons

Virtual Platforms

RLX SL Groups

Virtual-platform group claiming, forum routing, group notices, and RLX group/forum mapping.

ProductionVersion 0.1.0
Product images coming soonA closer look at RLX SL Groups.

What it does

Features at a glance

  • Connects web admin, product data, and in-world Second Life business processes
  • Useful for merchants and estate operators that need support, delivery, and staff visibility
  • RLX SL Groups can be packaged as an optional upgrade, bundle component, or project-specific module
  • RLX SL Groups provides a focused Second Life capability for LifeRaft OS based on its manifest and documentation

Built for your workflow

Who it’s for

  • Virtual-platform creators and merchants managing their own web presence
  • Venue, service, and product teams connecting in-world work with a community portal

Setup and fit

Compatibility

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

Required add-ons

Optional connections

From setup to everyday use

A straightforward starting point

  1. Activate RLX SL Groups and review its add-on settings
  2. Configure the module settings and permissions
  3. Add the records, content, media, or rules this module manages

Before you choose

Common questions

What does RLX SL Groups do?

Virtual-platform group claiming, forum routing, group notices, and RLX group/forum mapping.

What does RLX SL Groups need to run?

RLX SL Groups requires rlx-sl-api alongside the LifeRaft OS core. Other related add-ons are package suggestions unless their manifests also list a requirement.

How ready is RLX SL Groups 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.

Which other add-ons are required?

RLX SL Groups lists rlx-sl-api as required dependencies. Check their availability and licenses when planning the build.

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.
  • Virtual platform QA — Test endpoint URLs, connector scripts, owner permissions, delivery/recovery, and in-world object state.
  • Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.

Make RLX SL Groups part of your build.

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

Let’s talk