Lead to Cash Bash Hub handbook
This is the internal handbook for people who run, support, and maintain Lead to Cash Bash Hub. It is not attendee, sponsor, or speaker help. Keep public how-to material in the app at /guide and contextual help surfaces.
Use a runbook only when you have the role it requires. UI route guards make navigation clearer; database and function authorization remain the authority. Record what you observed, the time, and the affected record IDs in the incident log; never paste attendee contact details, tokens, or credentials into a ticket.
Start with the right task
Section titled “Start with the right task”- Cannot sign in or see expected access: Access troubleshooting
- Event-day execution: Live operations
- Content is wrong or missing: CMS publishing and recovery
- Need a decision or escalation: Incident response
Claim strength
Section titled “Claim strength”This handbook describes repository configuration at commit e06690c. “Configured” means source declares behavior; “deployed” requires release evidence; “live-verified” requires an observed production check. Do not treat a green build or a local test as production proof.