Feature Modules

Range Warden uses a module system that lets administrators enable or disable major features. This keeps the interface clean — pages and functionality for disabled modules are completely hidden from the sidebar and unavailable via the API.

Required role: Admin

Navigate to Admin → Modules tab.

How modules work

Each module controls a set of related features. When a module is:

• Enabled — Its pages appear in the sidebar, its API endpoints are active, and users can access the features.
• Disabled — Its pages are hidden from the sidebar, its API endpoints return an error, and the features are inaccessible.

Modules can be toggled on and off at any time. Disabling a module does not delete any data — if you re-enable it later, everything is still there.

Available modules

Module	What it controls	Dependencies
Payments	Payment recording, refunds, Stripe integration	None
Range Ops	Lane management, range status controls	None
Check-In	Member and guest check-in/checkout	Requires Range Ops
RSO	RSO shifts, RSO portal, approval queue	Requires Check-In
RSO Scheduling	Monthly RSO shift calendar and preferences	Requires RSO
Training	Training course tracking and certifications	None
Kiosk	Self-service kiosk for members and guests	Requires Check-In
Email	Email template configuration and customization	None
Reports	Analytics dashboards and report generation	None

Module dependencies

Some modules depend on others. The dependency chain ensures that foundational features are active before features that build on them.

Dependency tree:

Payments (standalone)
Range Ops (standalone)
├── Check-In (requires Range Ops)
│   ├── RSO (requires Check-In)
│   │   └── RSO Scheduling (requires RSO)
│   └── Kiosk (requires Check-In)
Training (standalone)
Email (standalone)
Reports (standalone)

Enabling a module with dependencies

When you enable a module, its dependencies must already be enabled. For example:

• To enable Kiosk, you must first enable Check-In and Range Ops.
• To enable RSO Scheduling, you must first enable RSO, Check-In, and Range Ops.

The system will prevent you from enabling a module if its dependencies are disabled, and will show which modules need to be enabled first.

Disabling a module with dependents

When you disable a module, you cannot do so if another enabled module depends on it. For example:

• You cannot disable Range Ops while Check-In is enabled.
• You cannot disable Check-In while RSO or Kiosk is enabled.

The system will tell you which modules need to be disabled first.

Enabling a module

1. Navigate to Admin → Modules.
2. Find the module you want to enable.
3. Click the toggle to turn it On.
4. If the module has unmet dependencies, a message indicates which modules need to be enabled first.
5. Once enabled, the module’s pages immediately appear in the sidebar for users with the appropriate roles.

Disabling a module

1. Navigate to Admin → Modules.
2. Find the module you want to disable.
3. Click the toggle to turn it Off.
4. If another enabled module depends on this one, a message indicates which modules need to be disabled first.
5. Once disabled, the module’s pages are immediately hidden from the sidebar.

Note

Disabling a module does not delete any associated data. Check-in records, payment records, RSO shifts, and other data created while the module was active are preserved. Re-enable the module to access that data again.

Recommended configurations

Full-featured range

Enable all modules for a complete range management system:

• Payments, Range Ops, Check-In, RSO, RSO Scheduling, Training, Kiosk, Email, Reports

Membership-only club

For clubs that only need to track memberships and collect dues:

• Payments, Email, Reports

Range with RSO portal but no kiosk

For ranges where RSOs handle all check-ins (no self-service):

• Payments, Range Ops, Check-In, RSO, Email, Reports

Getting started (minimal)

Start with the basics and add features later:

• Payments, Email

You can enable additional modules as your needs grow.