System config

Open System → Config. This screen groups global settings such as:

• Business timezone and billing currency — affect how times and money render across Admin; business timezone also drives route Daily schedule window evaluation. New configuration uses a matching row as the effective factor and the route default outside windows; legacy configuration without schedule.mode keeps multiplication semantics.
• Global route strategy — set ROUTE_STRATEGY to hash_affinity (default), weighted_random, weight_priority, or weighted_round_robin; model rules, Route Pool defaults, and priority-tier policies can override it.
• Alert webhooks (for example Feishu or WeCom) — optional incident notifications.
• Custom entries — advanced global values whose names and meanings your team defines.

Sensitive values can be shown or hidden in the UI for screen-sharing.

Integration Keys are managed separately

Admin API Keys no longer live in System Config. Create named least-privilege keys for each system and use case under System Integration → Integration Keys. See Integration.

What to do in Admin

1. Open Config.
2. Verify business timezone and billing currency match your policy.
3. On the global route strategy card, click Change and select the fallback used when no model or Route Pool policy overrides it.
4. Configure or rotate alert URLs if needed.
5. Add any other agreed global entries via Add (or the equivalent control) and save.

Next

• Integration
• Docker