Editors can lock a version of content items so that they cannot be edited by others while it is in an approval workflow.

Preview links for external users to allow reviewers without access to the admin UI—such as SMEs or content requestors—to view and provide feedback on content before publishing, enabling efficient collaboration and maintaining quality standards across teams.​

Content Managers will be able to apply more restrict governance processes around their content. They will be able to 'archive' or remove content that is no longer used from the Content Hub and selectors, and then restore it from the Recycling Bin if and when they wish to refresh the content. This capability will also provide editors with an additional safety net against the accidental deletion of content.

We’re introducing support for invariant fields—content fields that don’t require localization and are shared across all cultures. These fields will be stored outside of culture variants and workflow, reducing duplication and simplifying updates. This helps prevent errors, such as overwriting in-progress translations, and ensures consistent values for things like product prices, metadata, or taxonomy. It also improves governance and reduces custom development, making it easier for both technical and non-technical users to manage global content efficiently.

We’re enabling internal users to create and edit orders directly within the admin UI. This allows teams to support scenarios like manual order entry, phone or email sales, and post-purchase adjustments.

Editors will be able to upload files within the channels without needing to navigate to the Content Hub. Uploaded assets will be automatically assigned to a default content type and saved to the Content Hub, and are able to leverage the AIRA digital transformation capabilities.

When available, Marketers will have the option to use field visibility conditions that allow them to specify rules based on which certain form fields can be hidden or displayed to users.

We are focused on incrementally increasing the speed of our SaaS deployment pipeline for customers. Backup creation currently adds a significant portion of time to customer deployments, so we have been doing a series of three backup optimizations targeting the database, app service and storage. In this third of three optimizations, we plan to shorten the amount of time taken when creating pre-deployment backups of the blob storage by modifying the approach that we currently take to our backup operations. Specifically we plan to introduce restore point functionality in our storage backups in order to minimize deployment times.

A follow up increment to our SaaS Deployment Speed Improvements, we will undertake additional enhancements to further improve the speed and scalability of our storage backups.

Transferring from self-hosted to SaaS can sometimes be challenging as the available toolsets may differ. Our SaaS customers are requesting greater visibility into the database that Kentico manages in the cloud. Customers want to be able to inspect the contents (typically for troubleshooting purposes), and validate whether the changes they have made have been successfully implemented. We plan to address this issue while retaining the security and maintainability of our service. If possible we will also introduce additional DB query performance metrics which would enable our customers to monitor improvements that they have made over time.

Managing gated content for individual members can be very time-consuming for website administrators. Membership roles act as a way to organize members, making the management of restricted content on your live site more efficient. Simply group your members into roles and set up access to specific pages or entire sections of your website based on these roles.

When this feature is delivered, Marketers will be able to create online forms that are presented in multiple languages while keeping all the submissions together.

We’re making it easier for editors to create and manage content variants directly within visual editing experiences—like the page builder or email builder. This removes the need to switch back to the Content hub to edit reusable items.

By enabling contextual variant creation, editors can stay in flow, work faster, and more effectively support localized and personalized experiences without breaking focus.

Once Marketers have a clear overview of their digital ecosystems thanks to Customer journeys, it is time to step up and focus on management and orchestration.

Thanks to AI Campaigns, Marketers will have a more effective and straightforward way to prepare assets for their touchpoints and publish them to specific audiences and channels. Of course, associated goals and metrics are the key to success.

Organizations often struggle to efficiently manage and categorize vast amounts of contact data for targeted marketing, customer service, and sales strategies. Manual tagging of contacts based on their interests, behaviors, and demographics is time-consuming and prone to errors, which can lead to ineffective communication strategies and missed opportunities. This lack of automation in tagging processes impedes the ability to effectively segment, personalize interactions, and trigger relevant workflows, ultimately impacting customer engagement and business insights.

By automating the tagging process, businesses can save time, reduce human error, and increase the overall efficiency of their contact management and marketing strategies.

Modelling navigation in the page tree is a simple and user friendly way of managing website menus. However, while they are good for simple sites and navigation, they pose limitations for complex and advanced navigation approaches. We will introduce a new approach that will enable users to set up and manage their navigational structures, so they can generate sitemaps more easily, set up and manage the navigational structures for all their web channels without cluttering up the page tree unnecessarily.

We’re introducing a centralized, personalised means of giving teams clear visibility into workflows in progress, task ownership, and pending actions. This will also help managers to quickly identify bottlenecks, see who’s responsible for each step, and track progress across projects.

We’re extending workflow flexibility by allowing content to follow different paths based on parameters like language, content type, or channel. Leveraging AI, we will enable more granular and dynamic approval processes to support localization, compliance, and multi-channel needs. Larger teams with diverse stakeholders will benefit from tailored routing instead of being limited to a single linear flow. This enhancement aims to reduce complexity, improve efficiency, and remove the need for workarounds in sophisticated content operations.

Support for discounts, coupons, and gift cards is coming to Xperience by Kentico’s commerce offering. Admins will be able to define and manage promotions through a clear UI, including setting discount values, tracking usage, and connecting offers to products. Developers can register discounts via backend APIs and extend logic to match specific project needs. The pricing service will apply discounts automatically, ensuring accurate pricing across carts and orders.

Support for subscription-based business models is coming to Xperience by Kentico, including tiered memberships, recurring billing, and automatic renewals. This will enable clients in membership-driven industries to monetize recurring value without relying on custom development or third-party systems. The feature will offer integrated subscription lifecycle management.

Developers will have the ability to add custom fields to their taxonomy tags so that they can link pages, content items, or extend the metadata associated with the tag.

We already have the ability to automatically tag media assets with appropriate taxonomy tags using AI. We now want to extend this capability to all content that resides within the Content Hub, and to be able to update it when the content changes. As assigning all relevant tags to newly created content items (or pages) can be very time-consuming, we plan to let AIRA do the work for Content editors. This will save content editors and implementers a lot of time as they will no longer need to review and assign tags manually to every piece of content as it is created - especially during project hydration when content is being uploaded in bulk. It will also play an important foundation in being able to use it more relevantly during adaptive digital experiences.

AI experiments and optimization will help automate the testing and refinement of content as well as customer journeys to improve performance metrics. By leveraging AI for tasks such as A/B testing, multivariate analysis, and predictive personalization, marketers can identify the most effective variations of experiences across channels and user segments—without manual guesswork—thereby accelerating decision-making, increasing ROI, and continuously enhancing the digital experience based on real user data and behavior patterns.

We want to allow customers to store, view and manage a number of settings associated with their SaaS tenant via the Xperience Portal including improved secrets handling and the ability to review their App Service and DNS settings.

The ability to view or export logs for incident investigation is important for many of our customers. We intend to provide our SaaS customers with the means to investigate any incidents relating to their account - providing a query-able record of activities that have occurred within our service within a given timeframe. As some of our larger customers are required to retain logs for long periods of time, we also intend to enable them to ship the logs to an external service for storage and analysis.

Our customers have requested the ability to restrict access to specific SaaS environments according to their business or regulatory needs. For example, they may want their content editing team to work on a dedicated staging environment that no-one outside the company's team is able to access. We want to be able to configure these restrictions directly from within the Xperience Portal.