Today, we are releasing a smaller summer update with a range of improvements across the Content Library, translation workflows, chat, flows, templates, and market handling.
The release focuses primarily on making everyday work easier, reducing avoidable mistakes, and improving how content is organized across markets.
📚 Improved sorting in the Content Library
You can now sort tiles in the Content Library by:
• Date
• Content type
• URL
Each sorting option can be applied in ascending or descending order.
This makes it easier to find recently added content, group similar content types, or organize large libraries by URL.
🔎 More precise search filters
We have expanded the search options in the Content Library.
You can now choose how Magnity should match the text you enter:
Containing
Finds tiles where the entered text appears anywhere in either the URL or source text.
Exact
Only returns tiles containing an exact match.
Begins with
Returns tiles where the URL or source text begins with the entered text.
Ends with
Returns tiles where the URL or source text ends with the entered text.
This should make it substantially easier to search large content libraries and locate specific groups of tiles.
🌐 Campaign parameters must now be confirmed before translation
Before starting a translation, Magnity will now ask whether campaign parameters should be included.
You must actively choose Yes or No before continuing.
Previously, campaign parameters were disabled by default. This meant users could easily begin a translation without noticing that campaign parameters had not been included.
The new confirmation step reduces the risk of campaign information being unintentionally omitted.
💬 See which element you are chatting with
When you open the chat, the top of the chat panel now shows the element or module currently connected to the conversation.
This makes it easier to understand exactly which part of an email, webpage, or other asset Magnity is editing or responding to.
'
🔗 Share and delete flows
You can now share flows with other users.
This allows colleagues to access and continue working with an existing flow rather than rebuilding or duplicating it manually.
Flows can now also be deleted when they are no longer needed.
📨 Flows now appear in the correct order
Emails inside a flow are now displayed in their natural sequence:
• Email 1 appears first
• The final email appears last
Previously, the order was reversed, with the final email shown first. This made the flow more difficult to review and navigate.
The updated order should make flow projects much easier to understand.
🎨 Template colour themes
We have opened up support for colour themes in template settings.
This allows a template to support different predefined colour variations.
The functionality must currently be enabled in the backend by the Magnity development team.
If your organization uses templates in multiple colour themes, please contact us so we can discuss how this can be enabled for your setup.
🛠 Bug fixes
We have also resolved several issues affecting markets, content selection, and translation.
🌍 Emails now inherit the correct master market
When you create an email using content from a specific Content Library market, that market will now become the master market for the email.
Previously, the user’s default master market was always applied.
This worked efficiently when users primarily created content for one market, but it caused problems when teams worked across multiple countries or regions.
For example:
A user has the UK as their default master market but creates an email from a German content tile.
Previously, the email would be written in German, but the project would still be assigned to the UK market and exported to the UK email folder.
Going forward, the email will be created as a German market email and exported to the German email folder.
This change applies to newly created emails.
📌 Select all is now always visible
We have fixed an issue that required users to scroll back to the top of the Content Library before they could use Select all.
The Select all control is now sticky and remains available while you scroll through the library.
🗣 Fixed an issue with the language merge field
We have fixed a minor issue affecting the language merge field.
In some cases, Magnity inserted the name of the master language instead of the translated language value.
This could result in individual elements not being translated correctly.
The merge field will now use the correct language value.
🔜 Coming this week: The new Content Agent
This week, we are also preparing to release the new Content Agent.
We have done extensive work to turn it into a more complete research and planning platform.
The new version introduces an entirely redesigned and substantially more flexible canvas, together with broader support for research, planning, and structured content development.
More functionality will follow as we continue expanding the Content Agent over the coming releases.
Questions or feedback?
Our support team is here to help:
✉️ ulsa@magnity.ai | 📞 +45 29 35 25 78
Thank you for using Magnity.
— The Magnity Development Team