Support & Feedback

Viewing documentation for: Treasurer

All Roles Treasurer Leader Parent Scout

Treasurer focus

Prioritize account setup, controls, and financial verification responsibilities.

  • Validate billing, payment confirmation, and reporting requirements first.
  • Coordinate leader access while keeping treasury-only controls restricted.

Use this page when you need help, want to report a bug, or want to request an improvement.

TroopForge support starts with the in-app feedback form in the footer, then escalates by role based on the workflow impacted.

Support Channels in TroopForge

  • Primary path: in-app footer Send Feedback form.
  • Best for: bugs, workflow confusion, missing access, and enhancement requests.
  • Feedback link appears only when signed in.

Submit Feedback from the App Footer

  1. Open footer link Send Feedback.
  2. Complete Name (recommended for follow-up clarity).
  3. Complete Email (required) so the team can respond.
  4. Describe the issue in Description (required) with expected vs actual behavior.
  5. Use Add a screenshot when the issue is visual or tied to a specific page state.
  6. Submit with Send Feedback, or use Cancel to close without sending.

If the form does not open, refresh once and retry from the same page. If it still fails, include that detail in your next report.

Support Request Template

  1. Role and account context (treasurer/leader/parent/scout).
  2. Exact page and action taken.
  3. Exact error text or warning text.
  4. Expected result versus actual result.
  5. Whether issue is blocking troop operations (for example, payment or invitation flow).

Leader/Treasurer Escalation Scenarios

Access and configuration blockers

  • Missing admin actions in Organization Settings.
  • Invitation flow issues in Invite User or pending invite follow-up.
  • Roster import preview/confirm mismatches.

Financial and reconciliation blockers

  • Unexpected balances in event registrations and account summaries.
  • Approval flow issues in Pending Payment Requests.
  • Treasurer-only admin boundaries not behaving as expected.

What Happens After Submission

  • Reports are triaged by severity, reproducibility, and troop operational impact.
  • Critical blockers (access, payments, data integrity) are prioritized first.
  • Feature requests are reviewed for repeat demand and roadmap fit.

Known Limits of the Feedback Form

  • One submission should focus on one issue to keep triage clean.
  • Do not include sensitive payment credentials in reports.
  • Use clear reproduction steps for intermittent issues.

Related Documentation