Skip to main content
Overrides describe which settings a caller may supply when starting a conversation. Keep this policy narrow: a personalized first message usually needs less freedom than replacing the prompt or attached resources.
This guide covers policy authoring and read-back. The documented conversation-start paths are currently gated, so a saved override policy does not establish working session customization.

​
Policy flags and caller values

The agent’s permission flags live under platform_settings.overrides.conversation_config_override. These are booleans that describe whether a setting may be overridden. They are different from the values a future session request would supply. The individual permission flags default to false. Review the exact nested schema in Get agent before adding a field.

​
Prepare a least-access policy

1

Choose the necessary customization

Prefer dynamic variables for named text values. Only allow broader configuration replacement when the application has a clear need and can validate the caller’s request.
2

Keep resource selection controlled

Treat prompt, model, tool, and knowledge overrides as significant changes. An allowed override does not grant access to another workspace’s resources or replace authorization in the service handling an action.
3

Save the policy in a draft

Preserve the agent’s other platform settings and save a complete server draft. Read back the permission flags and confirm that only the intended fields are allowed.
4

Prepare accepted and rejected examples

Record a valid caller request and a request that should be denied for each enabled field. Keep runtime verification pending until a supported conversation-start path is available.
Other flags under platform_settings.overrides include enable_starting_workflow_node_id_from_client, enable_procedure_ids_from_client, custom_llm_extra_body, and enable_conversation_initiation_client_data_from_webhook. They default to false. Enabling one does not release workflow execution, custom-model publication, or webhook delivery.

​
Frequently asked questions

The policy records permission to supply a conversation-specific value. Editing the base agent configuration is a separate operation; inspect both the policy and base settings in the draft.
No. Do not use an override flag as a workaround for unavailable voice, custom-model, or conversation execution paths.