Overview
When you translate an email, you may want to keep certain sections exactly as they are. This is common for legal disclaimers, compliance text, or pre-approved footers.
You can prevent these sections from being included in the translation request by using globally locked modules.
Before You Begin
Use this workflow if:
Your footer or content should never be edited in an asset.
You want the content excluded from translation requests.
You can create separate module variations for each language.
Do not use this workflow if:
Users need to edit the module in an asset.
You want the content to be translated automatically.
How Globally Locked Modules Work During Translation
A globally locked module cannot be edited by users after it has been added to an asset.
When you translate an email:
Fully globally locked modules are not included in the translation request.
The content remains unchanged.
This behavior is intentional. It helps preserve approved text that should not be modified during translation.
This approach is ideal for content that must remain consistent across emails, such as legal disclaimers or compliance statements. Because globally locked modules cannot be edited in assets, use this approach only for content that should remain fixed.
To support multiple languages, create a separate module variation for each language. When building your email, select the appropriate variation for the language of your asset. Learn more about Module Variations.
Make a Module Globally Locked
After you decide a module should remain unchanged during translation, enable the Locked setting in the module.
To globally lock a module:
Open the module in the editor.
Open Module Settings.
Enable the Locked toggle.
Save your changes.
Once enabled, users cannot edit the module after it has been added to an asset. The module is also excluded from translation requests.
Best Practices
Use globally locked modules only for content that should remain fixed in your assets.
Global locks work well for legal footers because fully locked modules are excluded from translation requests. This helps preserve approved terminology and compliance language.
Use global locks sparingly. Because globally locked modules cannot be edited in assets, overusing them can make future updates more difficult.
Reserve globally locked modules for content such as:
Legal disclaimers
Compliance statements
Corporate-approved messaging
Other content that must remain unchanged
For content that users need to customize, leave the module editable instead.
If you need to limit editing without completely locking a module, use Editing Restrictions instead of a global lock.
Need more help? Contact support via live chat using the chat bubble in the bottom right corner or email support@knak.com.