Platform kill switches (system admin)
The platform-wide toggles for cron jobs, AI features, and third-party integrations — when to use them, and how they override tenants.
System → Settings → Kill Switches (https://cpr.co/system/settings/kill-switches) is the red-button room. If something is on fire — a bug floods email, SMS costs spike, a third-party is down — flip a switch here and the platform stops that behavior instantly across every tenant.
What the page shows
Two sections: 10 feature kill switches and 19 cron job toggles. Each is a simple on/off with a last-changed-by timestamp.
The 10 feature kill switches
| Switch | When to flip off |
|---|---|
| email_enabled | Mailgun is misbehaving or we sent a bad blast |
| sms_enabled | Twilio outage or cost spike |
| payments_enabled | Stripe outage or fraud surge |
| booking_enabled | Roll-out freeze (public booking should not create new rows) |
| support_chat_enabled | AI chat is answering something wrong |
| claude_enabled | AI tool calls — admin chat, proactive worker, approval queue — all pause |
| gmail_sync_enabled | Gmail OAuth issue |
| ringcentral_sync_enabled | RingCentral OAuth issue |
| automations_enabled | Bad automation rule is firing in a loop |
| email_sequences_enabled | Drip campaign is misconfigured |
The 19 cron toggles
Each scheduled job (class-sync, class-reminders, cert-expiration-reminders, gmail-sync, demo-activity, generate-seo-pages, and so on) has its own switch. Turning one off keeps the rest running — useful when one job is failing but you do not want to pause everything.
How kill switches interact with tenant settings
Inheritance
- If a platform switch is OFF, every tenant is OFF — tenant settings cannot override.
- If a platform switch is ON, each tenant can still be OFF individually.
- This is intentional: the platform has veto power.
Was this article helpful?
Still need help?
We're here for you — call or email us any time during business hours.
Mon–Fri 8am–5pm Central Time