Admin Guide

How to use each management page — fields, workflows, and notifications

Overview

Tally Manager lets you create and manage tally activities — the activities that tribes submit points for. Each activity has a name, category, and one or more point tiers that define how points are awarded.

This page also has a Submission Reports tab where you can review all tally point submissions, edit individual entries, and see total points by tribe.

Permission required: tallyManager or admin role.

Activities Tab — Creating & Editing Activities

FieldRequiredWhat It Does
Activity NameYesThe name displayed on the public submission form and in reports. Example: "Camping Trip", "Community Service", "Cooking Competition".
CategoryYesGroups activities in the submission form. You type a category name; it auto-completes from existing categories. Example: "Camping", "Service", "Cooking". Activities in the same category appear together on the form.
Tier Dropdown HeadingNoThe label shown above the tier selector on the public form. This tells the submitter what the tiers represent. Example: if your tiers are "1 Night", "2 Nights", "3+ Nights" — set this to "How Many Nights?"
Sort OrderNoControls display order within a category (lower number = appears first). Defaults to 999. Use this to put the most common activities at the top.
NoteNoOptional note displayed next to the activity on the submission form. Good for clarifications or rules. Example: "Must attend full day to qualify."
Point TiersAt least 1A table of tiers, each with a label and a point value. These create the dropdown on the submission form. See examples below.
Limit one submission per placement per event (toggle)NoWhen ON, each tier (e.g. "1st Place") can only be claimed once per event — good for competitions where there's only one winner. Participation-style tiers are always unlimited. Leave OFF for activities anyone can earn (attendance, service hours, etc.).
๐Ÿ† Award (per-tier checkbox)NoEach tier row in the Point Tiers table has its own "๐Ÿ† Award" checkbox. When a tier is checked, a tally submission for that specific tier also creates a row in the public Awards table — the tribe + recipient appear on the Awards page, the Tribes showcase, and the Chief Portal Awards section. Check it on placement tiers only (1st/2nd/3rd Place, Champion); leave it unchecked on participation/attendance tiers so routine point-earning doesn't clutter the awards list. Example: a "Derby Car" activity would check the box on 1st/2nd/3rd Place but NOT on "Participation". Only NEW submissions are affected when you change a checkbox — existing submissions aren't retroactively converted.

When a submitter picks an award-tier on the public tally form, they're also asked "Who Won? (Recipient)" — a dropdown of the tribe's Primary members (the same roster used by the registration form). The picked dad becomes the award's recipient and the award hard-links to his site account, driving the Our Awards tab in his Member Portal. Sons usually win, but the award attaches to the dad (the account holder); the son's name can go in the Event Details / Comments field.

Understanding Point Tiers

Tiers are the core of how points are awarded. When a tribe submits this activity, they select a tier from a dropdown, and the corresponding points are added to their total.

Example 1 — Simple Activity (One Tier)

Activity: Attended Meeting
Category: Participation
Tier Heading: (leave blank — only one option)

Tier LabelPoints
Attended5

On the submission form, the submitter sees "Attended Meeting" and the single option "Attended" for 5 points.

Example 2 — Tiered by Distance

Activity: Hiking
Category: Camping
Tier Heading: Select Distance

Tier LabelPoints
Under 3 Miles5
3 – 5 Miles10
5+ Miles15

On the form: the submitter picks "Hiking", then sees a dropdown headed "Select Distance" with the three options.

Example 3 — Tiered by Overnight Stays

Activity: Camping Trip
Category: Camping
Tier Heading: How Many Nights?

Tier LabelPoints
1 Night10
2 Nights20
3+ Nights30
Example 4 — Penalty / Deduction

Activity: Late Arrival
Category: Deductions
Tier Heading: How Late?
Note: Points are deducted. Arrive on time!

Tier LabelPoints
15–30 min late-5
30+ min late-10

Negative point values are allowed. The points range will show as −10 – −5 pts in the activity list.

Example 5 — Cooking Competition with Placement

Activity: Burger Challenge
Category: Cooking
Tier Heading: Placement
Sort Order: 1 (puts it at top of Cooking category)

Tier LabelPoints
1st Place25
2nd Place15
3rd Place10
Participated5
Tips
  • Use Sort Order to control which activities appear first in their category on the submission form.
  • The "+ Add Tier" button adds a new tier row. You can remove any tier with the "× Remove" button.
  • If an activity only has one possible point value (like "Attended Meeting" = 5 pts), you only need one tier row.
  • Negative points work for deductions — just enter a negative number in the Points field.

Submission Reports Tab

Two reports are available:

Report 1: Total Points Summary

The default view — an aggregated leaderboard showing total points per tribe, ranked highest to lowest, with submission count per tribe and a grand total. Click any tribe row to jump straight to that tribe's full breakdown in Report 2. Download or email a CSV of the summary.

Report 2: Tribe Details

Shows every individual tally submission, grouped by tribe. Each row shows who submitted, what activity, which tier they selected, points earned, and any details. You can Edit or Delete individual submissions inline. Download or email a CSV of the full report.

Notifications

Email / SMS Notifications

Tally Manager itself sends no emails when activities are created, edited, or deleted.

However, tally submissions (made on the public form) now do send email: the submitter gets a confirmation email (if they provided an address) and chief@tetonnation.com gets an admin notification listing the tribe, submitter, total points, and line items.

Overview

Event Manager is where you create, edit, cancel, and reinstate events. It has three top-level tabs: Events, Registrations, and Notifications. Events appear on the public calendar, upcoming events widget, and home page registration bar.

Permission required: eventManager or admin role.

Events Tab — Event Form Fields

FieldRequiredWhat It Does
Year, Month, Day StartYesWhen the event starts. These drive calendar placement and the "upcoming events" widget.
Day EndNoFor multi-day events (e.g., a campout from the 15th to the 17th). Leave as "None" for single-day events.
Event TitleYesAuto-title-cased on save. Displayed everywhere: calendar, registration page, home bar.
Event TypeYesCampout, Social, Service, Fundraiser, or Other. Used for filtering in the calendar.
Start Time / End TimeNoShown on the registration page, in confirmation emails, and in the ICS calendar invite attachment. Uses 24-hour format (HH:MM).
Location / AddressNoShown on the registration page as a clickable Google Maps link.
Flyer / Flyer 2NoUpload an image or paste a URL. Flyers are shown on the public events calendar page. Two flyers can be displayed side-by-side.
Registration TypeNoNo Registration = info-only event. Internal = registration via this site. External = link to a 3rd-party registration page (shows URL and URL Label fields).
Entry FeeNoDollar amount. Set to $0 for free events. Shown on the registration form.
Registration URL / LabelNoOnly shown when Registration Type = "External". The URL is linked on the calendar; the label is the button text (e.g. "Register", "More Info").
Early Bird Deadline / NoteNoIf set, shows on the registration form (e.g., "$5 off before June 1"). Automatically shows as strikethrough after the deadline passes.
Registration is OpenNoToggle switch. When ON: the event shows in the home page registration bar (HomeBar) and the public registration form is accessible. When OFF: registration link is hidden.
Mark as DoneNoMarks the event as completed. Dims the event row in the list.

The event editor has inner tabs across the top: Event Details (the fields above) · ๐Ÿ“ Description · ๐Ÿ’ต Payment Details · Event Registrants · ๐Ÿ”” Notifications. The Payment Details tab is covered next.

๐Ÿ’ต Payment Details Tab — Paid Event Registration

For events with Registration Type = Internal, the Payment Details inner tab controls how attendees pay. When a fee is set, the public registration page collects payment by credit card through Elavon's secure lightbox — the card is entered in Elavon's own pop-up window, so card data never touches the Teton Nation site.

FieldWhat It Does
Pricing modeEither a single flat Entry Fee for everyone, OR per-person pricing (a Primary fee + a Secondary fee, e.g. adult vs. child). Per-person mode multiplies by the headcount the registrant selects.
Add-onsOptional extra line items (t-shirts, meals, etc.). Each add-on has a label, a price, and a pricing mode: fixed (a set price × quantity) or open / donation (the registrant types any amount). Add-ons appear on the registration form below the base fee.
Donation-Only eventsWhen enabled, the event accepts pure donations with no attendance — the registrant just picks a tribe and enters an amount. Useful for fundraiser events.
๐Ÿงช Payment Test Mode (toggle)Important. When OFF (normal): the registration page runs the real Elavon payment — a real card is charged. When ON: the page shows a "Simulate Payment" button instead and completes the registration without charging anything. Use Test Mode ON to rehearse the registration flow or train volunteers; switch it OFF before the event goes live so real payments are collected. The toggle is per-event — each event remembers its own setting.

What the registrant sees

On a paid event, the registration page walks the attendee through their info, then a Pay button opens the Elavon card window. On success, the registration is saved and a confirmation email is sent that includes a Payment Receipt block (amount charged, transaction ID, authorization code, date) so they have a record for their files. Free events ($0) and Test Mode events skip the card window entirely.

Registrations Sub-Tab (within Event Editor)

When editing an existing event, a Registrations sub-tab appears inside the editor (requires eventRegManager or admin permission). This gives you a quick view of who has registered without leaving the event editor.

  • Inline edit — click a row to edit registration details (family name, contact, tribe, attendees, payment).
  • Delete — remove individual registrations.
  • CSV Download — export all registrations for the event as a CSV file.
  • Email List — send a formatted registrant list with CSV attachment to any email addresses you specify.

Cancel / Reinstate Events

These are special actions at the bottom of the edit form for an existing event.

Cancelling an Event

  1. Toggle "Cancel This Event" — a warning section appears.
  2. Write a Cancellation Message (this is sent to all registrants who have an email on file).
  3. The system shows how many registrants will receive the email.
  4. Click "Confirm Event Cancellation & Send Emails".
Important

Cancelling immediately updates the event status — you do not need to also click "Save Event". The cancellation email is sent to all registrants with an email address via Resend.

Reinstating a Cancelled Event

  1. Toggle "Reinstate This Event".
  2. Optionally write a Reinstatement Message.
  3. Click "Confirm Reinstatement".

If you leave the message blank, the event is reinstated silently (no email sent).

Reminders Section (within Event Editor)

Each event can have up to two email reminders and two SMS reminders configured. Set these in the Reminders section at the bottom of the event editor.

  • Email Reminder 1 / 2 — choose how many days before the event to send (e.g., 7 days before, 3 days before). A live hint shows the computed send date, or a warning if the date is already in the past.
  • SMS Reminder 1 / 2 — same as email, with a time picker. Shown greyed out with a "Coming Soon" badge — SMS via Twilio is pending credential setup.

When the event is saved, the system automatically queues reminder emails for all current registrants at the configured date/time (9:00 AM EDT). New registrants added later are also picked up when the queue processes.

Reminder Delivery

Reminders are delivered by the notification queue, which processes every 30 minutes. The reminder email includes event details and an upcoming events block.

Notifications Tab (top-level)

The Notifications top-level tab lets you send ad-hoc event update emails to all registrants for any event. This is the same template system available in the Notification Manager.

Available Templates

  • Time Change — announces a new start/end time. Attaches an updated .ics calendar invite.
  • Date Change — announces a new date. Attaches an updated .ics invite.
  • Location Change — announces a new venue. Attaches an updated .ics invite.
  • Cancellation — event is cancelled (same as the Cancel button in the editor, but allows re-sending).
  • Reinstatement — event is back on.
  • Thank You — post-event mass email; include an optional personal message and up to two upcoming events.
  • Custom — fully custom subject and body for any other update.

Workflow

  1. Select an event from the dropdown (shows events from last 3 months through future).
  2. Choose a template.
  3. Edit the pre-filled subject line if needed.
  4. Edit the message body in the live preview area.
  5. Optionally send a test email to yourself first.
  6. Choose Send Now or Schedule (pick a date/time).
  7. If recipient count > 90, a stagger warning is shown — the send is queued to the notification_queue table for rate-limited delivery.

Notifications

Emails Sent From This Page
  • Cancel Event: Sends cancellation email to ALL registrants with the custom message you write. Sent via Resend.
  • Reinstate Event: Sends reinstatement email only if you include a message.
  • Notifications Tab: Sends the selected template to all registrants (immediately or scheduled).
  • Reminders on Save: Queues reminder emails for all current registrants at the configured days-before time.
  • Normal Save / Delete: No emails sent.

Overview

Event Reg Manager lets you view and manage registrations for all events. You can edit registration details, delete registrations, download CSV exports, email registrant lists, and manage external (NSD) registrations.

Permission required: eventRegManager or admin role.

Selecting an Event

Use the Active filter (card view of events with registration open) or the All filter (list view of past year through future). Each card/row shows the event title, date, number of registrations, and status. Click to view registrations.

Events from nationallonghouse.org (NSD / National Longhouse) are shown with an orange "NSD" badge. These come in via the email pipeline and are read-only — you cannot edit or delete NSD registrations from this page.

Internal Registrations

Internal registrations (submitted through this site) are fully editable. The registration table shows: #, Family, Tribe, Contact, Attendees, Payment, Registered date, and Actions.

Editing a Registration

FieldRequiredWhat It Does
Family NameYesPrimary identifier for this registration group.
Contact NameYesThe person who registered.
Email / PhoneNoContact info. Email is used for cancel/reinstate notifications.
Membership StatusNoDropdown: "Existing Member — Select My Tribe" or "Guest / Prospective Member". Controls which tribe field is shown.
TribeNoDropdown of all tribes. Shown when membership = Member.
Referred by a Tribe?NoShown when membership = Guest. Records which tribe referred this guest.
AttendeesNoDynamic rows: each row has a Name and Age. Click "+ Add Attendee" for more rows.
Payment MethodNoFree, Cash on Site, PayPal, Zelle, Other.
Payment StatusNoFree, Pending, Paid. Color-coded in the table (green = Paid, orange = Pending).

External Registrations (NSD)

Registrations from nationallonghouse.org arrive automatically via email pipeline (Gmail → Mailgun → Edge Function). They are shown in read-only mode with an orange "NSD" badge. You can view all registrant details but cannot edit or delete them from this page.

The Tribe column may be blank for newly arrived NSD registrations, since NSD registration emails do not include tribe/subgroup data.

Sync Tribes Button

The Sync Tribes button (🔄) fills in missing tribe data for NSD registrations by cross-referencing the NSD member roster. This runs a two-phase flow:

  1. Preview — the system fetches the NSD roster, matches names to NSD registrations, and shows you a list of planned tribe assignments. No changes are made yet.
  2. Confirm — after reviewing the planned updates, click Confirm. Matched registrations get their tribe filled in. A summary shows how many were matched and any names that could not be matched automatically.
Unmatched Names

Names that don't match (e.g., nickname vs. legal name) can be manually patched afterward. Contact the admin team for direct database edits, or use the manual tribe sync workflow described in the internal docs.

Export & Email

Download CSV

Exports all registrations for the selected event as a CSV file. Includes all fields: family name, contact, email, phone, tribe, members, ages, payment info, membership status, and registration date.

Email Registrant List

Opens a modal where you enter one or more email addresses (comma-separated). Sends a formatted registrant list with an Excel-compatible CSV attachment to those addresses.

Notifications

Emails Sent From This Page
  • Email Registrant List: Sends a formatted email with CSV attachment to the addresses you specify.
  • Edit / Delete Registration: No emails sent.
  • Sync Tribes: No emails sent.

Overview

Tournament Manager is the most feature-rich admin page. It has four tabs:

  • Manage Tournaments — create, edit, delete tournaments; view & manage registrations
  • Bracket Generator — generate single or double elimination brackets from registered teams
  • Active Tournaments — run live tournaments (click matches to set winners, auto-saves to cloud)
  • Saved Brackets — browse, edit teams, complete, or delete saved brackets

Permission required: tournamentManager or admin role.

Manage Tab — Tournament Form

FieldRequiredWhat It Does
CampoutYesLinks the tournament to a campout event. Dropdown auto-populated from campout-type events. You can type "Other (Impromptu)" for standalone tournaments.
Tournament NameYesE.g. "Cornhole Tournament", "Spades Tournament".
Game TypeYesThe type of game (e.g. "Cornhole", "Spades", "Dominoes").
Bracket TypeYesSingle Elimination = lose once, you're out. Double Elimination = teams must lose twice (has Winners and Losers brackets, Grand Final, and optional Reset match).
Date & TimeYesWhen the tournament takes place.
Hosting TribeNoWhich tribe is hosting. Shown on the public registration page.
Entry FeeYesDollar amount per team.
Max TeamsYesMaximum number of teams that can register. Default: 200.
DescriptionNoOptional details shown on the registration page.
Payment OptionsAt least 1Check at least one: Cash on Site, PayPal (enter email/link), Zelle (enter phone/email), Other (enter description).
Open for RegistrationNo"Yes — Open" or "No — Closed". When open, the tournament appears on the public registration page.

Manage Tab — Registrations Panel

Click "Regs" on any tournament row to open the registrations panel. Shows all registered teams with team name, tribe, contact info, and payment status. You can:

  • Edit — change team name, tribe, contact, members, payment status.
  • Delete — permanently remove the registration.

Bracket Generator Tab

  1. Select a Campout and Tournament from the dropdowns (only open tournaments appear).
  2. Pre-registered teams load automatically. You can Remove teams (exclude from bracket) or Add Walk-ins (teams registering on-site).
  3. Optionally change the Bracket Type (Single or Double Elimination).
  4. Click "Generate Bracket". The bracket is drawn with randomized seeding.
  5. Click "Save Bracket" to save to the cloud. After the first save, the bracket auto-syncs every 30 seconds.
  6. Shuffle re-randomizes seeding (same bracket, different matchups).
Walk-in Teams

Add walk-in teams using the form below the team summary. Click "Save Walk-ins to Sheet" to save them as registered teams (marked as walk-ins). They'll persist even if you regenerate the bracket later.

Regenerating

If a saved bracket already exists for the selected tournament, generating a new one will permanently delete the existing bracket(s). You'll be warned before this happens.

Active Tournaments Tab

Shows all tournaments with active (saved) brackets. Click "Open" to load a bracket and run the tournament live:

  • Click any match to select a winner. The winner advances automatically.
  • Use the Undo button on any match to clear a winner and re-pick.
  • Click "Edit Teams" to fix team names, tribes, or members mid-tournament.
  • When a champion is determined, the "Submit Result" section appears with champion and runner-up auto-filled.
  • Optionally paste a Tournament Photo link (Google Drive share links are auto-converted).
  • Click "Submit Tournament Result" to save to the results/history table.

Saved Brackets Tab

Three sub-tabs:

  • Browse — view and load saved brackets.
  • Edit Teams — select a bracket, then edit team names, tribes, and members. Saves back to cloud.
  • Manage — mark brackets as "Complete" (removes from active list) or delete them permanently.

Notifications

Emails Sent From This Page

None from the admin page directly. Confirmation emails for public tournament registrations are sent automatically via Resend when someone registers on the public registration form. To send update notifications (time change, venue change, cancellation) to registered teams, use the Notification Manager → Tournaments tab.

Deleting a Tournament

Cascade Delete

Deleting a tournament permanently removes the tournament and all associated data: all team registrations and all saved bracket states. This cannot be undone.

Overview

Tribe Manager has three tabs for managing the organization's tribes, awards, and leadership roster. Changes here flow to the public pages (Tribes, Awards, Leadership).

Permission required: tribeManager or admin role.

Chiefs Can Self-Edit

Tribe chiefs do not need tribeManager permission to update their own tribe profile. They can edit the tribe saying, chief photo, logo, and social links directly from the Chief Portal → Edit Tribe Profile tab. Only tribe renaming requires tribeManager or admin access here.

Tribes Tab

FieldRequiredWhat It Does
Tribe NameYesThe official tribe name. Shown across the entire site (registration forms, leaderboards, etc.). Only tribeManager / admin can rename tribes.
Tribal Saying / MottoNoDisplayed in quotes on the public tribe card.
Logo ImageNoUpload an image or paste a URL. Shown on the public Tribes page.
Chief First Name / Indian Name / PhotoNoInformation about the tribe's chief. Displayed on the tribe's public card.
Facebook / Instagram URLNoSocial media links displayed as icons on the tribe card.
Where Tribes Appear

Tribe names populate dropdowns across the site: Login (registration), Event Registration, Tournament Registration, Tally Submissions, and all manager pages that have tribe selectors.

Awards Tab

Awards are managed within Tribe Manager on the Awards tab — there is no separate Awards page for admins. Awards appear on the public Awards page and on each tribe's card on the Tribes page.

FieldRequiredWhat It Does
TribeYesWhich tribe receives the award.
Award TypeYesAnnual Award = org-wide, no campout. Social Event Award = tied to a campout. Custom Award = flexible. Controls whether the Campout field is shown.
Award NameYesE.g. "Tribe of the Year", "Best Burger Challenge". An icon is auto-assigned based on keywords (e.g. "cornhole" gets a corn emoji).
YearNoYear the award was given.
CampoutNoShown for Social Event / Custom types only.
NotesNoAdditional context.
IconNoAuto-assigned emoji. You can change it manually.

Leadership Tab

FieldRequiredWhat It Does
NameYesFull name of the leader.
Indian NameNoDisplayed alongside the name on the public page.
Sort OrderNoControls display order on the public Leadership page. Lower = first (e.g., Chief of Nations = 1).
TitleYesE.g. "Chief of Nations", "Secretary", "Treasurer".
TribeNoOptional tribe association.
PhotoNoUpload or paste URL.
Bio / DescriptionNoShort description shown on the public Leadership page.

Notifications

Emails Sent From This Page

None. All Tribe Manager operations are saved directly to the database with no email triggers.

Overview

Expense Manager is a review/admin page for expenses submitted via the public Expense Submit page. You cannot create expenses here — only review, approve, reject, and track reimbursements.

Who can access this page:

  • expenseManager permission (or admin) — the super-user view. Sees and acts on every tribe's expenses. For national-level finance volunteers.
  • tribeWampum permission — the tribe treasurer. Sees and acts on only their own tribe's expenses.
  • tribeChief permission — the tribe chief gets the same tribe-scoped access, since chiefs sometimes handle reimbursements on the wampum's behalf.

See the "Tribe Roles: Chief vs Wampum" note in the User Manager tab for how these roles fit together.

Tribe-Scoped View (Wampum / Chief)

When a user signs in with a tribe-scoped role only (tribeWampum and/or tribeChief, but no expenseManager and not an admin), the page automatically scopes to their tribe:

  • A green banner at the top reads "Reviewing expenses for [Tribe] tribe".
  • The Tribe filter is pre-selected and locked to their tribe — they can't switch to another tribe.
  • Only their tribe's expenses load at all (enforced server-side, not just hidden in the UI).

A user who also has expenseManager (e.g. a chief who does national finance) gets the full all-tribes view — the broader permission wins.

Status Workflow

An expense moves through three states: PendingApproved or Rejected.

"Approved" means reviewed AND reimbursed. In this organization the wampum (or chief) reviews an expense and pays it out โ€” typically Zelle โ€” in one action. There's no separate "Reimbursed" status; approving the expense IS the record that it was handled and paid.

The edit panel also has optional Reimbursed By / Reimbursed Amount / Reimbursed Date fields for bookkeeping detail (who sent the money, exact amount paid, date) — useful when the reimbursed amount differs from what was requested, but not required.

Filters & Summary

Filter by Campout, Tribe, or Status (Pending, Approved, Rejected). A separate Group by dropdown (Campout / Submitter) reorganizes whatever the filters leave — see "Grouping the list" below. Summary cards at the top show expense count, total amount, Pending Review total, and Approved / Reimbursed total. (Scoped Wampum/Chief users have the Tribe filter locked — see above.)

Exporting

Two buttons next to the filters export whatever the filters currently leave (grouping is visual only and does not change the export):

  • โฌ‡ Excel / CSV — downloads a CSV file (opens in Excel / Numbers / Google Sheets) with a summary header plus one row per expense line item.
  • โœ‰ Email Report — opens a dialog to email that same CSV as an attachment, along with an HTML summary table in the message body, to any address you enter.

Expense Table

Expenses are grouped by submission batch (all items submitted together share a batch ID). The group header shows the campout, tribe, submitter, item count, total, and aggregate status. Click a group to expand individual line items. Click any row to open the edit panel.

Grouping the list

The Group by dropdown adds a layer of section headers above the submissions:

  • No Grouping (default) — one flat list of submissions, newest first.
  • Group by Campout — submissions are bucketed under a header for each campout.
  • Group by Submitter — bucketed under a header for each person who submitted.

Each section header shows that section's expense count, total, and how much is still pending — useful for "what did this campout cost the tribe" or "what do we still owe this person." Click a section header to collapse or expand everything in it. Grouping runs after the filters, so you can (for example) filter to Pending only, then group by Submitter to see who is owed what.

Changing status from the list

You don't have to open the edit panel just to approve something. The Status column is a dropdown right in the list:

  • On a group header โ€” changing the status sets every item in that submission at once. This is the fast path: a wampum can approve a whole expense report in one click.
  • On an individual item row โ€” changes just that one line item.

The change saves immediately. Open the edit panel only when you want to add the optional Reimbursed By / Amount / Date detail or admin notes.

Deleting an expense from the list

There are two delete buttons, both marked and both with a confirmation dialog:

  • On an individual item row (next to the receipt link) — permanently removes that single expense.
  • On a group header (next to the ▼ expand toggle) — permanently removes the entire submission, every line item at once.

Use delete for junk or duplicate submissions; for a legitimate-but-denied expense, set the status to Rejected instead (that keeps the record). Wampum and Chief users can delete expenses for their own tribe; admins / Expense Managers can delete any.

Edit Panel

FieldWhat It Does
StatusChange to Pending, Approved, or Rejected. "Approved" means reviewed & reimbursed (see Status Workflow above). This is the primary workflow action.
Reimbursed By (optional)Name of the person who handled the reimbursement.
Reimbursed Amount (optional)Dollar amount actually reimbursed (may differ from requested amount).
Reimbursed Date (optional)Date the reimbursement was made.
Admin NotesInternal notes — not visible to the submitter.

The panel also shows read-only info: campout, tribe, submitter name, email, category, description, amount, receipt link (click to view), and submission date. Receipts are stored in a private bucket; the link generates a temporary signed URL on click.

Typical Workflow

  1. Someone submits an expense on the public /expense-submit page with receipt(s).
  2. It appears here as Pending.
  3. The wampum (or chief) reviews the expense and receipt, then pays it out (Zelle, etc.).
  4. Change status to Approved โ€” that records it as reviewed & reimbursed. Optionally fill in the Reimbursed By / Amount / Date fields for bookkeeping. If the expense isn't valid, change status to Rejected instead.

Notifications

Emails Sent From This Page

None directly from the UI. Currently no automatic emails are sent when you approve, reject, or reimburse an expense.

Overview

Reports is the analytics dashboard for event and tournament data. It has five tabs: Event Registration Details, Tournaments, Event Overview, Tribe Roster, and ๐Ÿน Break Arrow Reqs.

Permission required: reports or admin role.

Event Registration Details Tab

Select any event from the dropdown to view its full registration analytics. Works for both internal events and external/NSD events from nationallonghouse.org.

Stat Cards

At the top: total registrations, total attendees. For external (NSD) events: total revenue (sum of family transaction charges).

๐Ÿน Break Arrow card — if the selected event has any Break Arrow requests, an additional gold-bordered stat card appears with the total count and per-tribe breakdown. Clicking the card (or any tribe row) jumps to the ๐Ÿน Break Arrow Reqs tab pre-filtered to that event.

Charts

  • By Tribe (center) — horizontal bar chart showing number of registrations per tribe. Gives a quick read of which tribes have the most participation.
  • Add-ons Sold (left) — bar chart of add-on items sold for events that have them (e.g., raffle bundles, meal upgrades). Only shown when the event has add-on data.
  • Registrations Over Time (right) — line chart showing cumulative registrations by day from the first registration through the event date.

Registrant Table

Full list of registrants below the charts. Includes filters for tribe, payment status, etc. Sortable columns.

Export Options

  • Download CSV — exports the full registrant list as a CSV file.
  • Email Registrant List — sends the list with CSV attachment to addresses you specify.

Add-ons Detailed Report

The Detailed Report button (📋) in the Add-ons Sold card opens a modal showing a per-purchaser breakdown: who bought which add-ons and how many. This modal has its own Download CSV and Email buttons for sharing the add-on breakdown separately.

Tournaments Tab

Select a tournament from the dropdown to view its registrations and results. Shows registered teams, tribe breakdown, payment status summary, and the final result (champion, runner-up) if the tournament has been completed.

Event Overview Tab

Cross-event analytics: attendance trends across all events, revenue over time, tribe participation summary across the full year. Useful for year-end reporting and planning.

Tribe Roster Tab

Live Primary-member roster for any tribe pulled directly from the NSD/ClubExpress API. Pick a tribe from the dropdown to load the family list grouped by household.

  • Download CSV — flat Tribe/Chief/Member Name list with summary header row.
  • Email Roster — sends the roster to addresses you specify (reuses the email modal).

๐Ÿน Break Arrow Reqs Tab

View, edit, and manage Break Arrow requests submitted by all chiefs across all tribes.

Filters

  • Event filter — All Events or a specific event.
  • Status filter — All Statuses, Pending, or Complete.

Stats Bar

Above the table: total request count, total sons across all selected requests, plus pending and complete counts colored orange and green.

Table Columns

Tribe, Submitted By (the chief who submitted), Dad, Son(s) with Indian names in italics, Event, Notes, Submitted date, Status badge, Actions.

Actions

  • โœ“ Complete — one-click button on pending rows to mark as complete.
  • โœ๏ธ Edit — opens the inline edit panel where you can change Dad, Sons (comma-separated), Indian Names (comma-separated, same order), Event, Notes, and Status.
  • ๐Ÿ—‘ Delete — permanently removes the request.

Export

  • โฌ‡ CSV — downloads the currently filtered list with all columns (incl. Indian Names).
  • โœ‰ Email — sends the CSV as an attachment to an email address you specify.

Notifications

Emails Sent From This Page
  • Email Registrant List / Email CSV: Sends the report data with CSV attachment to addresses you specify.
  • Email Roster (Tribe Roster tab): Sends the roster to specified addresses.
  • Email (Break Arrow Reqs tab): Sends the filtered Break Arrow report as a CSV attachment.
  • Mark Complete (Break Arrow): No email — status update only.
  • All other actions: No emails sent — Reports is read-only analytics.

Overview

Notification Manager is the central hub for sending bulk emails to members. It has three tabs: Events, Tournaments, and General Mass Email. All sends go through Resend with rate-limited delivery (max 90 emails per 30-minute batch) via the notification queue.

Permission required: notificationManager or admin role.

Events Tab

Send event update notifications to all registrants for any event. This is identical to the Notifications tab inside Event Manager, but accessible without opening a specific event editor.

How to Use

  1. Select an event from the dropdown (shows events from the last 3 months through future).
  2. Choose a template: Time Change, Date Change, Location Change, Cancellation, Reinstatement, Thank You, or Custom.
  3. Edit the pre-filled subject line if needed.
  4. Edit the message body in the live preview pane.
  5. Optionally send a test email to yourself first.
  6. Choose Send Now or Schedule (enter a date and time).
Stagger Warning

If the recipient count exceeds 90, a warning is displayed. The send will be queued to the notification_queue table and delivered in batches of up to 90 per 30 minutes to comply with Resend rate limits. Do not use "Send Now" for very large lists — schedule instead.

Templates That Attach .ics Files

Time Change, Date Change, and Location Change templates automatically attach an updated .ics calendar invite so recipients can update their calendars.

Tournaments Tab

Send tournament update notifications to all registered team members for any tournament.

How to Use

  1. Select a tournament from the dropdown.
  2. Choose a template: Time Change, Venue Change, Cancellation, or Custom.
  3. Edit subject and body as needed.
  4. Test, then send or schedule.

Recipients are all email addresses collected from tournament registrations (team members JSONB). The system de-duplicates before sending.

General Mass Email Tab

Compose a fully custom email to all members in the system. This is the broadest send available — use it for org-wide announcements, reminders, or newsletters.

Recipients

The recipient list is collected from all unique emails across: event registrations, tournament registrations (member fields), and member profiles. De-duplicated before queuing.

How to Use

  1. Enter a Subject for the email.
  2. Write the email body in the HTML textarea. Full HTML is supported (no salutation is added automatically — write your own opening).
  3. View the live preview to see how it will look, including the auto-appended upcoming events block.
  4. Send a test email to yourself to verify formatting.
  5. Send Now or Schedule the send.
Upcoming Events Block

All mass emails automatically include a live "Upcoming Events" section at the bottom (up to 3 open, non-cancelled future events). This is appended automatically — you do not need to add it yourself.

Large Recipient Lists

Mass emails to all members will almost certainly exceed 90 recipients. They are always queued to the notification_queue table and delivered in rate-limited batches. Do not attempt to "Send Now" for mass emails with large lists — schedule the send for a time when the queue can process it.

Notification Subscriptions

Notification Manager also manages CC subscriptions — additional email addresses that should receive copies of certain system emails (event registrations, cancellations, etc.). These are configured in User Manager per-user.

Overview

The Chief Portal gives tribe chiefs a focused view of their tribe's data without needing full admin access. It opens to a dashboard — an at-a-glance landing page — and you click into the area you want.

Permission required: tribeChief or admin role. Tribe chiefs automatically see only their own tribe's data. Admins can see all tribes.

The chief's tribe is auto-detected from their profile. The tribe name is shown italicized under the user name in the pill.

The Dashboard

When you open the Chief Portal you land on the dashboard. It's organized into two groups:

Viewing & Reporting

Three report cards, each showing a live preview and clickable to open the full view:

  • ๐Ÿ“‹ Event Registrations — preview shows your next upcoming event with a count of how many from your tribe have registered (and, for donation events, the dollars donated).
  • ๐Ÿ”ฅ Tally Points — preview shows your tribe's current-year point total and all-time total.
  • ๐Ÿ’ฐ Tribe Expenses — preview shows pending expense dollars awaiting review and approved totals.

Below the cards is a ๐Ÿ‘ฅ Tribe Roster strip — click it to open the full roster.

Manage & Submit

A toolbar of three action buttons: ๐Ÿน Submit Break Arrow Request, ๐Ÿ† Manage Awards & Honors, and โœ๏ธ Edit Tribe Profile.

Getting Back

Every screen you click into has a "โ† Back to Dashboard" banner at the top. Click it to return to the landing page.

๐Ÿ“‹ Event Registrations

View event registrations filtered to your tribe only. This is a read-only view — chiefs cannot edit or delete registrations from here.

Active Filter

Shows events with registration currently open, displayed as cards. Each card shows the event title, date, and how many of your tribe have registered. Click a card to see the tribe's registrant list for that event.

All Filter

Shows all events from the past year through future, as a list view. Useful for reviewing past participation or checking upcoming events your tribe hasn't registered for yet.

Tribe-Only View

Only registrations where the tribe field matches your tribe are shown. Guests or unaffiliated registrants are not included.

๐Ÿ‘ฅ Tribe Roster

Displays a live roster of your tribe pulled directly from the NSD website. Members are grouped into family units.

Family Grouping

  • Dad (Primary) — the primary NSD member (dues payer)
  • Spouse (Secondary) — the primary member's spouse/partner if listed
  • Children (Tertiary) — kids listed under the family membership

Only active members are shown (dues paid and background check cleared). The roster reflects the current NSD data as of the last fetch.

Refresh

Click the Refresh button to re-fetch the roster from the NSD website. The page shows a "Fetching roster…" loading indicator while the data loads. The roster auto-loads on your first visit to this tab each session.

๐Ÿน Break Arrow

Submit a Break Arrow request when sons in your tribe will be performing the sacred arrow breaking ceremony. Nation leadership is notified by email and a plaque is arranged.

Submitting a Request

  1. Dad — pick the dad from the dropdown (sorted "Last, First" alphabetically). Only Primary NSD members appear.
  2. Sons Breaking Arrow — checkboxes appear for the dad's sons (children) from the NSD roster. Check each son who will be breaking arrow.
  3. Indian Name — for each checked son, optionally type their Indian (ceremony) name in the inline field. Leave blank if not applicable.
  4. Event — pick the event where the ceremony will take place. Only today and future events appear, soonest first.
  5. Notes — optional context for nation leadership.
  6. Click ๐Ÿน Submit Request. Both chief@tetonnation.com and your own email receive a confirmation.

Your Tribe's Break Arrow Requests

Below the form is a list of all Break Arrow requests submitted for your tribe. Each row shows Dad, Son(s) (with Indian names in parens), Event, Notes, Submitted date, and Status.

  • Status badge — orange "Pending" until someone marks it complete; green "โœ“ Complete" once finalized.
  • โœ“ Done — mark a pending request complete (the ceremony took place / plaque arranged).
  • โœ๏ธ Edit — reopen the form pre-filled with this request's data to make changes.
  • ๐Ÿ—‘ Delete — permanently delete the request (cannot be undone).
Reports & Analytics Visibility

Anyone with reports permission can also see all Break Arrow requests across all tribes via the ๐Ÿน Break Arrow Reqs tab in Reports & Analytics, where they can also mark them complete.

โœ๏ธ Edit Tribe Profile

Chiefs can update their tribe's public profile directly from the Chief Portal — no tribeManager permission required.

Editable Fields

FieldWhat It Does
Tribe Saying / MottoThe quote displayed on your tribe's public card on the Tribes page.
Chief First NameThe chief's display name on the tribe card.
Chief Indian NameThe chief's Indian name, shown on the tribe card.
Chief PhotoUpload a photo or paste a URL. Shown on the tribe card.
Tribe LogoUpload the tribe logo image or paste a URL. Shown on the Tribes page.
Facebook URLLink to the tribe's Facebook page. Shown as a Facebook icon on the tribe card.
Instagram URLLink to the tribe's Instagram. Shown as an Instagram icon on the tribe card.
Tribe Name is Read-Only Here

The tribe name is displayed for reference but cannot be changed from the Chief Portal. Only a tribeManager or admin can rename a tribe (via Tribe Manager). This protects the referential integrity of tribe names across all registration data.

Changes save immediately to the database and are reflected on the public Tribes page right away.

๐Ÿ† Awards & Honors

Add and manage your tribe's awards — the recognition entries that appear on the public Awards page and your tribe's card on the Tribes page.

  • Add a custom award: name, type (annual or campout-specific), year, recipient (an individual or the whole tribe), an optional photo, and notes.
  • Edit or delete any of your tribe's existing awards.
Auto-Created Awards from Tally

Some awards in this list may have been created automatically. In Tally Manager, individual point tiers can have a "๐Ÿ† Award" checkbox turned on (e.g. the 1st/2nd/3rd Place tiers of a competition). When a tribe submits a tally for one of those checked tiers, an award is auto-added to this list. They look like any other award and can be edited or deleted normally — they won't regenerate unless the tally is resubmitted.

๐Ÿ’ฐ Tribe Expenses

An overview of every expense submitted for your tribe. Stat cards at the top show Pending, Approved, and All-Time dollar totals. Expenses are grouped by campout, each with a count and subtotal. Each row shows the submission date, submitter, category, description, amount, and a status badge (pending / approved / rejected). Receipt links open the receipt image in a new tab via a temporary secure link.

Exporting: two buttons above the list — โฌ‡ Excel / CSV downloads your tribe's expenses as a CSV file, and โœ‰ Email Report emails that CSV as an attachment (with a summary table in the message body) to any address you enter.

Deleting: each expense row has a small button to permanently delete that single expense, and each campout header has a that deletes every expense filed under that campout. Both confirm first. Use delete only for junk or duplicate submissions — for a legitimate-but-denied expense, the Wampum should set its status to Rejected instead (that keeps the record).

Viewing vs. Approving

You can delete and export from this Chief Portal screen, but you can't approve or reimburse here. To approve and process expenses, go to the Expense Manager page. Both the tribeChief and tribeWampum permissions unlock Expense Manager scoped to your tribe, so a chief can act on the wampum's behalf when needed. See the Expense Manager tab of this guide.

๐Ÿ”ฅ Tally Points

A read-only summary of tally points submitted for your tribe. Stat cards show the current-year total, the all-time total, and the number of separate submissions. Below the cards, submissions are grouped by category, with the most recent shown in a detail list (date, activity, submitter, result, points).

Notifications

Emails Sent From This Page
  • Break Arrow Request submitted/updated: Sends an HTML notification email to chief@tetonnation.com and the submitting chief's own email. Includes tribe, dad name, son(s) with Indian names, event details, and notes.
  • All other actions: No emails sent. Viewing registrations, refreshing the roster, editing the tribe profile, and browsing expenses/tally are silent.

Overview

User Manager controls who can access the admin pages and what they can do. It handles account approvals, role assignments, page permissions, and notification subscriptions.

Permission required: rightsAssignment or admin role.

Pending Tab

Shows users who have requested access (via the Login page "Request Access" form). Each card shows:

  • Display name, email, tribe, phone
  • What permissions they requested
  • Their message explaining why they need access

Actions

  • Approve — sets role to "member" and auto-applies any requested permissions. A welcome email is automatically sent via Resend confirming their access has been granted.
  • Reject — sets role to "rejected" (they cannot log in to admin pages).

Active Tab

Shows all approved users in accordion rows. A filter dropdown next to the toolbar lets you narrow by category: All Users / Admins / Nation Officers / Members. Default also group-sorts — admins first, then nation officers, then members; alphabetical within.

Each row's collapsed header displays:

  • Name and email on the left
  • Permission chips in the middle — one short-label chip per page permission (e.g. "Events", "Reg Mgr", "Tournaments"). For the tribeChief permission the chip includes the assigned tribe (e.g. "Chief Portal ยท Pocomoke"). Admins show a single gold "All Access" chip. Holders of a nation office also get a purple chip with the office name.
  • $ badge — a small green dollar badge appears when the user has any permission that grants access to financial data (Event Reg Manager, Expense Manager, Tribe Wampum, or Reports).
  • Role badge on the right (member / admin / pending / rejected)

Click a user to expand their settings:

SettingWhat It Does
Rolemember = access only to pages enabled by permissions. admin = full access to all pages (permission checkboxes are hidden, replaced by "full access" text). Note: nation offices and tribe chief/wampum are NOT stored in role — they live in page permissions.
TribeAssigns the user to a tribe. Required for Chief Portal access to work correctly.
Page PermissionsCheckboxes for each permission key. See the permissions table below.
Nation Leadership7 honorary nation-officer titles (Nation Chief, Medicine Man, Sachem, Wampum, Fire Chief, War Chief, Webspinner). Purely titles — they grant no page access. Shown in the member pill as a gold chip. Shown on the public Leadership page as auto-generated officer cards. Visible for every user including admins (the Nation Webspinner is often the site admin).
Public Profile / Officer CardDisplay Name, Indian Name, Photo URL, and Bio. Used to build a nation officer's card on the public Leadership page (auto-generated for any user holding a nation office). Saved with the same Save button as Role / Tribe.
Email NotificationsCheckboxes for CC subscription types. See the subscriptions section below.
Apply Role TemplateDropdown of pre-defined templates. Click "Apply" to replace the user's permissions with the template's permission set. Honorary nation-officer titles are preserved — templates only govern page permissions.
Auto-Backfill on Approve / Reactivate

When you approve a new user (or reactivate an old one), the system auto-links their account to any existing data that was previously matched only by name:

  • Event registrations — any rows where contact_name matches their display name get user_id set to their new account.
  • Awards — any awards where recipient_name matches their display name get recipient_user_id linked. Drives the "Our Awards" tab in the Member Portal.

Actions

  • Save — appears when role or tribe is changed. Saves both to the database.
  • Deactivate — sets role to "rejected" (user loses access).
  • Delete Account — removes the user's profile. Note: the authentication account is NOT removed (must be done manually in the Supabase Dashboard).
Permission Changes are Instant

Page permission checkboxes and notification toggles save immediately when clicked. No need to click a separate "Save" button for those.

Page Permissions Reference

Permission KeyGrants Access To
eventManagerEvent Manager — create/edit/cancel events, send notifications, configure reminders.
eventRegManagerEvent Reg Manager — view/edit/delete registrations, sync NSD tribes, export lists.
tournamentManagerTournament Manager — full bracket and tournament CRUD.
tribeManagerTribe Manager — rename tribes, manage awards and leadership.
tallyManagerTally Manager — manage tally activities and submission reports.
expenseManagerExpense Manager (all tribes) — review and update expense status/reimbursements for every tribe. The national-level finance role.
tribeWampumExpense Manager (own tribe only) — review and approve expenses for the user's assigned tribe only. The tribe-treasurer role. Same Expense Manager page, automatically scoped + tribe filter locked.
reportsReports — analytics dashboard for events and tournaments.
rightsAssignmentUser Manager — approve/reject users, assign roles and permissions.
notificationManagerNotification Manager — send bulk emails to event registrants, tournament teams, or all members.
tribeChiefChief Portal — dashboard view of the user's tribe: registrations, roster, expenses, tally, awards; submit Break Arrow; edit tribe profile. Also unlocks Expense Manager scoped to their tribe (can approve/reject), since chiefs sometimes act on the wampum's behalf.
Tribe Roles: Chief vs Wampum

Two permissions are scoped to a single tribe (the one assigned on the user's profile):

  • tribeChief — the tribe's leader. Gets the Chief Portal: an overview dashboard of their tribe's registrations, roster, expenses, tally points, and awards, plus the ability to submit Break Arrow requests and edit the tribe profile. Also gets tribe-scoped Expense Manager access (can approve/reject their tribe's expenses).
  • tribeWampum — the tribe's treasurer. Gets the Expense Manager page scoped to their tribe, where they review, approve (= reviewed & reimbursed), and reject their tribe's expenses.

Both roles can act on their tribe's expenses โ€” the wampum is the primary, the chief is the backup. They're independent — assign one, the other, or both. Both require the user to have a tribe assigned on their profile (the scoping depends on it).

Notification Subscriptions

These checkboxes control which system-generated CC emails the user receives when certain actions occur in the system:

  • Event Registration — receive a CC when any member registers for an event
  • Tournament Registration — receive a CC when any team registers for a tournament
  • Tally Submission — receive a CC when a tribe submits tally points
  • Expense Submission — receive a CC when an expense is submitted for review
  • Event Cancelled — receive a CC when an event is cancelled
  • Event Reinstated — receive a CC when a cancelled event is reinstated

These are independent of page permissions — a user can receive CC emails without having access to any admin page.

Deactivated Tab

Shows deactivated/rejected users. Actions:

  • Reactivate — sets role back to "member".
  • Delete Account — permanently removes the profile.

Role Templates Tab

Create pre-defined permission sets that can be quickly applied to users. Each template has:

  • Template Name (required) — e.g. "Event Coordinator", "Tournament Director", "Tribe Chief"
  • Description — what this template is for
  • Page Permissions — same checkbox grid as the user settings

Templates make it easy to onboard new admins with consistent permission sets.

Notifications

Emails Sent From This Page
  • Approve a user: A welcome email is automatically sent via Resend informing the user their access has been approved.
  • Reject / Deactivate / Delete / Permission changes: No emails sent.

Overview

The Member Portal (/member-portal) is the personalized landing page for any signed-in member. Visible to any active role โ€” no special permission required. Auth gate blocks logged-out visitors. Member-pill nav and Chief Portal link both appear here for signed-in users.

Tabs

  • ๐Ÿ“… My Events โ€” every internal + external event registration tied to this member (matched by signed-in user_id, falling back to contact_name = display_name). Donation-only registrations render as a compact ๐Ÿ’ donor card with a gold left border, separate from event-attendee cards. Each event card is now an expandable accordion: the header (title + date + โ–ธ chevron) is always visible; click it to expand the full detail. Keeps the list compact when a member has many registrations.
  • ๐Ÿ† Our Awards โ€” personal awards on the logged-in member's account (tournament wins, derby car, etc.). Hard-linked via awards.recipient_user_id (set at tally-submit time when the winner-picker chose this member), with a name-match fallback against display_name for legacy rows. Awards auto-created from tally submissions get an "Auto from Tally" badge.
  • ๐Ÿ›ก๏ธ My Tribe โ€” tribe profile (name, image, description, leadership).
  • ๐Ÿ† Tribe Honors โ€” three sub-sections: Tribe-Wide Awards (gold border), Tournament Wins (blue), Individual Honors (purple, with recipient name + Indian name + photo). Lazy-loaded on first tab open.
Our Awards vs. Tribe Honors

Our Awards is personal โ€” awards on your account (you / your son). Tribe Honors is tribe-wide โ€” every award and tournament win for your whole tribe.

Notes

  • The Honors tab pulls from the same awards table TribeManager + ChiefPortal write to โ€” any honor a chief or admin submits for the member's tribe shows up here.
  • Members can edit their own profile (display name, phone, tribe assignment) via the My Profile link in the pill menu.

Overview โ€” Donations & Service Events

"Service" or "fundraiser" style events accept donations (alongside or instead of attendance) using two related building blocks: open-amount add-ons (donation buttons within an attending registration) and donation-only registrations (a separate registration mode that skips attendance entirely).

Setting Up an Event with Donations

  1. Create a "Donation" add-on once in the Add-ons Catalog tab of Event Manager:
    • Open ๐Ÿ›’ Add-ons top tab โ†’ + New Add-on.
    • Label = "Donation" (or whatever you want shown to registrants).
    • Toggle Custom Amount (Donation) ON. The price field becomes a suggested amount โ€” leave 0 or enter a tasteful suggestion ($20).
    • Save. The catalog list now shows a purple "Donation" badge next to it.
  2. Attach the donation add-on to your event:
    • Edit the event โ†’ Payment Details tab โ†’ Add-ons section โ†’ + Add Item โ†’ pick "Donation" from the dropdown. Override the suggested amount per-event if needed.
  3. Allow donation-only registrations (optional but typical for service events):
    • Same Payment Details tab โ†’ toggle Donation-only registration enabled ON.
    • You must have at least one donation-type add-on attached for the toggle to save.

Result: registrants see a "Step 1 โ€” Choose Your Path" card that lets them pick ๐ŸŽ‰ I'm Attending or ๐Ÿ’ Donation Only. The attending flow includes the donation amount as an optional add-on with quick-pick chips ($5 / $10 / $25 / Custom). $0 totals skip Step 3 (payment) entirely.

How Donations Show Up in Reports

  • ๐Ÿ’ Donations stat card (under the top stats row) โ€” count + total $, includes both donation-only rows AND attending rows that included a donation add-on.
  • Donations by Tribe panel (directly under the stat row) โ€” segmented bar per tribe split into three colored buckets:
    • โ— Member โ€” donation came from a member of that tribe.
    • โ— Guest Referral โ€” guest registrant selected this tribe as their referring tribe; the donation credits that tribe.
    • โ— Donation Only โ€” dedicated donation-only registration that explicitly chose this tribe.
    Inline labels under each bar show the per-bucket dollar totals.
  • By Tribe chart (attending counts) groups all guest variants under "Guest/Prospective" so the tribe-attendance counts aren't polluted by guests.
  • New vs Existing chart adds a Donation Only row when at least one donation-only registration exists. The bar counts only dedicated donation-only rows (the broader donation total is on the stat card).
  • Email Registrant List automatically excludes donation-only registrants โ€” donors don't get the "event roster" email blast. The CSV export still includes them with a Type column for full visibility.

How Donations Show in Other Pages

  • Chief Portal โ†’ Event Registrations โ€” donor rows get a ๐Ÿ’ $X badge on a gold-tinted background and "donor" label instead of an attendee count. The headline summary reads "X members registered ยท ๐Ÿ’ N donors ($total)." Donations don't count toward the Not-Yet-Registered roster pie chart.
  • Member Portal โ†’ My Events โ€” donation-only registrations appear as a compact ๐Ÿ’ donor card (gold left border) showing "Supporting [tribe]" and the amount.
  • Confirmation emails โ€” attending+donation registrants get the standard registration confirmation with a "Donation โ€” $X" line in the order details. Donation-only registrants get a dedicated "Thank You for Your Donation" template with a receipt-style table.

Tip โ€” When To Use What

  • Service event with optional donations + attendance (Day of Service, fundraiser dinner): toggle Donation-only ON. Members and guests can either attend (and optionally donate) or donate without attending.
  • Regular event with optional tip jar: attach the Donation add-on but leave Donation-only OFF. Registrants can throw in a donation while registering, but the only flow is "I'm Attending."
  • Pure fundraiser with no attendance: still pick a regular event, mark it free, attach the donation add-on, and turn Donation-only ON.
v7