2026.34 Infrastructure Changes

3 min read

Changes on Application environment

Change	Environment Variable Name	Application Default Value (if env variable unset)	Example	Required	Applications	Short Description
Added	`FEATURE_FLAG_ENABLE_SHARED_CHATS_UN_19869`	`false`	`true`	false	`backend-service-configuration`	Enables chat owners to share a snapshot of a chat with users/groups allowed by the company sharing policy, and recipients can continue it as a private chat. The audience is controlled via the `chatSharingPolicy` company configuration (`spaceMembers` or `allCompany`).
Removed	`FEATURE_FLAG_AGENTIC_TABLE_CAN_ANSWER_ROLE_UN_21308`	-	-	-	`backend-service-configuration`	Can Answer feature is GA now.
Removed	`FEATURE_FLAG_ENABLE_CODE_EXECUTION_FENCE_UN_17972`	-	-	-	`ai-service-assistants-core`	No longer read from env on this service — setting it here has no effect. Now registered in the FF service instead (see row below).
Added	`FEATURE_FLAG_ENABLE_CODE_EXECUTION_FENCE_UN_17972`	`false`	`true`	false	`backend-service-configuration`	Wraps Code Execution tool output in a fenced block. Now registered in the FF service and toggleable per-tenant via the admin UI. Default is `false` — tenants that relied on the old env var being set to `true` must be re-enabled here.
Removed	`FEATURE_FLAG_ENABLE_HTML_WITH_FENCE_UN_17927`	-	-	-	`ai-service-assistants-core`	No longer read from env on this service — setting it here has no effect. Now registered in the FF service instead (see row below).
Added	`FEATURE_FLAG_ENABLE_HTML_WITH_FENCE_UN_17927`	`false`	`true`	false	`backend-service-configuration`	Wraps HTML rendering output in a fenced block. Now registered in the FF service and toggleable per-tenant via the admin UI. Default is `false` — tenants that relied on the old env var being set to `true` must be re-enabled here.
Removed	`FEATURE_FLAG_ENABLE_NEW_ANSWERS_UI_UN_14411`				all	This is GA, the env was still present defaulting to true, but now it was completely removed from the codebase.
Added	`GRAPHQL_OPERATION_NAME_IN_URL_ENABLED`	`false`	`true`	false	`web-app-admin` `web-app-chat` `web-app-knowledge-upload` `web-app-theme`	Appends the GraphQL operation name to request URLs (`?op=<operationName>`) so requests are easier to tell apart in the browser network tab. Set to `true` to enable.
Added	`FEATURE_FLAG_NEW_NOTIFICATION_BANNER_UN_23900`	`false`	`true`	false	`backend-service-configuration`	Switches to the new banner notification admin page and banner view. When enabled, the legacy Banner admin page and the legacy notification banner are hidden. Toggleable per tenant via the admin UI.
Added	`FEATURE_FLAG_ENABLE_KB_ROOT_VISIBILITY_UN_23074`	`false`	`true`	false	`backend-service-configuration`	Users with the `chat.data.admin` role can see all company Knowledge Base folders and files that already have at least one access grant, without needing per-folder access.

Code-execution/HTML fence flags moved to the FF service

The two feature flags for code execution have now been consolidated into the backend-service-configuration as well and no longer live in the ai-service-assistants-core.

The following flags have been moved:

FEATURE_FLAG_ENABLE_CODE_EXECUTION_FENCE_UN_17972
FEATURE_FLAG_ENABLE_HTML_WITH_FENCE_UN_17927

These Feature Flags can now be controlled as environment variables on the backend-service-configuration service or in the Feature Flag Admin UI (currently only accessible by Unique Admins).

Defaults to false - if you had these flags previously enabled on ai-service-assistants-core make sure you enable them again when moving them to backend-service-configuration.

Shared Chats feature setup

Enabling the Shared Chats feature requires enabling a feature flag and adding a sharing policy to the company settings.

FEATURE_FLAG_ENABLE_SHARED_CHATS_UN_19869 needs to be set on the backend-service-configuration (or via Feature Flag Admin UI)
Company sharing audience set via the chatSharingPolicy company configuration

Setting the company configuration setting for the sharing policy is currently only possible via API (GraphQL). Here is how to do that:

Query the current company configuration

curl --location 'https://api.<base-url>/chat/graphql' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <YOUR TOKEN>' \
--data '{"query":"query Company {\n    company {\n        configuration\n    }\n}\n","variables":{}}'

This will give you a JSON with the existing company configuration. Use that and append it for the next step.

Append the chatSharingPolicy to the existing configuration
Possible values are spaceMembers or allCompany.

bash

curl --location 'https://api.<base-url>/chat/graphql' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <YOUR TOKEN>' \
--data '{"query":"mutation CompanyUpdateData($input: CompanyUpdateInput!) {\n    companyUpdateData(\n        input: $input\n    ) {\n        configuration\n    }\n}","variables":{"input":{"configuration":{"referenceStyle":"style2", <...others>, "chatSharingPolicy":"spaceMembers"}}}}'