LifeRaft OSTM
← All add-ons

Community

RLX Teams

Organizational team directory pages, member assignments, team profiles, tabs, public member detail pages, and explicit links to separate community Groups.

ProductionVersion 0.3.0
Product images coming soonA closer look at RLX Teams.

What it does

Features at a glance

  • Public teams directory
  • Team detail pages with summary, description, cover, icon, contact URL, visibility, status, and tabbed content
  • Team member records linked to users
  • Member title, role label, bio, expertise, avatar, links, lead flag, active state, and sort order

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.

From setup to everyday use

A straightforward starting point

  1. Activate rlx-teams
  2. Create team profiles with public summaries and Markdown descriptions
  3. Add members to teams and define roles, bios, expertise, and links

Before you choose

Common questions

What does RLX Teams do?

Organizational team directory pages, member assignments, team profiles, tabs, public member detail pages, and explicit links to separate community Groups.

What does RLX Teams need to run?

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

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

Let’s talk