Platform settings
Path: /admin-settings → Platform Settings tab
Central place for platform-wide configuration that does not belong to a single subsystem tab. Secret values live in AWS Secrets Manager; Postgres stores metadata and non-secret defaults only.
Send test email
Queues an EMAIL_SEND Tasker job so you can confirm the worker's mail transport before relying on password-expiry or notification emails.
| Field | Required | Description |
|---|---|---|
| Recipient | Yes | Destination address. |
| Subject | No | Defaults to Delphi test email. |
| Body | No | Plain text. When empty, the server adds a timestamp and triggering user id. |
After you click Send test email, open Job history, filter by type EMAIL_SEND, and confirm the job reaches COMPLETED.
When EMAIL_TRANSPORT=ses, Tasker needs a matching AWS_REGION, a verified sender (EMAIL_SENDER_ADDRESS), ses:SendEmail / ses:SendRawEmail on the Tasker role, and — while the AWS account is in the SES sandbox — a verified recipient address. HTTPS proxy env vars (HTTPS_PROXY, HTTP_PROXY, NO_PROXY) are honored for SES API calls as of v0.9.13-patch3.
Secret storage
| Field | Description |
|---|---|
| AWS Region | Region for the Secrets Manager client. |
| Namespace | Prefix for secret names (e.g. voiceai/production). |
| General secrets collection | Path segment for platform secrets (default platform/secrets). |
| TLS materials collection | Path segment for trunk TLS PEMs (default platform/trunk-tls). |
Use Test Connection before saving in production. Changing collection paths does not migrate existing Secrets Manager payloads — move secrets operationally first.
AI builder defaults
When enabled, configure provider / model / team-secret key pairs for:
- Briefing chat — pre-build discovery assistant.
- Builder / generator — flow synthesis from the briefing.
Team secrets are tried first, then platform defaults, then local env fallback.
QA scoring defaults
Default provider, model, team-secret key, and scoring prompt for batch QA jobs.
SigNoz observability
| Field | Description |
|---|---|
| Signoz URL | Base URL for call debug views and span persistence jobs. |
| API key secret | Platform Secret key name holding the Signoz API key (default signozApiKey). |
| Retention days | How long persisted span trees are kept. |
| Span persist delay seconds | Delay before PERSIST_CONVERSATION_SPAN_TREE runs after hangup. |
| SIP ladder persist delay seconds | Same for PERSIST_CONVERSATION_SIP_LADDER. |
Resilience defaults
v0.9.14 adds platform-wide resilience defaults for provider timeouts, retry behavior, bot-delay comfort messages, and call-level error actions. Teams inherit these settings unless a team admin enables a team override; individual flows can still override provider and error-handling settings in the Flow Designer.
Use this section for defaults that should apply to most teams, such as:
- STT/TTS/realtime/bot timeout and retry defaults.
- Bot no-input comfort message timing and retry count.
- Call-level failover triggers and transfer/hangup actions.
Leave values empty when you want existing flow behavior to stay unchanged.
Egress defaults
Default global egress route ID — fallback when a transfer has no flow-level route and team/base-number defaults cannot be resolved. Must reference an enabled global egress route synced to Kamailio. Leave empty to disable the platform fallback.
Transfer restrictions
Platform defaults for outbound transfer destination rules (premium-rate blocking, optional country-code allow lists). Teams may override in team settings.
Platform secrets
The bottom section of this tab manages platform secrets — LLM API keys, SigNoz keys, generic secrets, and TLS materials. Metadata is in Postgres; values live in AWS Secrets Manager (general collection vs TLS collection depending on purpose).
Before new teams can use shared OpenAI/Azure keys, SUPERUSERs must create platform secrets openaiDefaultKey and (for non–OpenAI-only plans) azureDefaultKey, then Set Secret for each. See Team default secrets for autopopulate behaviour, tier rules, and troubleshooting.
TLS-specific workflow (CA / client cert for SIP trunks): Platform TLS materials.
Language management
TelWeb language entries live on the dedicated Languages tab. Use Platform Settings for defaults and secrets; use Languages to enable locales and edit translation overrides.
See also
- Platform TLS materials — CA / client cert workflow for SIP trunks.
- Languages — manage TelWeb locales and translation overrides.
- Job history — verify
EMAIL_SENDdelivery. - Tasker (Ops) — mail transport env vars and job handlers.