Admin - Subscriber Management

⚡ Quick Actions

Templates

Manage reusable templates here. This includes trip templates and full site-package templates that can be prepared for individual groups.

Ryder Cup 5 round template

Uses the Myrtle Ryder Cup structure: 5 rounds, seeded team matches, side games, payouts, and the existing Myrtle trip, standings, and prize pages, with roster sizes starting at 12 golfers and staying in groups of 4.

Download Template Guide

Answer these setup questions before the trip is created.

What should the trip be called?
Where is the trip being played, and what group or organizer name should show on it?
What date does round 1 start, and what are the five course names?
What are the two Ryder Cup team names?
What should the first tee time be, and how many minutes apart should each foursome go off?
What package, reservation, coordinator, and contact phone details should be saved?
Who are the seeded players in order, and what handicap index should each seed start with? Use at least 12 golfers, in groups of 4.

Trip Name Group Name Location Round 1 Start Date Team A Name Team B Name First Tee Time Foursomes Per Round Minutes Between Tee Times Package Type Reservation Number Prepared By Contact Phone

Round 1 Course Round 2 Course Round 3 Course Round 4 Course Round 5 Course

Seeded Roster (12+ lines, seed order 1-N, total golfers must stay divisible by 4) Handicap Indexes (same order as roster)

Group tee-times deployment template

Deploys a dedicated group profile on the shared tee-times stack, then downloads the package spec, guide, and minimal-admin starter artifact for that group.

Download Deployment Guide

Answer these setup questions before the group is deployed and the package files are generated.

This now creates a live shared-stack deployment under a dedicated group slug, with separate public, admin, minimal-admin, calendar, inbound-email alias, and scoped admin/delete codes. A separate database/env per group is still the lower-risk option if you want hard isolation.

What should the site be called for this group?
What short app name, group name, group reference, and group URL slug should be used?
What primary/secondary emails, reply-to email, club-request email, phones, icon, and theme color should ship in the package profile?
Which optional modules should be included beyond the core tee-times and admin pages?
Any deployment or branding notes that should stay with the package?

Site Title Short App Title Group Name Group Reference Group / URL Slug Club Name Club Request Button Label Primary Contact Email Club Request Email Secondary Contact Email Reply-To Email Support Phone Club Phone SMS / Text Phone Theme Color Icon Asset Name Mongo DB Name Group Admin Code Group Delete Code Delete Confirm Code Inbound Email Alias

Include handicaps pages Include trip systems Include outings system Include notifications Include scheduler rules Include backups

Admin Alert Phones Deployment Notes

Golf Group References

Use these labels when asking for tee-time updates. This keeps the main site and separate group deployments clearly identified.

Loading golf groups...

Site Inventory

One place to see the different site areas, page groups, and reusable templates that exist in the current projects. Use this as the admin-page directory for what systems are live and where each one is managed.

Loading catalog...

Backups

Create a recovery bundle with the primary database, secondary database, and a site snapshot. Run this before major changes and at least monthly.

Monthly Backup Schedule

Uses the existing scheduler. On the configured day/time it creates a full backup bundle and then trims older backups by retention count.

Loading...

Weekly Backup Schedule

Adds a weekly full backup in addition to monthly retention coverage.

Loading...

Daily Backup During Active Trip Season

Runs daily only within the selected season window.

Loading...

Monthly Day Hour Minute Keep Backups Weekly Day Weekly Hour Weekly Minute Daily Hour Daily Minute Season Start Month Season End Month

Off-Machine Copy Policy

Track whether backups are also copied somewhere outside this server.

Loading...

Off-Machine Location / Process

Restore Databases

Restore the primary DB, secondary DB, or both from a selected backup. This replaces live data. The confirmation id must exactly match the selected backup.

Backup Target Confirm Backup ID Delete / Restore Code Destructive Confirm Secret

🔔 Global Notification Settings

Event Notifications

Send email notifications for all event changes (new events, player sign-ups, etc.)

Loading...

Subscriber Change Emails

Send subscriber emails for immediate event and tee-time changes such as new events, cancellations, sign-ups, removals, and added tee times.

Loading...

Automated Scheduler

Runs timed jobs (4 PM empty-tee club alert, 5 PM reminders, admin checks, and weather refresh).

Loading...

📬 Scheduled Email Rules

Toggle each scheduled email rule independently. These only apply to automated scheduler runs.

4 PM Club Alert (Tomorrow Empty Tees)

Sends the configured club contact an alert at 4:00 PM if tomorrow has empty tee times.

Loading...

5 PM Reminder (48 Hours)

Sends subscriber reminder emails for empty tee times 2 days out.

Loading...

5 PM Reminder (24 Hours)

Sends subscriber reminder emails for empty tee times tomorrow.

Loading...

5 PM Nearly-Full Alert

Sends subscriber alerts when tee times are over 50% full within 4 days.

Loading...

Admin Empty-Tee Alerts (6 Hour Cycle)

Sends admin alerts every 6 hours for 24hr/48hr empty tee times.

Loading...

📝 Tee-Time Change Log

See recent adds, edits, and deletes (including club notify attempts).

Inbound Tee-Time Email Log

See the tee-time details captured from incoming reservation emails.

👥 Subscriber Management

This page manages the BRS Group subscriber list only. The same email address can also be subscribed to Seniors or any other group separately.

Total Subscribers

-

Loading subscribers...