Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dialai.ca/llms.txt

Use this file to discover all available pages before exploring further.

Environment workspace in light mode
The Environment workspace is where you view and override the platform configuration values that apply to your tenant — timeouts, allow-lists, integration API keys, and other knobs that change platform behavior without touching a flow. Two tabs: Environment (your tenant’s overrides) and Global Manager (cross-tenant rollouts).

​
Accessing Environment

Navigate to Settings > Environment in the left sidebar.

​
Environment tab

The Environment tab lists every config entry visible to your tenant, grouped by namespace (e.g., Initializers, Javascript, OpenAi, Speechmatics).
ColumnWhat it shows
KeyDotted-path name of the entry (e.g., Initializers.TimeoutSeconds, Javascript.AllowedDomains).
TypeValue for plain config; Secret for values pulled from the secret manager.
SourceWhere the current value comes from — Tenant override (set here), Secret Manager (provisioned externally), or platform default.
StatusConfigured once an override is in place.
ValueThe current value. Secrets show as Hidden.
ActionsUpdate value (for plain values) or Update secret (for secrets).
Click the information icon next to a key to see its description and accepted format.

​
Adding an override

1

Click Add Override (top right)

Opens the override dialog.
2

Pick the key

Choose the variable from the catalog. The catalog lists every variable the platform recognises.
3

Set the value

For plain values, type the new value. For secrets, you’ll be prompted to write to the configured secret manager.
4

Save

The override takes effect immediately for new conversations.
Changes to integration credentials (e.g., Speechmatics.ApiKey, OpenAi.*) propagate to live infrastructure on the next request — if the new value is invalid, live conversations will start failing. Validate against a non-production tenant first.

​
Global Manager tab

The Global Manager applies the same change to multiple tenants at once. Useful for platform-wide rollouts where you don’t want to click through tenants individually.
1

Pick scope

Toggle All to target every tenant, or turn it off and pick specific tenants from the multi-select.
2

Pick a key

Choose the variable to roll out.
3

Set the value

Enter the new value in the Action panel.
4

Review the per-tenant table

The table below shows the current value for each selected tenant — useful for spotting tenants where an override is intentional and shouldn’t be clobbered.
5

Apply

Pushes the change to every tenant in scope.
Global Manager is typically restricted to platform admins. Most tenant operators don’t have access — and shouldn’t need it.

​
Environment vs flow Variables

Don’t confuse this page with flow Variables (the per-flow knobs on the flow editor’s Variables tab):
SurfaceScopeWho sets itUsed by
Environment (this page)Tenant-wide.Tenant admins.Platform infrastructure — timeouts, allow-lists, API keys.
Flow VariablesOne flow.Flow author.Function code and prompt templating inside that flow only.
If a value is shared across multiple flows, it belongs here. If a value is specific to one flow’s behavior, it belongs on the flow’s Variables tab.

Theme

Tenant branding — display name, logos, palette.

Flow configuration

Per-flow Variables, Wrap Up, Start Up, and more.

Permissions

Roles that can read or modify these values.