LifeRaft OSTM
← All add-ons

Operations

RLX NDA

NDA, beta agreement, contributor agreement, and private-access document gates for LifeRaft OS.

ProductionVersion 1.0.0
Product images coming soonA closer look at RLX NDA.

What it does

Features at a glance

  • Public agreement index and agreement detail pages
  • Accept route with CSRF protection and versioned acceptance ledger
  • Admin document manager with Markdown editor
  • Assignment manager for route, role, addon, section, product, resource, waitlist, form, support, team, brand, staff, and funnel/custom contexts
  • JSON export/import for documents and assignment rules
  • Helper functions for other add-ons: pending checks, context checks, acceptance checks, and gate callout HTML

Built for your workflow

Who it’s for

  • Teams replacing scattered records with a shared operational workflow
  • Administrators responsible for day-to-day coordination

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. Activate rlx-nda and review its add-on settings
  2. Create agreement documents in Markdown from Admin > RLX NDA
  3. Create assignment rules for standalone pages, routes, roles, addons, funnels, sections, products, downloads, or custom contexts

Before you choose

Common questions

What does RLX NDA do?

NDA, beta agreement, contributor agreement, and private-access document gates for LifeRaft OS.

What does RLX NDA need to run?

RLX NDA 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 NDA 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.
  • Data QA — Check exports, filtering, retention, audit visibility, and staff-only permissions.
  • Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.

Make RLX NDA part of your build.

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

Let’s talk