We are going to get started at the top of the hour, but just wanted to start a little bit early as we could see some attendees already joining us in the waiting room. Thank you so much for being on time. We're very excited to have you with us today. We're going to give it just a couple of minutes for people to join. A very warm welcome to the Q3 Product Update Webinar. For those of you who are just signing in, welcome to the Impero Q3 Product Update W ebinar. A really, really warm welcome. So excited to see so many of you already logging in a minute in advance. We're just going to give it another minute or so before we get started to allow people the chance to sign in. I'm just going to give it another minute or so. I can see more people signing in. Very exciting. Welcome if you're just joining us to the Impero Q3 Product Update Webinar. We're going to get started at the top of the hour. We'll just give everyone a minute or so to sign in. I can see the numbers are starting to tick up now, which is very exciting to see so many of you making the time this morning to join us. For those of you just joining, welcome to the Impero Q3 Product Update webinar. Just going to give it another 30 seconds or so for people to be able to sign in. I know some people are running from their morning meetings to join us. We'll get to kick it off in just a second. I can see so many of you joining. The numbers are just ticking up a tiny bit, but we'll get started here as well. Welcome to the Impero Q3 Product Update. We're so excited to see so many of you joining. We're going to get started now. We're very excited to see so many of you taking the time to join us here this morning to hear a little bit more about how we are working to improve our platform for risk and internal control management. Before we go into the presentations for today, I did just want to do a quick rundown of some practical housekeeping. The webinar is being recorded, and we will share it afterwards via email. Do keep a lookout for the email probably in your inboxes tomorrow in case you want to rewatch or you want to share it with any of your colleagues who are also using the Impero platform. We will, as we always do, also share these recordings in the Help Center. Do take a look there as well if you want to ever go back and see any of the previous recordings as well. We do welcome questions throughout the session. Please do feel free to use the Q&A. We will reserve all of the questions for the end of the webinar and try to group them all there. We encourage you to ask questions along the way. I'll be monitoring the chat as well to make sure if any of you need assistance during the webinar to help moderate that. What we'll be covering today, as always, we'll have a little bit of an update on the Impero roadmap. Then we will take a look back at some of our recent releases from the past quarter, making sure that you are up to date on what is happening there, and maybe even can start using some of the features if you're not already doing so. We are going to have a special feature update today on control triggering. Last but not least, we will have David as well joining us to talk a little bit about how we view AI. Before we go into the presentation, I did just want to do a quick introduction to all of the speakers. My name is Jasmine de Guzman. I am the Marketing Director here at Impero. I'm simply just moderating here today. Let's give it over to the stars of the show, which is our amazing tech and product team. Xisi, do you want to do a quick introduction? Hi, everyone. Also welcome from my side. My name is Xisi, working as a Product Manager at Impero. Yeah, thanks for joining today. I'll provide you a bit of an update on the recent releases just in a bit. Wonderful. Thanks, Xisi and Kristian. Hello, everyone. I'm Kristian Jensen. I'm a Senior Product Manager here at Impero. It's really nice to see so many familiar names from the networking days that we had here in Copenhagen. Welcome to the rest of you as well. I'm excited to be here today. Last but not least, David. Hi, everyone. I'm David Højelsen. I'm the CTO here at Impero. I'm going to speak a little bit about how we view AI in Impero in the future and how we comply with the different rules and regulations. Wonderful. Thanks so much. If you've joined us before, you know we love to start off with a poll. We are going to do that today as well. It should be popping up on your screen in just a minute here. The first poll today is we know a lot of you are using Impero for a specific use case or in a specific department. We also know a lot of you are looking to roll out Impero into other departments for different areas that you'd like to do internal controls on. Are you looking to roll out Impero to other departments? Are you already set with your setup? Maybe you're rolling it out into finance, into your tax departments, or your compliance departments. These are probably the three most common ones we see, which is why we have them up here on the screen. We also see people rolling Impero out to other departments to support the finance, tax, and compliance functions. Wonderful. I can see a lot of you are about 50% of you don't have plans right now at this time. A lot of you are actually looking to roll it out into other departments. Very cool to see that. Of course, as always, our customer success and our implementation departments are always here to spar with you as well if you need help. I will close out the poll. I'll just do a quick share of the results in case you're curious as well. We have about 13% who are looking to move more to finance, 18% into tax, 18% into compliance, 10% to other departments, and about 43% of you are not looking to at this time. Maybe you got some inspiration here today from other organizations. All right. I closed out the poll. With that, I will hand it over to you, Kristian. Yes. Xisi and I will be talking a little bit about the roadmap and about the product roadmap altogether. With these webinars, we find it super important for us to actually give an update on the roadmap process. While the roadmap is a living document and living and breathing document that will change, we still want to be super transparent about what we're working on, what we're planning to work on, and what has already been released, and so on. Could you do next slide? Thank you. Of the massive, really major releases that we've done, we've released the control testing module, which we'll be going a little bit more into detail with later. We'll also be going more into detail to control triggering, which since last time has now been out and living with multiple customers actually using it in their production environment. I'll be talking a little bit more to that as well later. We have, as most of you, I'm sure, have already seen, released a dashboard where we are doing continuous improvements on improving the dashboard to all the various feedback that we're getting to make sure that it caters to your needs as well. If you can go to the next slide—oh, no, sorry, wait a second—we have also been working more on AI prototypes within Impero. As mentioned, David will go more into detail around how we make sure to comply with various regulations and so on, and also our overall process on it, our overall thoughts on it. We have done some various improvements on our internal side to make it a lot easier for us to do AI prototypes. One of the things that we have tried, and I know that the people participating in networking events have already seen a little preview of this, but we'll also show it here, is a simplified way of basically getting a start to write a control based on the input that you have on the control program and based on the input that you have of the idle of the control. We have, yeah, we're tinkering with these sorts of ways of making people creating controls or people performing controls a lot easier. We'll go into a lot more detail on that in the future in this webinar. We are working continuously on various things regarding our architectural excellence to make sure that we are consistently having a very strong platform architecture and so on. One of the areas that there's been a lot of change on, I think, and a lot of movement on also is within our integration and connectivity. We have done some changes to our customer-facing APIs. People that have an API integration with us are probably already aware of that. If not, this is also a way for us to communicate these things where you can now see your task within your API integration or pull it from us. We are working also on including the future activities, making sure that you can see what's coming up for activities in the API. We are working on improving our Power BI connector. There are various things we can do there. If you are using the Power BI connector today and you really want us to consider some of the things that you have been struggling with, please let us know. If you're looking into doing this in the future, reach out, please. Of new things, we are looking into how we can do better user provisioning, for example, using Azure AD. Creating users within the Impero compliance management platform that are aligned with your existing Active Directory and so on. I'm not sure if it was specified that we were considering doing a SAP connector in the last webinar. If not, it's here. If you are using SAP today and you're struggling with the integration between SAP and Impero, please let us know what your challenges are so we can also maybe go into a deeper dialogue with you on improving those areas. Going back to the first part, in the internal controls and risk management enhancement, we are now officially starting to work on entity management, better handling of entities within Impero. This is something that we have heard a lot of feedback from various customers. Of additional things that we are starting to investigate and how we can do it better is issue management, raising issues within Impero relating to controls or risks. Today, this seems like a natural extension, especially with the release of control testing, where after a control test is no longer seen as not effective for whatever reason, the most natural part is to create an issue based on this. This is still in the planning phase and something that we're looking into. If you have a lot of input here, please let us know. We are more than happy to help you and to listen to your feedback. I think that's everything on the roadmap here for now. We'll go into the recent releases where Xisi will be talking a little bit about the recent releases. Perfect. Thanks so much, Kristian. I can see we already have some great questions coming in. Please do keep those coming in as we go along. Xisi, over to you on the recent releases. Yes, thank you. I will start with an update on the latest release in September and then hand it over to Kristian again to give you more insights about the control testing and the control triggering. For your overview, here are the highlights of the September release. As you see, we have focused on improving the information and the communication flows for controls, but also made it easier for you to deal with the control documentation, besides the improvements to user experience that we just continuously work on. Now let's just walk through the new functionalities together one by one. Next slide, please. As a part of the control editor, we have now added the functionality to set up notifications about the control completion. Before this release, it was only possible for control reviewers to notify performers about the approval of controls. With this release, further stakeholders or team members who are not actually directly involved in the control process can also be notified automatically when the controls are completed. This can be very quickly set up in the control assignment section when creating or updating a control. With that, it's no longer needed to send manual notifications via email. You can just make sure that the control results are reviewed immediately in urgent cases, or you can unblock further workflows or reporting that are dependent on the completion of certain controls. Generally, this is a feature that you can use to make control results more transparent in the organization and to raise awareness and confidence. Next one, please. Also, as a part of improving the information flow, we have worked on enhancing the visibility of pending control tasks. As you know, many performers submit their controls without logging into the platform. Until now, they just referred to the pending tasks in the email notifications they have received before. From now on, once control performers or reviewers submit the control, they will see other pending tasks right after as a friendly reminder. They have the option just to work through their to-dos by clicking on each of the pending tasks. A further feature we have introduced this time is the support for bulk downloading control attachments. With this feature, you can just mass select multiple control activities to download all the files submitted by control performers or reviewers after you have filtered out the relevant programs and controls and set up the needed time period in the control activity list. All attachments then will be available in a folder structured by programs and time periods. You can very easily associate them with completed control processes. The last part of the September release I'd like to share with you are some small improvements that we have implemented to improve the quality of your daily life, so to say. After receiving a lot of good feedback on the new dashboard, we have also now introduced the sticky filters in the dashboard that many of you have asked for. These filters now auto-save for each individual user. We have rolled out the pagination feature across Impero, so the navigation becomes smoother for you. From here, I would like to hand it back to Kristian again for more on control testing and further feature updates. Yes, thank you. For control testing, we already have multiple customers using it today. For those of you that are struggling with maintaining effective and efficient internal controls, maybe it's something that could be relevant to you to reach out and hear how we can actually use or how you can use control testing as a way to hopefully avoid risk materializing. I do want to highlight the demo or the tutorial here that William has made that you can scan using the QR code. I'll also talk just a little bit about control testing altogether. Control testing is a way for you to identify weaknesses and gaps within your internal controls. It's straightforward to set up multiple control tests that are already following your internal policies around how you want to sample controls. We did make it generally available from July 30th this year. It is not per default enabled within your production environment. If this is something that you're interested in trying out or if you're interested in what it can actually do to help you with maintaining effective internal controls, then please submit here to the poll that will happen in a few minutes. We'll make sure to reach out. Yeah. Awesome. Thanks so much, Kristian. As you mentioned, there's already several customers using it. I see we also got a great comment in the chat that someone's already using the bulk downloading of control attachments and that they're loving it. Fantastic to see that so many of the features that we are releasing are being adopted. If you're not adopting them yet, please do let us know. We are always very happy to help. On top of that, we are also trying to make sure that if you need help, we have quick video tutorials. Myself and the marketing team have been working very closely with William from Implementation to make sure that we are putting out tutorials for you on all the different features that we have. Again, really open to hearing requests. If you'd like a tutorial for something specific, do let us know. We will also be putting out a tutorial in the upcoming days about the new control completion notifications. Do stay tuned for that. You can also scan the QR code here where we actually have a playlist with all of the different features and tutorials that are available. We'll continue to add to that one. That could be a good one to bookmark as well, either for yourself or for any other Impero admins or frequent users in your team. Kristian, before we jump into that poll, you were also going to tell us a little bit about control triggering. That's something that I know we're all very excited to hear about. Let's jump into that. Yes, thank you, Jasmine. As mentioned during the product roadmap slide, we have moved control triggering from being something improper to actually something that we find that we see as ready for customers. We already have the first few customers actually using it within their production environment. For those of you not familiar with control triggering, it is basically a way of moving away from calendar-scheduled controls or people being only reliant on the calendar year to perform controls, to then moving into more of a dynamic environment where you make sure that when control A is finished, control B can start right away. We would love to understand a lot more around how this could be used for different use cases. Today, it is possible for you to set up controls that are being triggered. This is also not something that is enabled by default within your environment. Similarly, please reach out if this is something that you find useful within your environment. I know that we'll also be working together with William on creating a demo of this so you can see it in action before just enabling it within your environment. Similarly to other or existing controls within the Impero compliance management platform, there is still a clear traceability of why or when a control was executed. Everything that you come to expect from the Impero compliance management platform is also readily available within control triggering that we have today. Awesome. Yeah, I think that's everything on control triggering. Perfect. Now that we've gone through that as well, I will launch that poll that we did mention. Just give me a second here. It'll be popping up on your screen. It is simply just if you are interested in getting the control testing module enabled, let us know. We'll make sure to reach out to you if you're curious about exploring control triggering. The last one we haven't actually talked about, but it is something that we did send out an email about to all of our customers, all of you, last week. It is about provision 29 of the U.K. Corporate Governance Code. These are some new legislation and regulations coming into effect at the start of 2026. If you do have a large U.K. subsidiary, it is something that you at least want to be aware of. Therefore, we mention it here as well. Do check out, we have a ton of blog posts on our website about it. We also have a great readiness checklist as well. I can see some people have answered here. I'll close that out. We just got one more answer. I'll just close that out now. We will follow up with you for those who have answered. We are now moving into the last section of the webinar. Before we jump into it, I'm actually going to launch one more poll. This is around the use of AI in your work of risk and internal controls today. If you've been following along in our webinars, you'll know that we actually asked you this exact same question in Q1. It was very interesting for us to see the results. There were a lot of people who were not sure. There were also some people who did not use AI in this domain. A lot of people were looking into it. We are now six months down the road from that webinar. I think just in general in the landscape of the world, how AI is being viewed, how it's being adopted, I know I see a lot of CFO-centric newsletters talking about this is probably one of the top priorities for a lot of companies. We did just want to do another kind of status check-in to see where are you at now? Has that feeling in your organization changed into how you wish to see AI? We have a couple or quite a few answers, a few more ticking in. I will share the results because I'm sure it's very interesting for everyone. All right, I'll close them out. Just to share the results, it does seem like about 15% of you are actively using it. Very cool. We'd love to hear how. The majority of you, which is similar to, but I think this is actually a higher degree than in the spring, 54% of you are looking into it. 7% of you don't wish to use AI in the domain. That's actually significantly less than when we did this poll in the spring. About a quarter of you are not quite sure yet. You know what? That's OK. That's also why we do talk about it on webinars like this, so that you do get a little bit more thoughts and insight and thinking about it. We also know that and are aware that in some organizations, it is something on an organizational level that needs to be discussed and not only in your department and your focus on risk and internal controls. With that, I'll hand it over to David to dig into this topic. Perfect. Perfect. Thank you. Really interesting poll results, I think, going from 20-something percent to 7% in not wishing to use AI. I think it's some of the considerations that we are bringing into our product development as well. Of course, we would be really happy to get direct feedback on anything that relates to how you see AI being used inside the Impero platform. Please go to the next slide, Jasmine. Simply how we in Impero view AI, it's not a construct that should automate everything. We would rather see it as assisted driving as opposed to completely fully autonomous driving. We have a few rules that we've set out internally when we look at what features that we experiment with and what we want to build. Basically, AI should free up time for users to focus on what really matters. That could be helping extract data, give better context on the data that is in the platform in order to help operators better act on the controls and the control programs, but also the control results that are put into the platform. We would like that AI acts as a guide and support tool, never a replacement for judgment. What we mean there is basically that we should not just hand over the control of the entirety of the platform to AI. It will always be something where it's easily leveraged and suggested inspirationally only. Basically, AI should suggest and a human should validate. AI should also be readily available and trustworthy. Trustworthy? Trustworthy? The meaning behind that is that we know that a lot of users are currently using free versions of LLM models on the side, updating content and putting it into Impero, which is potentially a major leak of confidential data and other things. We would like to provide an in-tool assistance for that where we can validate in a compliant way the use of AI, even from a chat model dialogue in order to get assistance in the platform. Lastly, AI should basically ease control completion. That could be normalizing the way that controls are written, tasks are built. It could also be in-context descriptions of controls. First time you fill out a control, having an assistant being able to explain why you would need to fill out this control and what would be important and how other people had potentially done it. Those are some of the governing principles of how we view AI tooling that we will put into the platform. We do have quite a long list of ideas and prototypes that we are actually working on. We're looking forward to showing you all some of that in the future. Next slide, please. With all of that said, AI also raises quite a bit of concern. What happens to data, especially in a platform like Impero, where a lot of sensitive data is uploaded and potentially controlled and accessed by AI? What we strive to do and what we basically committed to doing is completely commit to our customers that we, of course, obey all the rules with regards to the E.U. AI Act. We have more about that that you can read in our Trust Center. To frame it, our core principles are that all AI features, they'll never be enabled by default. You've probably seen a lot of platforms where suddenly an AI feature appears or data has been used. That will never happen in Impero. That is something that we will guarantee. It will always be by a customer asking to be enabled and having AI enabled in the platform. Customers can always opt in and out at any time. If you don't want the feature anymore or don't give access to it, you would always be able to opt out. We also commit to having clear, transparent communication both to our customers, the operators of the platform, but any user in the platform should be able to see clearly in the UI when AI is active and when content is actually generated by AI or any AI features in use, basically to distinguish between the autonomous driving or the assisted driving. We always have a clear scope of what we will deliver in that sense. No customer data will be used in training AI models. We have completely watertight shutters between the data that you upload and how we use and train specific models. That is completely separated. There will be no cases of customer data being used to train AI models. All data processing will be compliant with GDPR and basically any other applicable privacy laws. We would never use or leak any of this data to models that are not authorized to handle that type of data. Any third-party AI vendors also have to live up to these specific standards, which is extremely important. That's basically some of the rules governing how we pledge to work with AI securely in the Impero setup, but also giving a little bit of context as how we envision AI being helpful in your day-to-day work within our platform. If there's a need of clarifications, of course, always feel free to reach out. Our E.U. AI Act policy is, of course, available on our Trust Center. Please go and check it out. There's also a lot of other great content in our Trust Center. That's pretty much it. Thank you. Wonderful. Thanks, David. We're going to get into the Q&A. I can see we've got some great questions already. I also just want to do a little shout-out and promotion for we are putting on a 2026 trends survey right now. We'll send that in the follow-up email. We're collecting input from all of you that we'll put together in a little mini report and share with all of you because we think it's really important to share knowledge, making sure that we're distributing. Please do feel free to share anything that you think is happening within the next 12 months in the governance, risk, and compliance space so that we can continue to share knowledge with each other and continue to push the to the next level. I'll also mention that we are looking for brand ambassadors. If you are looking to boost your own personal brand within the risk and control and compliance space and would like to work with Impero as a brand ambassador for us, do feel free to reach out. We'll also put that in the follow-up email. As I mentioned before as well, just did want to remind you and make you aware about provision 29. Again, it might not be applicable to your organization. I think it's always something that when you're operating on a global scale, it can be very difficult to stay up to date on legislations. That is also when we're working with customers. We know that this is a big focus area for some of them. We do just want to continue to share that knowledge as well to make sure that you're as prepared as possible in your risk and control setup. We are also going to be joining some upcoming events. If you did not get to join either our fantastic networking event in Germany in the spring or our big compliance curated conference that we had just a little over three and a half weeks ago here in Copenhagen, you can also meet us at the Tax Operations Conference in Dortmund next week. We're also doing a great webinar with the German Compliance Manager Association with Pascal Heck from C&A a couple of weeks from now. We'll also be at the Tax Technology Conference in Germany in November in Frankfurt. We'd love to see you there if you happen to be attending. I will also note that you can save the date already for our end-of-year product update webinar, which will be just like this, but a bigger wrap-up of the year, which we'll be hosting on December 11. We will send out an official invitation approximately a month in advance or so. I just want to share that date already with all of you because we know the end of the year does end up being incredibly busy. We will record that one as well as usual. If you can't join us live, you can always watch the recording. Before we jump into the Q&A, the final poll of the day that I have for you is related to some of these things. I will launch that one now. Let me just close out the other poll. It should be live on your screens. It's not cooperating with me for some reason. Maybe we'll come back to that one in a second. We'll come back to that one in a second when I figure that out. Let's jump into some of the Q&A then. The first one is related to AI. David, this is for you. I think you've answered it a little bit, but I think it's always good to reiterate. Will AI have access to our data/environment in Impero? Will AI be trained based on our data? We have confidential information, so we are, of course, not interested in giving AI access to that data. AI will not have access to any data unless explicitly given. It's not that enabling AI on a tenant will let AI crawl through all your content and figure out what to do with it. It's basically the opposite way. There is a model that has an API. If you want to address that, you would, for instance, in making a control description, feed that specific data one time into that model, and the result would be given back. The short answer is no, it will not have access to all data. The data access is completely limited. Super. Thank you, David. We have one more question here about AI. You mentioned that it's not going to be trained on customer data. How will it then be trained? We are basically using off-the-shelf validated models that have the base knowledge of an LLM. We will be able to train it on specific frameworks that are not related to any customer data, feeding it descriptions of specific control frameworks or legislation or other things. That will be structured in a vector database that will allow that model to understand the context one to one. When you give it a specific question, it will utilize that data. We are not, in a sense, training any models. We are giving them context, but not the context that is your data. It's generic content that you would be able to find online on, let's say, specific frameworks or other things. Perfect. Thanks, David. The next question, I think, is for you, Kristian. It's related to entity management and the roadmap. I can see that the entity management feature has progressed from a planning state to in-progress state. How are you progressing with the development? When can we expect it to be released? I, as a marketer, would probably ask you that myself. I probably know the answer. Stay tuned for this product update webinar, but next one. Kristian, I'll let you respond to that as well. Thank you. The short answer is that the entity management will be rolled out in various phases. It will be rolled out on a per-tenant basis for now. I'm not ready to share a public timeline of the specific development process, but it is one of our top priorities right now. If you are sitting in an internal controls environment as of today and you're really missing the functionality, then I would urge you to reach out. I'll make sure to get in touch with you and see how early we can start having some of these phases rolled out to your environment. I hope that somewhat answered the question. That's awesome. It's just wonderful for us to see excitement about some of the features as well that we have coming up. I will also just note to the person who asked this question, you submitted it anonymously. We can't follow up with you. Please do as well reach out to us so that we can get you in dialogue with our team if that's something you're interested in. We have a couple more questions, but they're more pieces of feedback. I know we can't necessarily distinguish between feedback and questions in the Q&A section of Zoom here. I will keep some of the feedback and make sure that it is passed along to Kristian, Xisi, and David. We have a question for you, Xisi, about the notification of the completed controls. Regarding the notification of completed controls, we have a number of subsidiaries that perform a certain control. When the deadline is reached, we check to see the response, but some respond after the due date. Is it possible to set up a specific notification that we can receive only for those who submit after it's due so we don't have to check that manually? Thanks for the question. The current version of the feature does not support that. The notification on late control submissions is not available, but we would like to hear more feedback from you on that specific use case. It might be an interesting add-on, be it for this notification feature or as a part of the reporting module. Great. We have some good questions. Thank you, Xisi, for answering that. Kristian, we have some questions for you about the control triggering. The first one is simply, is it released now or not? If you could provide some clarification on that. Yes. Right now, control triggering is available to be enabled within your environment, within your tenant today. It is not enabled per default. If, after hearing about control triggering or if you want to know more about it and it's not currently enabled within your tenant, please reach out. We'll make sure to give you a demo and to showcase what it can do. I see there's also a question about control triggering and testing, control testing being made available live. The same goes for control testing. Control testing is currently available and in general availability. It is not enabled per default. If it is something that sounds relevant to you, I urge you to reach out. I'm sure that we can facilitate a demo and run you through the entire module. Perfect. It's actually good that you picked up on that, Kristian. There's actually one more about the triggering functionality. Will the triggered control preparer know whether the control was triggered by the first control completion or by scheduled timing? default is that the control performer will not necessarily know whether it's due to the calendar sending out the control or whether it's due to the previous control triggering this control. I said control a lot of times. If there is a use case for that, I would love to hear more about it and understand why if that's wanted or that's unwanted. I'm sure we can try to see if we can figure something out. However, within the event logs and so on, and making sure that you have full traceability of what's happening, you will be able to see what occurred on a specific control and control A triggering control B and so on. It is definitely something that we're logging. The control performer per default will not see this distinguishing between the two. All right. Super. The next one, I believe, is also in relation on, can you elaborate more on the possibility to have a procedure for control or process? I'm not sure I understand the question. Otherwise, maybe we can have the person clarify in a follow-up. Yeah, I'm not sure I follow fully either. Fair. We'll make sure to see if we can follow up with that person. All right. Someone's wondering if control testing is part of everyone's agreements. It is an add-on, which we've communicated at several different webinars before. Control testing is an add-on to most agreements. Please reach out to our team for more details on that with regard specifically to your agreement. We also have, just conscious of time, but we can squeeze in a couple more questions. Xisi, this is for you again regarding the due date changes. The person was very supportive of the idea of the late controls that we previously discussed. It would also be very beneficial for due date changes on activities to be even more simplified. If an activity is not ready to be submitted, it is very cumbersome to have to move all the data and archive an activity that simply needs a couple more dates. Is that on the radar? Yes, it is. Generally, we have heard about it quite frequently and are trying to understand the different use cases and reasons for the control postponement so we can come up with a better suitable solution to avoid this kind of manual archiving and reopening of controls. Thanks for bringing it up again. Super. We have a question for you, David, around AI. It might be a combination of you and Kristian. When will any AI-related features potentially be released to users? We don't have a set time yet because we are in this experimenting mode. We are quite far, basically production ready with some, but we do have considerations that we would like to address first. I don't know if you can elaborate a little bit more, Kristian. Yes. Currently, we have working prototypes and so on. In theory, we could just enable it for customers today. However, we really want to make sure that we nail the value for customers before enabling it. We are holding back a little bit. I think it was Matthew reaching out. Matthew, if it's something that is super relevant for your organization, then I'm sure that we can figure something out. For now, we're holding back a little bit until we feel super confident in the value, not just for the customers, sorry, for everyone involved within using AI. I hope that answered your question. Super. We have one last question for you, Xisi, and then we will wrap things up. Xisi, is it possible to set up that Impero automatically sends reminders to all due controls on a weekly basis to the responsible person or the reviewer, depending on who it is awaiting? I think probably you, whoever has asked this question, are aware of setting up multiple reminders in the control editor. That would not be on a weekly basis, but depending on if the control is due for three or five or more days, that would be an option if it's not in use. We would be also interested in thinking of extensions in the future. Great. The last question that I can just see that I'll just address before we wrap up here and just say thank you is there's been a couple of questions about whether control triggering is an add-on. Please reach out because it depends on your contractual agreement with us. We can't give a blank answer on that. Please do just reach out individually for more details on that. Unfortunately, I could not get the last poll working. If you are interested in giving us a G2 or OMR review, participating in a case study, or becoming a brand ambassador, please do feel free to reach out in the email that we will send out tomorrow. Like I mentioned, or as I usually do, you can follow us on LinkedIn. We also have our different newsletters, which I think most of you who are on this call are already receiving. We are also posting lots of great things on our blog. Make sure to check out our different resources, including the Help Center as well. With that, we just want to say a really big thank you. We will see you all on the 11th, no, yeah, 11th of December. Thank you, everyone. Wishing you all a wonderful day. Thank you all. Thank you. Thank you.