Organization Settings

LILT provides organizations with several settings that can be tweaked to streamline the translation process in the way that works best for your organization. To find the settings, navigate to the settings gear on the left sidebar. Organization settings are broken down into the following sections:

• Custom QA checks
• Translate / CAT Editor
• Workflow
• Assignment
• Style guide
• API
• Assist
• External Models (self-managed only, when enabled)

The options within the Settings page affect all users and projects across your organization. Changing settings will affect your session immediately and will take effect for other organization members when they refresh their page.

​

Custom QA checks

Customers are able to upload and use custom QA configurations at the organization level. These QA checks will be applicable when running Batch QA in the CAT editor. The ability to upload QA config files is restricted to admin users. Files must be .qccfg file type, and LILT will prevent the upload of any other file type. LILT only allows one config file per language pair. If you need to update a config file, you will need to first delete the existing file and reupload a new one.

​

Translate / CAT Editor

AI provider for CAT suggestions: If the AI provider is set to “LILT Contextual AI”, linguists will see suggestions in both the CAT and the CAT sidebar. If suggestions are set to “None”, there will be no suggestions. “None” is typically used when a translation needs zero MT bias. Allow Copy/Paste: If theAllow Copy/Paste setting is set to “Warn”, linguists will get the below popup if they copy/paste content from outside of the LILT Platform into LILT Translate. If the setting is set to “Block”, all copy and paste will be blocked within LILT Translate. Fuzzy match threshold: This is a set 75% threshold and not configurable. More information is available in Data Source Memory Matching. Case-sensitive matching: If this is turned on, Data source matches are forced to respect case-sensitivity. Segment character limit control: When enabled, this will warn the translator that the space of the translation is limited based on character count metadata (if available). Prioritize recency: If enabled, this will disable 101% match priority and allow for recency-based match prioritization. 101% matches will be treated as equivalent to 100% matches, prioritizing recency over context precision. For more information, please reference Translation Memory Matching and Suggestions. Mandate Error logging: If turned on, error logging is mandatory in the selected stage(s) when a reviewer changes anything in the target segment. For more information on error flagging, please reference Segment Comments and Error Flagging.

​

Subtitling QA checks

Please reference Subtitling QA checks for more information.

​

Workflow

The Workflow settings section allows you to set the default settings for new Projects created within your organization. These settings can be overridden on a per-Project basis from the Project Settings page of existing Projects. For more information about the Prioritize review sampling with AI setting, please reference the Review Sampling page for more information.

​

Allow unlocking locked segments

Unlocking locked segments allows for any role to unlock and update locked segments during the selected workflow stage(s). This is intended as a safety valve specifically for Reviewers and Customer Reviewers if errors are spotted during their review so they can quickly and easily correct any errors present, instead of needing to manually update Data Sources. After making any changes to a locked segment, the segment will be re-accepted and will no longer appear as locked. Any changes made will update the data source, auto-propagate to other exact matches in the document, and update in other translations in progress. The default status for this setting is OFF. *Note: While this setting can be applied to any workflow stage, the vast majority of organizations who use this setting will only have Customer Review selected. For more information, please reference Segment State Indicators.

​

Quoting settings

Automatic and Offline Quoting are configured in settings for organizations that wish to use quoting functionality. For more information, please reference Quoting in LILT.

​

Assignment settings

When a linguist is assigned to a document, they are automatically sent an email notification. Whatever content is in the Organization level instructions field will be included in all assignment emails for the organization. This is a great place to include: Note that assignment instructions can also be added at the Project level, as described in the Project Settings article. Limit Assignments: Only users and linguists directly in the organization can be assigned. Auto assign linguists: When turned on, Auto Assign will trigger 30 minutes after job creation.

​

Style guide

LILT’s style guide contains settings that are used for LILT Create and AI Review. Additionally, the style guide is available to linguists as part of Reference Materials and displayed directly within the CAT editor sidebar. Default values are applied, which can then be customized at the organization level as needed. Changes are saved on a field change. When a toggle switch is activated to indicate “Yes”, an open text box appears to provide additional specifics as needed. LILT Create - The LILT Create prompt is customized with all inputs from the style guide to provide context for content generation. To access the style guide from LILT Create, users can click on “Update your settings for LILT Create”, which will open the style guide in a new tab. AI Review - The AI Review scoring and automated revisions are customized with all inputs from the style guide, with the exception of the Formatting section, as those require document-level and external source context. The style guide is broken down into six sections:

• General
• Terminology
• Conventions
• Style
• Special rules
• Formatting

​

API

The API section lets you manage the API tokens used to authenticate with the LILT API.

​

Legacy API Key

Your original API key is displayed at the top of this section. This key continues to work as before and is not affected by the introduction of API tokens.

​

Individual API Tokens

The API Tokens section allows you to create and manage multiple named tokens for different integrations. This is useful when you connect several systems to LILT (e.g., a CMS connector, a CI pipeline, and an internal tool) and want to manage each one independently. Creating a token

1. Click Create Token.
2. Enter a descriptive name (e.g., “Contentful connector”).
3. Select who this token is for. Typically this will be the token creator but could be another customer contact or admin
4. Optionally set an expiration date.
5. Click Create. The full token is displayed once — copy it immediately and store it securely. It cannot be retrieved later.

Managing tokens The token list shows each token’s name, prefix (e.g., lilt_abc1...), creation date, expiry, and when it was last used. From this list you can:

• Revoke a token to permanently disable it without affecting other tokens.
• Rotate a token to generate a new secret while keeping the same name and configuration. The new token is shown once for copying.

Best Practices for API Keys Generate one API key per user per application. For example

1. Each connector has it’s own API key
2. Each user gets their own API key (e.g. if I’m using an API key for some sort of integration, I generate a new API key)
3. You can only access/copy an API key at the time of creation. You can’t go back and copya key after it’s been initially generated.
4. Temporary uses should have temporary keys but connectors should have non-expiring keys or expiration dates long in the future (because of the risks of connector API keys expiring)

API tokens use the same authentication methods (?key= query parameter or Basic Auth) as the legacy key, so no changes are needed in existing SDKs or CMS plugins. For more information, see our API documentation.