Add a Module to an Asset
Modules are reusable blocks of content like headers, footers, or product sections. You can drag and drop them into your asset layout.
Open your asset in the editor.
Scroll down on the right panel until you find the Modules section.
Locate the desired module.
Click and drag it into your asset where needed.
Working with Modules
Behavior of Added Modules
Modules are locked when added. You can move, clone, or delete them as a group.
You can update text, swap images, and add links inside the module.
You cannot add or remove content blocks within the module unless it is broken apart.
Break Apart a Module
If you need to customize the layout or structure of a module:
Click the Break apart module button.
The module will be split into editable sections.
You can now add or delete individual content blocks.
🔒 Note: Only users with the correct permissions can break apart modules.
Deleted Modules and Assets
If a module is removed from the admin panel:
It will not be automatically deleted from any asset it's been added to.
A warning will appear in the Optimize tab if a deleted or outdated module is present in your asset.
📌 Use this warning to review and update affected assets if needed.
Updating an Out-of-Date Module
How to Identify Outdated Modules
Open the Optimize tab in your asset.
Look for a warning beside the module or in the module list.
Click the warning or the dial icon beside the module to view update options.
How to Apply Module Updates
You have two ways to update a module:
In the Optimize tab, click Update module.
Click the dial icon beside the out-of-date module.
You can also update all modules at once using the Bulk Update option in the Module Manager.
What Gets Updated — And What Doesn’t
The system distinguishes between structural and content changes:
Type of Change | Updated? | Notes |
Layout (new rows/columns) | ✅ Yes | Structural changes are applied |
Editable text or images | ❌ No (if customized) | Custom content is preserved if marked as editable |
Locked content | ✅ Yes (for non-admins) | Reverts to the module’s default to maintain compliance |
✅ What Will Change (If part of the updated module)
These updates are applied automatically during the merge:
A new button, image, or column is added to the module layout.
A heading’s font style, color, or size is changed by the admin.
Padding or spacing between content blocks is updated.
A background color or border style is added or modified.
A new social icon is included in a footer module.
An old layout with 2 columns is replaced with a 3-column layout.
Text in a locked (non-editable) field is changed by the admin.
❌ What Won’t Change (If customized by the user and marked editable)
These are preserved to avoid overwriting your asset-level edits:
Text edited in a paragraph field marked as editable.
A swapped image (e.g., replacing a product photo with another).
A changed link (e.g., customizing a CTA button URL).
Reordered items within a list module if the container is editable.
Custom alt text or accessibility labels.
Special Case: Admin Overrides and Merges
If an admin has overridden a module and a non-admin user later tries to update it:
❌ The admin’s override will be lost. Non-admins lose admin-only changes when updating.
✅ If the admin performs the update, their custom override is preserved. Admins keep their overrides when updating.
Why This Happens
Admin users have elevated permissions that allow them to bypass locked fields and restrictions. Knak is designed to prioritize admin-set rules to ensure brand and legal compliance. Non-admin users cannot carry forward restricted edits. This prevents mistakes or unapproved changes from appearing in published content.
Scenario | Admin Updates Module | Non-Admin Updates Module |
Editable text | Preserved | Preserved |
Locked text | Updated | Updated |
Admin-only override (e.g., hiding a compliance disclaimer) | Preserved | Overwritten |
Image swap in a locked field | Replaced with default | Replaced with default |
Best Practices to Avoid Conflicts
To prevent lost work or confusion:
Admins should apply overrides last, just before review or approval.
Non-admins should not update modules after admin changes.
This keeps the workflow clean and ensures branding rules are followed.
Basics of Module Updates:
Need more help? Contact support via live chat using the chat bubble in the bottom right corner or email support@knak.com.






