Enable/Disable Features

Feature List

The complete list of feature flags and org settings — including scope and how each is configured — is documented in the Feature Flag Reference. The flags below are configured via the procedures on this page and are most relevant to self-managed deployments:

Feature	Type	See
enableNewLinguistPage	Admin CLI	Linguist Homepage below
enableLiltCreate	Both	LILT Create below
Incompatible Browsers	Environment Variable	Incompatible Browsers below
enableOCR	Admin CLI	Enable OCR using internal Tesseract deployment
enableOpenAiWhisper	Admin CLI	Enable ASR using internal Whisper deployment
enableWSO2Login	Admin CLI	See WSO2 SSO configuration
External Model Configuration	Environment Variable	External Model Configuration below

Enable Features via Admin CLI

NOTE: For LILT November 2023 release onwards, please use npm run dist-admin-cli instead of admin-cli

Perform the following steps to enable features for the organization:

Connect to front pod:
master# kubectl exec -it -n lilt <frontpod> -c front -- /bin/bash
To enable the feature for an organization, run this command from a front pod, replacing [enableFeature] with the appropriate feature and <ORG_ID> with the relevant Organization ID:**
npm run dist-admin-cli -- set-org-setting --orgIds <ORG_ID> --settingName=[enableFeature] --value=true
Refresh the UI.
Repeat this for all the organizations.

Linguist Homepage

The Linguist Homepage is enabled for the default Translator and Reviewer roles. For custom roles, you will need to select what the user’s homepage should be. For more information, please refer to documentation for the Linguist Homepage.

Configuration instructions

In order to configure the Linguist Homepage, please run the following command for each org: npm run dist-admin-cli -- set-org-setting -o=1 -s=enableNewLinguistPage -v=true Please note: New customers as of Q2 2024 have this enabled by default. If you’re a customer who has been working with LILT since before Q2 2024, you will need to enable this if you’d like the Linguist Homepage.

Enable workflow

Workflows are enabled by default. However, if you don’t see them due to migration issues, connect to the front pods and run the following commands.

npm run dist-admin-cli -- create-workflows-data -o=<ORG ID>

Enabling Features via Environment Variables

Incompatible Browsers

Add a new environment variable to the front values.yaml file as such ALLOW_INCOMPATIBLE_BROWSERS: true . This should be the same place customers configure their header and footer text.

LILT Create

In the UI

LILT Create is enabled by default. In environments where this has the possibility to cause confusion to users, system administrators can configure LILT Create per organization. If disabled, users navigating to the LILT Create page will instead see a brief statement that LILT Create has not been enabled for their organization.

Configuration instructions

In order to disable the LILT Create page, please run the following command for each org: npm run dist-admin-cli -- set-org-setting -o=1 -s=enableLiltCreate -v=false

System Configuration

Please follow the instructions in the section Enable LLM Services.

Miscellaneous Configurations

LILT QA Checks

LILT QA Checks are enabled by default. To disable this functionality, set the following value in your lilt/environments/lilt/values.yml file:

qa:
  onpremValues:
    app:
      args:
        option4: --disable-lilt-qa-checks

LLM Services

With the LILT v5.3.0 release (November 2025), customers can now opt to enable a set of additional LLM services. Follow the steps below to configure the following features:

Feature	Service/ Model
LILT Create	Llama3 (GPU Only)
OCR	Gemma (GPU Only)
ASR (Automatic Speech Recognition)	Whisper (GPU/ CPU)

Prerequisite

Each of these services requires dedicated GPU resources. Please refer to the Self-Managed Hardware Requirements for the specific resource needs.

Enable

GPU Availability: LLM services should not be enabled on systems with only 3 GPUs, as this may cause instability in standard neural services (translation, update) due to limited resources.
Update values.yaml and enable the following services for the required feature: a. llama-vllm-inference: Llama3 model for LILT Create b. gemma-vllm-inference: Gemma model for OCR c. llm-inference-whisper: Whisper model for ASR

Using CPU Workers for ASR (Whisper Model)

To run ASR (Whisper) on CPU workers instead of GPU, follow the guidance in your custom values.yaml and deploy. For example:

# Uncomment the following lines if using CPU workers
# includeTensorflowThreadSettings: false
# bucket: lilt
# resources:
#   requests:
#     cpu: 1
#     memory: 8G
#   limits:
#     memory: 8G

# Remove the following nodeSelector if using CPU workers
nodeSelector:
  capability: llm-gpu
  node-type: whisper
# Uncomment the following lines if using CPU workers
# nodeSelector:
#   node-type: worker

External Model Configuration

Self-managed deployments can optionally allow organization administrators to control which external AI providers (e.g., Amazon Translate, Google Translate, DeepL, Azure, OpenAI, Anthropic, AWS Bedrock) are available on the AI Providers page. When enabled, a new External Models tab appears under Organization Settings where administrators can toggle individual providers on or off.

Enable

Set ENABLE_EXTERNAL_MODEL_CONFIG to true in your values.yaml and deploy. The External Models tab will then appear under Organization Settings for all organizations.

Configure Providers

Administrators can enable providers in two ways: Via the UI:

Navigate to Organization Settings > External Models
Toggle on the desired providers
Enabled providers will immediately appear on the AI Providers page

Via the Admin CLI:

npm run dist-admin-cli -- set-org-setting --orgIds <ORG_ID> \
  --settingName=enabledAIProviders \
  --value='{"aws":true,"google":true,"deepl":true}'

The setting accepts a JSON object where keys are provider identifiers and values are booleans. Available provider keys:

Key	Provider
aws	Amazon Translate
google	Google Translate
deepl	DeepL
azure_gpt	Azure
open_ai	OpenAI
anthropic	Anthropic
aws_bedrock	AWS Bedrock

Providers that are already configured (i.e., credentials have been saved) will always appear on the AI Providers page regardless of the toggle state. The toggle only controls visibility of unconfigured providers.

​Feature List

​Enable Features via Admin CLI

​Linguist Homepage

​Configuration instructions

​Enable workflow

​Enabling Features via Environment Variables

​Incompatible Browsers

​LILT Create

​In the UI

​Configuration instructions

​System Configuration

​Miscellaneous Configurations

​LILT QA Checks

​LLM Services

​Prerequisite

​Enable

Using CPU Workers for ASR (Whisper Model)

​External Model Configuration

​Enable

​Configure Providers

Feature List

Enable Features via Admin CLI

Linguist Homepage

Configuration instructions

Enable workflow

Enabling Features via Environment Variables

Incompatible Browsers

LILT Create

In the UI

Configuration instructions

System Configuration

Miscellaneous Configurations

LILT QA Checks

LLM Services

Prerequisite

Enable

External Model Configuration

Enable

Configure Providers