How to manage platform settings

Platform-wide configuration lives here. Small changes ripple everywhere, so here's what each piece does.

What this guide covers

Central platform configuration: fee structure, defaults, payment modes, system information, cache management, streaming platform settings, and oversight of all API keys.

What you'll need

Platform admin access.

Where to go

Admin → Settings (plus Stream settings and API key oversight).

SCREENSHOT_REQUIRED: admin/settings/settings-page

Step by step

1. Open Settings to review/update platform configuration.
2. Key values include: processing fee percent + flat fee, default currency, default commission rate, platform name.
3. Payment mode (e.g. Stripe test vs live configuration) is reflected via platform settings — verify before/after any processor change.
4. Use cache-bust after publishing changes that should appear immediately on the storefront.
5. Check System info for environment diagnostics.
6. Manage platform-wide API keys (revoke any compromised organizer key); stream settings control contribution permissions and streaming configuration.

And then?

Settings changes affect the public platform immediately (subject to caching). Fee changes alter all subsequent checkout calculations.

Good to know (rules & limits)

• Treat fee and payment-mode changes as high-risk: verify with a test order after changing.
• Revoking an API key immediately breaks integrations using it.

How accurate is this?

Verified from source: getSettings/updateSettings, systemInfo, bustCache, checkout-stats, api-keys adminIndex/adminDestroy, stream settings/contribution-toggle routes; settings keys exposed by /platform/settings.