WoodWing 2026 Product Update

Good day, good afternoon, or good evening to everybody joining us today on this very important product update webinar. This is a webinar where we yearly assemble the full team of product managers and people responsible for the WoodWing Assets, Studio, and Connect portfolio to showcase the product release summary of 2025 and, of course, share the roadmap initiatives and plans for 2026, for the year to come.

I am Magdalena. I will be the moderator of the webinar today, and it is a great pleasure that you have joined us today to ask any questions that you might have throughout the sessions. We hope to have enough time to answer them all after the presented features and functionalities.

So, how does the agenda of the webinar look for today? Firstly, we are going to recap the 2025 initiatives. Then, the roadmap planning for 2026 is going to be shared. Then, individually, we will deep dive into WoodWing Assets, the two versions, version 6 and 10, WoodWing Studio, and last but not least, WoodWing Connect and the WoodWing apps.

Again, in the end, we want to answer any questions that our audience, customers, prospects, partners, anybody in the WoodWing ecosystem, has for us. If not, we will, of course, follow up with each and every one of you individually to provide you with the necessary response.

It is a great pleasure to have the speakers today, very important people from our product development and product management departments. In order of appearance: Tom Pijsel, the VP of Product Management. He will do the first introduction and overview of the roadmap plans. We have Ben Yao Kiongma, our Product Manager for WoodWing Assets, Dani Leyhue, our Product Manager for WoodWing Studio, Jeff Gapp, the Product Manager for WoodWing Connect, and Paul Walker, our Development Manager for WoodWing Connect and the WoodWing apps.

We have a great session planned out for today, and we hope to keep your attention and knowledge gained after this session for all the product releases we have had recently. Without further ado, I would like to ask Tom Pijsel to join us on stage.

Thank you. Let’s first dive into all the great things that we released last year. So, what did we do? We launched Assets 10, the next iteration of WoodWing Assets, with a brand-new UI, new ways to configure single sign-on, an in-app video editor, design editor, optimized mobile share links, and we will showcase Assets 10 later in this webinar.

Secondly, we focused on AI layout automation for newspapers. Also for that one, we have a demo later in the deck. We have been working on various apps as part of the WoodWing Connect umbrella, so PDF Manager, Workflow Assistant for Assets, and a Content Delivery Hub. And last but not least, content collaboration. Content collaboration has also been integrated into Assets 10.

But for 2026, we have, of course, much more in store. We are continuing with Assets 10, so a native trash can, of course a Studio integration, and improvements to the Assets 10 portal feature, and more to come. Next to that, AI assistants, both in Assets and Studio. We are going to work on copy editing, copy fitting, SEO, tone, and voice. And we are also going to explore the power of AI-powered search.

Of course, we are continuing with AI layout automation for both newspapers and magazines. And we are working on moving Connect and Cloud, so migration tooling to migrate customers from Assets 6 to Assets 10, usage dashboards so that you can have real-time insights into the amount of storage that you are consuming and the number of users that are accessing your system. And of course, we are continuing with the work of decoupling integrations, which will make it easier for you to upgrade to newer versions.

But let’s dive into the roadmap details. This is the roadmap for Assets 6. Key features for this year are the Studio integration, trash can, and API improvements. The portals feature, so we are finishing up our Angular migration project and simultaneously introducing a few new features, for example the ability to configure the filters that you want to see in the portal.

Also, a big focus will be on migration tooling. That has actually already started, from Assets 6 to Assets 10. And also along the year, we will explore the potential of AI-powered search and natural-language-powered search technologies, and how to best integrate them into Assets.

For Studio, the current focus for layout automation is on newspapers, but towards the summer, we will shift our focus to magazine production. Also here, you see the integration with Assets 10 on the roadmap. So this is the Studio part of that work, and the various AI assistants in both the Studio client. We are also looking at whether we can integrate the copy-fitting solution in InCopy.

And then lastly, Connect. We are extending the Connect core capability. So this is both our integrations and our plug-in work. For example, we are adding the planning interface as we speak, as well as making changes to the core products, both Assets and Studio, to better facilitate external integrations.

Next to that, we are consolidating our integrations, both the traditional WoodWing integrations as well as those coming from the Concord team, under one umbrella. Examples of those are also the apps that we are working on. So that is the Workflow Assistant, the Content Delivery Hub, and the PDF Manager, to also make them available and streamline Cloud migrations.

And with that, let me hand you over to Yaker to give you an update on Assets 6 and Assets 10.

Thank you, Tom. I will talk about the improvements. Let’s move to the next slide. Here we go. I will talk about the improvements we have made to Assets 6 and Assets 10.

For Assets 6, our main focus has been on fixing bugs and investing in better stability and performance. So this will also remain our focus for this year. For our cloud-native DAM product, at the beginning of this year we still called it Swivle. We introduced, as already mentioned, a completely redesigned interface with many new features and improvements. This major step forward is also the reason why we rebranded Swivle into Assets 10.

This version includes mobile-friendly share links, improved metadata management, in-app photo and video editing, and much more, which will be demonstrated in a video later. Assets 10 also integrates with our new WoodWing Identity Service, and with this identity service, we now offer single sign-on for Assets 10.

I would also like to briefly highlight a few key improvements we introduced last year. We released the metadata taxonomy feature. This is an Assets 6 feature brought over to Assets 10. This feature allows users to organize, standardize, and quickly search assets using controlled categories.

Another DAM consolidation feature currently released for testing is the front-end integration. This feature enables the panel and action plugins directly in the interface of Assets 10. It is currently in testing, and the production version will be released very soon.

The content collaboration feature has been added to Assets 10, and this feature allows teams to share, review, annotate, and approve assets directly from the DAM product. And finally, in addition to the photo editor and the video editor, we also added the design editor to Assets 10. With this editor, customers can easily design and customize flyers and leaflets directly from the DAM product, directly in the web browser. Let’s go to the video.

Here we go. Hello. In this demo, I would like to demonstrate some of the latest features in our WoodWing Assets product. This version of Assets is called Assets 10. We completely redesigned and updated the whole interface, and let me highlight a few differences between Assets 10 and the Assets 6 product.

The design is more up to date with standards. We have removed a few of the buttons, and we are now working with tabs in the design. We have the browsing part, as you can see here. We have the share part, where you have your share links, and we have the checkout part, where, if you are working with checked-in and checked-out files, you can find them over here.

Let’s talk about the metadata panel on the right side. In this metadata panel, we have now added a search option. So you can now search for metadata values in this metadata search. We also included a nice preview of the selected image.

In the metadata panel, you now have the ability to work and order the different categories and the individual metadata fields within the categories. For example, I would like to start with the file category at the top, and then within the file, I would like to have the demo category in the file category on top. You can now save it. You will now see those changes are applied on the right side here.

The same concept will also work in the filter panel. In the filter panel, you also have the ability to order the different metadata fields, as you can see here. And also this same concept will work in the different views and the metadata fields that are visible in the different views. So here you also have the ability to drag and order the categories, and within the categories, different metadata fields, and that, of course, goes for the different views as well.

Let’s upload a few files. The upload process also works a bit differently in Assets 10. We make use of multipart upload. This allows for uploading much larger files. You do not have a separate screen. It happens directly in the background. And here you see the uploaded file, where you can add metadata fields.

The multipart upload is also a big difference, a bit more technical. How uploads work on Assets 10 is that we do it directly to our back ends. This will allow for much faster upload because we bypass the server.

A nice feature is that during uploads, we make use of an AI auto-tagging engine, and during uploads, you see that we automatically add tags from the artificial intelligence engine. We make use of Amazon Rekognition. The preview is sent to Amazon Rekognition. This is viewed and looked at, and from that we get multiple tags back, which are added to the general tags.

So that is a cool feature that is part of the product itself. It is an in-app feature. Compared to our previous version, we now have what we call a different list view. The list view is more condensed. As you can see here, in the previous version, the list view was larger, and it is now more condensed. With that, you can see many more files at once. So this is much more like a list you see in your file explorer. This is a nice improvement.

Let’s go over to share link. Let me create a share link. Let me move to this new tab. And here you see the new share link. A great new feature is that we have now optimized the share links for mobile use.

And now you can see when the share link is opened on a mobile device, we automatically optimize the mobile share link page to the size of the mobile screen. This user only has the ability to view files. But if we had enabled upload in the same share link, guest upload, then users could also upload files in an optimized environment directly from their mobile.

We have introduced a nice dark mode. We have also introduced multiple in-app editors. For example, now if I open a JPEG file, I can edit this file. So we still have the ability to check out and check in a file, and then a user can use their own applications that are saved and installed on their local machine. But now we have introduced an in-app photo editor as well.

Let me open this file, and here you see a few windmills. Let me crop this image and give it a bit more of a vintage look. Let’s add a classical frame. And let me add some text: windmill in sand.

I can save this. I can select save as new, or I can save it as a version. Let me do the last. So you see the file is now the most recent file, this new edited file, but we still have the original file over here. But now you can see the checked-in file is this version.

The same concept will also work for videos. Let’s open this. Now I have an MP4 file. And now I do not have the option to open in a photo editor, but now I have the option to open in video editor. Here we have the file. At the bottom, you have a nice timeline where you can scroll through the file.

You can add an additional file that is stored locally or in the folder of Assets 10. You can work with the file. For example, you can change the volume, you can crop the file, you can trim it. So let’s remove a part of the beginning.

We can search for files in the system. This is that example. So let’s add this here. On the right here, we can add some text. And of course, you can show where to include the file. So where should this image be added?

There are many more possibilities here around adjustments, animations, how text should fly in, or how it should be presented. You can save the project and then restart working on the project. You can save it as a new file, or you can save it as a version.

Here we have it. And also here, you have the new version, but also still the original.

The last thing I would like to show is pretty much in line with the photo editor and the video editor. It is what we call the design editor. You can start the design projects. You can work with nice templates, and you can see this as an in-app light design version added to Assets 10, where you can create small leaflets and brochures directly from the DAM system, which can be shared with digital channels or different outlets.

You can, of course, completely customize this. You can work with the default templates. You can create your own. You can upload your own templates that different users can start from. You can save your projects and work from there.

The last thing I would like to mention is the WoodWing Identity Service. With the newly introduced WoodWing Identity Service, we now also offer single sign-on for Assets 10 users. This can be completely set up by a customer or partner itself. We support the latest standards like SAML and OpenID Connect, and it can all be done self-service, but of course, we can also help you with the configuration.

This concludes my demo. Thank you, and let’s move over to Dani.

All right, taking a look at WoodWing Studio. I want to first talk about some of our routine maintenance that we have been doing. First, I am going to start off with Adobe CC 2025. We, of course, added support for InDesign 2025, Studio for InCopy 2025, InDesign Server 2025, and then also Smart Styles 20.1 was released.

Inside WoodWing Studio itself, we added some updates for layout preview. We recently launched a new desktop app and Chrome extension. We added pagination for InDesign Server jobs. We released a new API which allows multi-set object properties. So if you are trying to update multiple metadata fields at the same time, there is a new API for that. And a new web service for clean and delete issues, as well as updates for MySQL 8.4, RabbitMQ 4.1, and PHP 8.4, is on the way, almost released.

All of these features are available for all of our on-premise and cloud customers. Now, I am going to shift focus and talk a lot about a feature that we released: content collaboration and commenting abilities. This is exclusively inside WoodWing Cloud.

Hello everyone, and welcome. Today, we are going to be taking a look at some of the most impactful collaboration features introduced in WoodWing Cloud over the past year, with a special focus on comments, @mentions, and the activity hub available in Studio and WoodWing Assets 10.

These updates are all about making collaboration cleaner, faster, more intentional, no matter how many people or files are involved. In any collaborative content creation process, communication is everything. Writers, editors, designers, fact-checkers, and reviewers all need to work together seamlessly to make content more accurate, aligned, and ready to publish.

Before now, feedback could easily get lost. Comments were general, notifications were scattered, and it was not always clear who needed to take action. That is exactly what these features are designed to solve. With comments, @mentions, and the activity hub, teams can now communicate directly inside the content, clearly signal ownership, and stay on top of conversations without leaving the platform.

One of the biggest improvements to collaboration in Studio is the ability to tag teammates using @mentions inside comments. To mention someone, simply type the @ symbol in any comment or reply. As soon as you do, a drop-down list appears showing relevant users by their full display name, such as Dani Leyhue. As you continue typing, the list automatically filters, prioritizing first-name matches to make the selection quick and intuitive.

The drop-down updates in real time. You can scroll using your mouse or arrow keys and then press enter, or you can simply click on the name if you want. Once selected, that person’s name is inserted directly into the comment, clearly calling their attention to that message.

The list shows up to 25 users at a time and is sorted alphabetically. If a user has been deactivated or deleted, their name will appear as unknown user with a question mark avatar, so that there is never confusion about who is active within the system. With mentions, feedback becomes direct, focused, and actionable, ensuring that the right people are looped in immediately.

Once someone is mentioned, the experience does not stop at the comment. Every @mention and reply generates a notification that appears inside the activity hub. It is a centralized place designed to help users manage all collaboration across their files. No more hunting through projects or guessing where feedback lives.

At the top of the Studio interface, a badge icon displays the number of unread comment notifications. This gives you instant visibility into new activity without opening individual files. You can filter the feed to show only unread notifications, mark individual items as read or unread, or select mark all as read to clear everything at once. The activity hub ensures nothing important slips through the cracks, especially when you are juggling multiple projects.

Clicking the badge opens the activity hub, which overlays the main application. In your comments feed, all comments routed to you start with the most recent. Each notification includes helpful context, whether it is a mention, a reply, or a resolved comment, and it will also show you a preview of the comment text. From here, you can view the thread to see the full conversation, or you can select go to file to jump directly to the source file and review details in context.

Now, let’s take a look at comments inside WoodWing Assets 10. Creative projects often involve many revisions and many contributors. To support that process, comments can now be added to any file in Assets 10. Whether you are requesting feedback, like “please review this file,” or giving direction, “what do you think of this version,” comments keep discussions visible, contextual, and tied directly to the asset.

Select any file in WoodWing Assets 10. Click the comments icon in the right-hand toolbar. Choose create a new comment. Type your message and post. You can now easily manage your comments. You can edit them, delete them directly from the panel, and mark comments as resolved once no further action is needed. Resolved comments move to a separate tab, keeping the active view clean while preserving the conversation history.

Just like in Studio, you can tag teammates using @mentions in Assets 10. The same rule applies: full names are displayed, the list shows up to 25 users, and deactivated users appear as unknown users. Mentions and replies appear in the activity hub, where users can filter, mark notifications, view threads, or jump straight to the file.

Thanks for watching this demonstration of comments, @mentions, and the activity hub in WoodWing Studio and WoodWing Assets 10. These features are designed to reduce friction, improve clarity, and help teams collaborate more efficiently without leaving the tools they already use every day. For full details, visit the WoodWing Help Center. And we cannot wait to see how your teams put these collaboration tools to work.

And with that, I am going to pass it over to Tom to talk about AI layout automation.

Thank you, Dani. Yes, layout automation. So, what is it all about? We see that a lot of manual effort is spent in repetitive tasks to fit content on the page. And although templates are great, you only have so many, and they are hard to manage.

Also, looking at alternative solutions, we see that they are often rule-based, which can lead to boring designs. And those AI engines make the articles bigger and smaller themselves, which leads to an inconsistent flow of articles over the section of your newspaper or magazine.

So we set ourselves the goal to create an algorithm that can generate the geometrical information on where to place the articles and images across the pages of a newspaper or magazine, all to minimize the need for manual copy fitting afterwards. The manual copy fitting is, for example, done by a designer, but it could also be a journalist who has to copy fit the text. So this functionality impacts both roles.

We introduced two new concepts into WoodWing Studio, which are the blueprints and the shapes. By using AI search technology, we combine past human-created designs to suggest the best layout for the content at hand.

The blueprints are the predefined high-level layout patterns which ensure a consistent flow within the section. So you control the size of the articles. The engine will never make the articles bigger than what you configured. A blueprint box can contain a story or an advert, for example. And the stories are split into several different types: lead story, secondary story, third, or filler. And you can create these pillar stories where you have multiple smaller stories combined into one pillar, combined, for example, with ads.

There is not an infinite number of blueprints that you can think of. So what we see now is that anywhere between 75 to 100 blueprints covers all the variants that you can ever think of, and it is typically more than what you now have in your templates.

The second thing that you need is an InDesign article shape, and this is the design of the article itself. The article shapes are typically extracted upfront from your existing templates, or they can be extracted from previously published work, and they are added organically. So when you produce new content, we can detect these new shapes and add them to the library as well.

This results in thousands of possible shapes that the algorithm can work with. In the case that no ideal shape is found, we are working on an AI solution that can automatically modify the shape itself, or in the future, create new variants on the fly. This solution will not change the text or the look and feel of the article. It will change, for example, the size of the image or the size of a quote to make the article fit.

So what is the difference with today? Today, you might have a few hundred fixed templates, but with AI layout automation, you have hundreds of thousands of flexible compositions directly available to you. At the moment, we are rolling out AI layout automation to various customers running various POC projects, and these are some examples of pages that you can create with AI layout automation.

So, let’s go over to the demo video to show you in action how easy it is to create a page.

In this video, we would like to show AI layout automation in action. As you can see, your page planner solution has created the empty pages in WoodWing Studio and already placed the sold ads. The next step is that we are going to place the stories on the page.

We select the pages for which we want to run layout automation and open the layout automation dialogue. At the bottom, we see a list of all the articles which have been written for this issue and category. And here at the top, we see how the algorithm is laying out the articles over the different pages.

As a user, I can now make some tweaks to the design. For example, by changing the story type from a lead into a second, or by changing the aimed page number. When I click update, you see that the story is now moved to page six and has become a secondary story.

Whether something is a secondary or lead story is a creative decision. It is not only based on the number of characters. You could, for example, have a small story with a large article being the lead story.

When you are happy with the result, you can hit the compose pages button. The design is then sent to InDesign Server and the stories are placed on the page. This takes a moment. We can now use the existing process to finish up the layout. For example, preview the layout and open one of the stories in InCopy or in the print editor, or finish the design in InDesign.

With that, let me hand you over to Jeff for WoodWing Connect.

Hi everybody. This is Jeff Gapp, and I am the Product Manager for WoodWing Connect. In a moment, we will also be seeing Paul Walker, but let’s just jump into the presentation here and talk about Connect and where we are.

WoodWing Connect, as we have discussed before in other presentations, is essentially an umbrella term for using our APIs, the webhooks within the Studio and Assets tools, and also the iPaaS tool, which is the Workato piece.

We have continued to refine, and you can actually see Workato here on the right-hand side, our connectors for Workato, as well as, over the last year, adding in APIs for Studio and really working to refine what we are doing in 2026.

We are going to be really working to take items from the partners and customers that they have wanted APIs and events for, and add those in. We are pretty excited about those. So stay tuned for what those are going to be.

Connect is also about a tool, what we call pre-built integrations. We have done quite a bit of work with AI, obviously. We have done some things where you can see Clarify trained a model. We have helped a customer create a model, train it, and use that within their business. So that was pretty fun and quite interesting.

These pre-built integrations that you see here are really starting points. Things like Dropbox and pushing things to Google Drive, right? Those are things that you might want to do just as part of the efficiency within your business or bringing things in.

We completed a project this year with monday.com that we are pretty excited about. Content reuse, ConvertAPI is one that is out there and available, where you can actually take certain kinds of content and convert it into others. The use case here was really for engineering firms, the ability to take CAD/CAM files and put them into the Assets tools with previews. So that is what we were doing there.

We have done quite a bit of work with Studio for going from Studio to WordPress and also from WordPress to Studio. We are not limited to WordPress. It just happens to be the request that we have in. So the centerpiece of the tooling is really quite flexible and can be used with other CMSs.

We also, of course, have, if we look at our WoodWing apps, a PDF Manager. Tom talked about this a little bit before. PDF Manager, the name does not really describe what it does. It can generate PDF files in a multitude of different ways. It can generate XML files, packages, generate PDFs from the publication overview, use workflow metadata from the tooling to pass into PDF so we can make some decisions about that, and some other things.

I am going to go ahead here and play a video, and then we are going to bring Paul in to finish up this particular piece of the presentation. So, here we go. We are going to take a little bit of a look at PDF Manager.

Hi everybody. My name is Jeff Gapp, and I am the Product Manager for WoodWing Connect. Today, we are going to take a quick look at PDF Manager, which is a tool whose name gives away its basic functionality, but it includes so much more.

PDF Manager has core functionality for generating PDFs with configurable parameters. You can create single-page or multi-page PDFs using defined job options, color settings, customizable file naming. You can do preflighting, error handling, getting messages back on errors back to the users. And you can also generate packaged InDesign layouts, export XML, export layout images, and also export images of the pages in PNG or JPEG.

For PDF Manager, the key capabilities, of course, are that we can generate the content, but we can also deliver the content. We can deliver it to Assets 10, Studio Server, an Amazon S3 bucket, or any other configured endpoints.

The workflow support, as we will see in the next slide, can be status-based workflow. It could be a trigger field, so a Boolean field: click it on, and that generates PDFs. And you can use something called the PDF dialogue.

The PDF dialogue is a tool that is part of, when PDF Manager is installed, the publication overview, and it allows you to email content to users for them to be able to review. It could be a single page. It could be an entire issue made up of multiple sections.

Let’s take a quick look at PDF Manager and the functionality. So in this case, we are here in the Studio web application. We are going to see here that we have several dossiers. Now, the easiest thing to do is simply to come into Studio, select the layout, and you can say generate PDF.

What then happens is the process is triggered. If the PDF generation fails, you will get a notification here along with a message that tells you what the failure was. And then you will get the layout set to done to indicate that the PDF file was actually generated.

The other ways of working are to use things like a trigger here. There is our PDF error message. You can also have a little flag here that says multi-page PDF or not. So whichever way you use to trigger the PDF Manager, the end result is an InDesign Server job within Studio.

The InDesign Server job runs, and we can actually see here within Studio Server, this is a list of all of the things that the PDF Manager did with the content that was sent to it. You can see here export PDF was done, archive the PDF, but it skipped export JPEG, PNG, etc., because we did not tell it, as part of the parameters we configured, to do those things.

Now what we can then do, and you can kind of see it right here, Connect PDF Manager, the PDF Manager is sending the files over to Assets. So if we look over here in Assets, we see that here are some files that were sent over earlier, and then we have this notification: the content of this folder has changed.

So if we click update, we get a series of PDFs, and you can see here that in this case, we made a series of single-page PDFs. Again, you can merge them together, and we also have the zip files that represent the packages for the generation of the layouts.

So, in short, that is PDF Manager and the functionality that is available today. Please reach out to us if you have questions. Thank you very much.

And I am back. So, just to finish up with PDF Manager, if you have questions, this is a cloud-only tool, right? It has a series of dependencies, and it is very, very, very flexible. With that, what I would like to do is introduce Paul Walker to the presentation. Paul, I am going to jump on.

Thank you very much. Thank you for the intro. Hello everybody. I am going to talk about three particular products in the WoodWing app. We have, first off, the Content Delivery Hub. This is a Studio product, and it is actually a modular product that will allow you to publish your print or digital articles to any one of your digital channels.

It will collect digital articles. It will reach into your print publications, either from an issue or through a particular brand. And it has a pre- and post-transformation module where you might want to gather metadata from the assets that were on the page, or gather metadata from an external API to enrich the content.

We then have transformation modules. There are several. They are all currently based on XSLT. So you can use that to take the XML, transform that into any particular pattern that you might require downstream.

We then have a post-processing module where, for example, in Studio, you can position the images, but it is using the whole image. You might only see a portion, and then it can crop and process and style, maybe push it to different external image processing services where you might want to normalize the color, and then transport that out the door.

Now, that can go through to an API, it could go to WordPress, it could go through to an SNS notification service. So again, there are different modules. This will allow you, from one single action within Studio, to then publish seamlessly out the door, transforming into the requirements of each of your channels.

All the way through the entire process, there is a notification system, so you can actually see as things are processing, as the data is being collected, and be notified of those transformations as they are happening.

We then have, I am going to skip over to the cleanup service. This is a dual product. So we have a Studio and Assets cleanup service. The Assets one is simply something that is scheduled on a given timescale, can run particular queries, and remove content, tidy up the DAM, keeping it nice for you.

The Studio version, so called the Studio cleanup, can again work with different criteria on brands and the issues on the inside. And that is kind of multi-stage. First of all, based on time, it can come in and lock your issues, so no more work is to be done on this one. Again, it will notify the users, going: this issue is now locked.

At a predetermined time, that can then be archived, and the entire issue can be archived off. And then finally, if you want to create the rule, that archive you could keep for a certain length of time, and that archive can then also be cleaned up.

So those are the Content Delivery Hub and the cleanup service. We also have a third one for today, which is the Workflow Assistant. This allows you to create a tailor-made, role-based panel within Assets. It allows for contextual, informative panels to guide your users through a particular workflow, making onboarding much quicker, reducing the complexity, and reducing errors.

I have a short video to show you, and I shall just start the video now. I will see you in two minutes.

Hi, I am Paul Walker, and I am going to introduce you to the Workflow Assistant. This is a role-based customizable panel inside WoodWing Assets. As well as enjoying all the usual metadata fields that you usually see in tags, we have multiple additional benefits. For example, straight from this tool, you can group.

Not only can you present taxonomies, you can also have information. So for example, in copyright here, you can guide users on what to do, making onboarding much quicker. You are presenting workflow in a human-readable form and then not just dealing with metadata.

This then goes on to being able to provide notes on required fields. So here we have an asset where title, label, subject is required. When they fill those fields in, that messaging will disappear and allow people to publish or unpublish.

As we notice here, this is unpublishable. The user cannot perform the action. This asset here, we can see that this asset is published, and we can unpublish it, but the publishing button is grayed out because there is no need for the user to do that.

We present all of this as a tool for the admins to be able to create, and it is a simple drag and drop. We have information here, and I can drag and drop new functionality, control how I want this to be configured, and present that to the user, allowing you or the consultant working with you to customize panels targeted directly for you and your users.

Thanks for watching. It gives you a little clue. Again, the key thing is keeping it informative. There are lots of different controls there to make sure that you can really craft the panel, guiding the user at every step of the way so that there are fewer mistakes and it is less error-prone in your workflow, which obviously reduces support calls and speeds up the entire process.

With that, I am going to hand back to Magdalena.

Thank you. Thank you, Paul. Thank you everyone for the lovely presentations and demos that you have prepared. I think they were very informative for all participants joining us, which are in a great number.

We did receive some questions throughout the session, and I would start with the first one from Dominic. Hello, can you mention what is for cloud and what is for on-premise? Tom, would you like to answer?

Yes, great question. As you see, it is a mix. There are, of course, some obvious cloud-only features, like everything that we are doing for Assets 10 is, of course, cloud-only. Then there are a few in-between features, like the AI assistants. Those will start cloud-only. We have not made the decision if we are going to release them on-prem. That also depends on the technical capabilities.

For the layout automation, we are also working with various on-premise customers already today to roll this out. So for those, it depends a little bit on their upgrade velocity, but it can work.

Okay, thank you. Another question from another Tom. Tom is asking, can we change the default AI tags? We would like to use AI face recognition to find our employees.

Yes, great question. So yes, this is possible. We integrate by default with AWS Rekognition, but Jeff and team already integrated with a lot of other AI vendors. AWS Rekognition is not the best AI service for celebrity detection or facial detection. For that, it is better to, for example, use Clarify, and we also have integrations available that we can integrate with both Assets 6 and Assets 10.

That is right. The AWS Rekognition, the default one, does text and tags. AWS does have the capability to do facial recognition. You might want to make a different decision, right? It is really up to you how you choose to do it.

We have done, as Tom noted, some work with one of our customers and building a model for them. So we have the process of feeding in the images for the model, being able to correct the model from the UI of Assets, right? So feed in an image to your model, get it tagged. If the tags are not right, you can take away and tell the model that this is not an appropriate tag, or add tags for that matter, so the model can get it. There is a lot of consideration about the question you are asking, and happy to walk you through it if you would like to talk about it.

Okay, thank you. Another question from Darren. This is about the PDF Manager, I believe. Can I create a package of the complete issue?

Absolutely. Yes.

And I think there was another question: timelines for Assets 10 or Studio integration and migration tool.

Timelines are always subject to change, but realistically, at the soonest, it would be Q4 of this year.

Thank you, Dani. Let’s see if we have other questions. I do not believe we have other questions, to be honest. I am looking at all the messages, but I guess that is it.

Yes. Well, if you have any additional questions, feel free to always reach out to info@woodwing.com. Or if you have a direct contact with any of the presenters, feel free also to reach out to them or to your partner or customer success manager from WoodWing. They will be more than happy to guide you through any questions or answer anything that you might be uncertain about.

So yes, I think we have two minutes left until the end. I would really like to thank everybody that joined us today. Of course, you will receive the recording after this webinar live session. I believe we send out the recording within a day or two. So in case you missed the beginning or a specific segment throughout the webinar, you can always return and listen through or watch the demos that were showcased today.

Any last words, Tom, that you might have?

Yes. So we would like to thank you for your attention, first of all. And we are really looking forward to working with you, releasing these features throughout the year, and also making them available to all your users so that they can take advantage of those features.

Yes, thank you so much. Take care everyone, and until next time. See you soon.

Note: this transcript has been auto-corrected using AI, it may contain mistakes