Hello, everyone, and welcome to the Impero Q1 product update webinar. We are very excited to see so many of you already on the line joining us. It is just about a minute until the top of the hour. We're just going to give folks a minute or two to kind of sign on. We know a lot of people are joining from other meetings beforehand, but happy to see so many of you joining live and already ticking in. Welcome. For those of you just signing in, welcome to the Impero Q1 product update webinar. We are so excited to have you here today.
It is just about to be the top of the hour, but we're just going to give it a minute to let everyone sign on as well, just to make sure that everyone has a chance to join if you're running from another meeting. Great to see so many of you already logging on and joining us live. We're very excited about that. For those of you just joining, we're just going to give it one more minute or so to let people, giving them the chance to sign on. I can see the numbers of participants continue to go up. Super wonderful to see so many of you joining us live for this Impero Q1 product update webinar. All right, just about another 15 seconds or so to let people sign on, continuing to see the number of participants go up.
That is absolutely fantastic. So wonderful that so many of you want to spend some time with us this morning to hear about our platform updates. With that, I think we're going to get started just so we can keep within the time limit as well. Welcome, everyone, to the Impero Q1 product update. We are so excited to have you here today. Before we jump into our presentation, we did just want to go through a few quick housekeeping items. This webinar is being recorded. If for whatever reason you're not able to stay on the entire time, we will also share the recording afterwards in case you want to share it with other team members of yours who are also working in the Impero platform.
We will also put the Impero Q1 product update webinar in the Help Center, as well as any other product update webinars that we do both in the future. If you join us in December for our End- of- Year Product Update webinar, you can also find that there in the Help Center. That will really be your go-to resource going forward, where you can find all of these webinars so you can have a look back if you're onboarding a new team member and want to get them up to date on what the developments have been in the Impero platform. Do feel free to use the Q&A button to ask questions live. We welcome all your questions. I will just note that we will address all of the questions at the end of the webinar instead of throughout. What can you expect from this webinar?
We are going to be walking you through our focus and roadmap priorities going forward. Of course, also doing a quick recap as well on our Q1 releases on the features and functionalities that you might not have started using yet. Xisi is going to give us an intro to that. Of course, a feature update on the beta of control testing, which Morten will give us an update. Last but not least, we'll do that Q&A that I mentioned before. A quick introduction to the team. My name is Jasmine de Guzman. I am the Marketing Director, and I will just be moderating the session. I'll let each of our other speakers quickly do a quick introduction. David, would you like to go first?
Sure, of course. I am David Højelsen. I'm a CTO in Impero and responsible for product management, design, and engineering.
Wonderful. Thanks, David. Xisi, would you like to go next?
Yes, I'm Xisi, working as a product manager. With Impero, I've been already for a bit more than three years now, and really happy to meet you all today and to share some of our new features.
Awesome. Last but not least, Morten.
My name is Morten Nielsen. I've been a part of the Impero journey for nearly 10 years. I am the Implementation Director here, and that meaning that we handle full implementations and also, the support as well. Pleasure to be here.
Wonderful. Thanks, everyone, for the intros. Before we get started and dive into the content for today, I did just want to do a quick little poll. You're going to very shortly see a poll launching on your screens. We'd love to hear about what functionality is most important to your future work with Impero. Is it enhancements to the risk management module, being able to better document items there? Enhancements to the internal controls section, making sure that you can proactively send out those controls? Is it better reporting and data insights, being able to use our reporting module to better report in your organization? Or, last but not least, is it third-party integrations such as webhooks to be able to connect Impero to other systems? Just going to leave this up for a couple more seconds.
Of course, this might not be the main, you might have other priorities than these ones, but we just wanted to get a quick read on how you guys are planning to work with the platform in the future. I can see that quite a few of you have answered. I am just going to give it two more seconds, and I will close out the poll. Happy to share the results as well. Seems a big spread, but definitely a big priority on enhancements to internal controls, about 43% of you. 30% of you are very interested in better reporting and data insights. Then enhancements to the risk management. Last but not least, with only around 9-10%, the third-party integrations. Thank you so much for sharing your thoughts and priorities with us.
We really appreciate it, and it's very helpful in our product and roadmap discussions and developments. With that, I'm going to hand it off to David, who's going to talk to us a little bit about our focus and roadmap priorities.
Sure, definitely. Thank you, Jasmine. Yes, I'm going to take you through a little bit of our thematic roadmap and which priorities we are working on, and how we will work with a roadmap going forward. Jasmine, please, next slide. We have decided to lean towards a thematic approach, meaning that all new features, everything that we hear from you as customers, everything that we uncover as relevant, we will have to tie to six different themes that we think is most important for the Impero platform. I'm happy to see that at least, for the winner of the poll, that internal control and risk management enhancements are definitely a key theme here, that we will be producing features for and more functionality. Performance monitoring data insights goes hand in hand, I guess, with number two. That is quite good to see.
We're also working and actually already have, artificial intelligence and machine learning inside the development environment of the platform. However, we are very cautious with the regulatory requirements and, really keen on getting your feedback on the potential usage of artificial intelligence, making it as secure and as good as possible, within Impero. We're working hard on achieving architectural excellence, meaning that we want to adapt the architecture and the infrastructure of the platform to better align with the development process, the product management and development teams in order to be able to quicker put new features to the market. Naturally, many of these also involve user experience and user interface improvements. That is naturally key.
Lastly, we are working on integration and connectivity, in order to make sure that we can export better, connect to, potentially, external systems, especially in workflow scenarios, like, like SAP or other systems. That is the key, or the main, themes that we are working on in Impero. Jasmine, if you would take the next slide. We've divided into three top categories, and you can see the six themes underneath. These are some of the features and improvements that we are currently working on. Everything in green is what is being actively working on and is planned for release. The yellow ones are planning, and that means that we basically can shift priorities and we can push things back and forth in the different timelines.
Going through the green ones, many of you, or some of you at least, have heard about our control testing MVP beta that we launched in January. We've had a lot of feedback. Morten is going through that later in this call. We are working on the general availability of that, putting some of the most important missing features into that, as we speak. We're working on sequential control triggering, meaning that we're taking controls from being triggered only based on time, to a scenario where you can attach controls to one another and thus produce small flows of controls that will trigger one another. We're working on bulk operations and automation, making it easier for larger enterprises to manage the platform and the data inside the platform.
Quickly going through, the architectural excellence points, we are building in better observability into the platform. We are strengthening our hosting infrastructure, and we are working hard on basically optimizing our front end and back end, the way that our code interacts with our internal API. That is all in order to be able to produce relevant features, faster and faster. Other than that, quickly going through some of the pending or planning items is defining and managing master controls, enabling better overall structuring of controls for sub-entities or groups, so you don't have to, once a master set is built, have to sit and tweak controls later on. It's a dashboard for better performance overviews. Naturally, it's AI-generated control descriptions that we actually have a really good working internal prototype on. It's improvement, improving engagement and control performance.
Lastly, it's connectivity through webhooks, which is to some extent tied to sequential control triggering, meaning that if a control is set to trigger, then we can also fire events outside of the system. You could start a workflow in SAP or other external systems. This is, on a larger scale, what we are working on currently and the coming time. We naturally have a ton of other features in pipeline, and we are constantly on a release cycle basis, reassessing what should come out next and what the priorities should be for those specific features. That's basically it for this quick rundown of the themes and the items that we are currently working on.
Wonderful. Thank you so much, David. With that, we're going to hand it off to Xisi to give us both a sneak peek at some upcoming features as well as a recap of our Q1 releases so far.
Yes, thanks, Jasmine. I'm going to show you a bit what we have been working on in the first quarter, but also a sneak peek into one of the upcoming features. Let's start with the preview of the upcoming functionality to support you to send immediate controls. At the moment, we only support recurring or manual controls with notification date and time in the future, but not sending out controls immediately. However, we have learned from you about the different use cases that would require the platform to support immediate controls. For example, you need to collect some build documents in an ad hoc manner, or there are, yeah, at the year-end controls that are only one-off. Some customers are implementing the audit recommendations today in Excel or with a, yeah, less convenient workaround in Impero.
You have added some new entities and controls, but that is after the regular notification date and time. With this feature we are working on, we would like to better support these use cases. You have an easier workflow to handle irregular controls, so it is faster and more intuitive, and this should help you to have all the documentation in one place to reduce frictions during different audit processes. Besides that, we have also been working on the feature Copy Risk Directory. We have recognized it is a very frequent request from customers or partners for their initial onboarding or the further rollout process. This feature is especially useful when you need to actually apply the same risk register or assessment framework on different corporate groups or divisions.
You just simply like to apply the same assessment factors on different processes or risk categories. All of that is just to make sure that the same management standards are, yeah, in place across the organization. We are now supporting the copy in each risk directory, as you see here. This copy includes, yeah, other risk registration information. I think you can go one more, Jasmine. Such as the names and the descriptions and also the risk assessment structure, including all the standards, so default and also custom factors you have defined with us. With that, you can very quickly multiply the existing structures yourself and make further modifications based on them. Other than that, we have been also further improving the usability of our platform.
For example, you see here in the control program, we are now supporting your personal saved view, meaning you can choose between the gallery or list view in the program and also display the controls in the split of a tag category. Which would be one of your control attributes. Like here, you see how many manual controls there are and, yeah, automated controls there are in this specific program. Yeah, you, after that, your view is saved. You will see this again when you re-enter the program, of course. Also, we have, yeah, been working on a smoother navigation in the event log. That will be the next slide. With the pagination, now it's much quicker than before to investigate changes within a long time span of one or more years.
For example, you want to know what has been changed on a specific control, you would search for that control in the search bar and check for changes in this log, yeah, depending on if it interests you to look back one year or several years. Lastly, we have been also improving the way we provide instructions on the task-based report. Many already use the status report, but the task-based report does not only inform about the operational performance, but really the actual answer distributions in the so-called radio button tasks. You can really evaluate the control results in a more qualitative manner. For example, here to indicate the control effectiveness based on how many instances have been rated as effective or not effective.
Yeah, we hope to get you started more easily with the in-app video explainer and also tooltips when you start creating the first task mapping. That is a recap of some of our work in the first quarter. I would like to give it back to Jasmine again.
Thanks so much, Xisi, for walking us through that recap. I will have a slide a little bit later, but in the task-based reporting as well, we have a new tutorial video, which is a great way if you're interested in getting started. Stay tuned for that. Before we jump into that, I'm going to let Morten walk us through some updates on the beta of control testing.
Thank you for that, Jasmine. As David mentioned, we kicked off the beta in January with some of our beta customers. Luckily, we've gotten a lot of very valuable feedback. If you jump a slide, Jasmine, we have made a little bit of an overview of what we have learned so far. Luckily, a lot of our customers are using the control testing module in a very similar way, meaning that it's been a lot easier for us to refine, okay, how should this feature actually work and how should it look also moving forward?
It provided us, again, a whole lot that not only on how it should look going forward, but also, okay, how does it actually fit these different use cases that we see in sort of in real life and not only in how control testing should be in theory and how could we basically match our functionality to make as good as a fit as possible. There were some key things that we identified that it's really important that we have a clear result list when we are setting up these different tests. I'll get a little bit back to that, but basically that you're able to get an exact overview of the outcome of the different tests when you are setting it up. The same goes for these bulk test creations here now in the beta.
We have mainly tested out smaller workflows and smaller tests, but when we scale this up, also some of the feedback that we've gotten back here is that there's a lot of tests that need to be performed in a lot of different entities. We need a smooth way and an easy way to set up multiple tests at once. It's been a really good process. We've learned quite a lot. If any of you who are here participated, we really, really appreciate it. It's also been a good way for us to decide on, okay, what way do we want to take this also moving forward? Let's have a look at the current state of the control testing. I'll just share my screen. With a bit of luck, I succeeded doing that also in the right window.
I'll just make sure that I'm still here. All right. Basically, we're still in the beta phase, meaning that there are some things that we know we are still missing and refining a little bit. This also means that it's not available for all of you yet. As you can see here, it will be available in the menu. We have our control testing icon here. Basically, what I can see here in this overview is my individual control testing program. Programs in this approach here, as you can see, we've set it up for finance purposes. We have our 2023, 2024, 2025 testing programs. This is basically how we envision this to see and also how it matches with the way our customers or the feedback that we have gotten in the beta process so far.
Now we are in the beginning of 2025, so we can have a look at 2024 in this case here. As you can also see a sneak peek on here, there are some tests that have already been created. This can be, for those of you who are really familiar with Impero, it can be compared a little bit to how these control programs actually work. As you can see over here on the axis right, it's also on this level. We basically control right who has access to what data. Let's try to open one of them. As you can see here, there's a bunch of different tests that have been populated here with the name, what entity is it that we want to test. There's some tagging again for those of you who are familiar with it.
What is it that we want to sort on? What is it that we want to report on maybe at a later date? Who is it assigned to? When is the due date? If we just have a look at, we can search through here and say, okay, we want to go through a test here of the bank reconciliation. I have prepared it a little bit here for the one for entity 100. It would look the exact same when you are setting up a new test from scratch. Clicking the create test up here in the upper right corner. Basically, on this dropdown here, you will search through, okay, what are the available controls that you have in Impero? We can have a quick view here if we want to see, okay, how is it actually set up? How is it actually defined?
I can see the tags with responsible, etc. This is from the control setup page. We inherit the tags from the control. This could be as here. Okay, it's from bank and cash. It will also be as this our key control. Is it preventive, detective, etc.? All the tags that are basically linked towards the control will be pre-populated here. There are some things that you'd like to add for control testing reporting purposes. It's also possible from the tagging mechanism here. It's the same library as what you're used to to add tags to your actual test. There is a title. We default to a CT colon and then the name of the actual control. I'll get back to this later as well.
As I already sneak peeked, this is to accommodate the bulk creation feature that we are looking a little bit into as well. We can basically mass populate these tests. There is a description. That is optional. These are basically the basic details of this test here. Now we need to say, okay, what is it actually that we want to sample for this test here? We can search through, again, using our tagging mechanism. In this case here, we wanted to filter out this specific entity. I can just do it here so you can see how it works. We can search through the entities in Impero. We can mark this off. Then we define the period. I decided here for a full year. You know that some of you are doing this on a quarterly basis or half-year basis.
You define that in your section here. It could be, okay, this was actually October to December. Define that in your setup of the actual test. We're designing some responsibilities or assigning some responsibilities. In this case here, it would be me. There are some that are also working with a review flow. It could even be up to a second reviewer here as well. The majority of the clients we've talked to during the beta phase only work with a responsible party, but we also do support the reviewer flow as well. We are setting a date. In this case here, now the due date is actually today in a few hours. It could be that, okay, it's actually on Friday, HGU at 12:00 P.M. Central European Time. We are allocating some time to both the responsible.
It could be, okay, we want a few days to do the test. We also want a day to do the actual review afterwards. Basically, what dates are we communicating here? You can up these numbers here so they fit your processes. It might be that you need a full month to do so. I know that the control testing can be quite an excessive thing for a lot of you, and you are typically smaller teams as well around this. Basically, this is how we set up the test. We will have a look at, okay, how should this test actually look? When we are defining these programs here that I initially talked about, we can obviously, as I briefly mentioned, see, okay, who actually has access to these. We can also define the different tasks.
These will apply to all of the tests that I showed before. There are two different types of conclusions that we are setting up here. One is on the control conclusion level. This is the one that I am showing right now. The other one would be on the actual sample. If we envision the bank reconciliation, we're doing it for a full year for a specific entity. We would have 12 results. Maybe I sample out three of these. What do I actually want my testers to test on these three entities here? We define that in the sample conclusion. By default, this section here comes out blank because we see many different approaches to this. You can basically design your own here using the parameters that you can see here on the right side.
Now we came up with a few examples here. It's fairly basic, but it could be, okay, was the control activity performed in due time? We can say yes, no to that. Again, we can define whether this is a required item or not. Maybe we'd like to see, okay, on this specific sample here, did we identify any issues? Did it pass? Find something major? Did we find something minor? We can also see that. Maybe we want a comment field in the end in case that there were any issues to sort of describe that. This is what we are sort of the conclusion that we're giving on the individual samples. I'll show you how that looks in a few minutes as well. Based on that, we are doing an overall conclusion. We'll always have this effectiveness rate here.
You can rename some of the options here, but essentially, it will fall into the categories of effective, partially effective, and not effective. This is the approach that we've gone for now, again, based on the feedback that we have received. You can basically build upon that. If there are some additional things that you'd like to conclude, I added in a comment field here in case the overall control rating was not effective. Okay, then we need maybe at least we need some explanation on why we had this outcome here. Everything that we set up here, and we do this on the program level. I'll just go one back here. We'll then apply for all of the tests here that we have.
For each of these controls, for each of these entities, we'll have these sample conclusions, and then I'll evaluate on the control. This has been a lot from an admin perspective, from a setup perspective. I know that in a lot of the cases, this will be the same as the one who are in the control testing team. Let's say that you do communicate with someone outside of the admin part of Impero. You'll receive an email looking like this that there's a test I need to do. I'm a little bit late here in this case here. It will basically be, okay, there's a control test assigned to me. I can see the name of it, see when the due date is. I'll click on the link here. I will come to the specific page for our control testing part here.
Those of you, again, who are familiar with submitting controls in Impero, this looks similar to that. I can see the title up here for my test. I can see over here in the upper right corner, my sample period. In this case here, January to December 2024. I can also see what entity it is that I'm testing. In my responsible section here for what I need to do, I can basically add in my samples. If you recall back, this is for a full year. When I click add samples here, I'll see all the results for this full year here. Let's say, okay, I'm interested in seeing March. I'm interested in June, maybe in August. I'll just go with that. I hit select. This is what I'll see here in the overview.
You can see when the due date was. I can see who was responsible. I can see in any case that there were some controls that were either completed after the deadline or it's not been completed yet because it's still either awaiting review or the responsible. I can see that in the statuses here. In order to evaluate my sample, I click on these individual results here. I get my sample conclusion here as we talked about just a minute ago. I can actually also get the link here to the activity. I can see, okay, what am I actually basing my sample conclusion on? Now I dive directly into the result of the actual control. I can see, okay, this one was for August. It was done by Morten. It was done for this entity in this region.
This was actually the documentation provided. I can review that. It looks fine. I will go back here and say, yes, it was done in due time. Yes, it lives up to all of my criteria. I can hit okay here. We do a small thing, especially to ease the review a little bit because you might see that we have this indicator here as an eye. I can basically see here that we viewed this or I viewed this item here just a minute ago, but I have not actually seen the activity down here as well. We do a short visual so we can actually check that, okay, the tester did actually click view activity. Did actually see, okay, this was the result for June. This was the outcome.
This is what they basically based their test results here, their sample conclusion here on. Now I'll just do the same thing here for the last one. This one was for March. Again, you can see all the same details as I just talked you through. Was done in due time. It was passed here. I can do my overall control effective for this conclusion and say, okay, based on the samples here that I've identified, I've provided a conclusion. We do an overall conclusion here of effective. This was where, in case this was not effective, well, okay, then I was actually required to do an explanation. Let's leave it effective for now. I'll submit it. That's basically it.
If there's a review, then it will go to review flow where you can basically reject or approve this going back and forward. Where does this leave us now? Now we've created these tests. We've sent them out in the organization to various entities. Then we get this overview. At the current state, this is in the activity list here that we can see. Here I have a list of all the performed or basically all the tests I've created. It's more accurate because some of them haven't been performed yet. We are introducing a new way of filtering or a new way of filtering in this list here as well. I can basically add in a filter here. I can decide, okay, what is it actually that I want to filter upon?
It might be, okay, I'm interested in specifying a specific entity here. It could be entity 100 as we talked about before. I have added in my filter here. I can add multiple filters here as we go. I can also use this quick search here in the upper right corner if I'm only interested, for instance, in having a look at the completed items or maybe I'm only interested in having a look at those who have not been completed yet. I can do that from this list here. It might be that, okay, I can see these ones here are not being performed by Morten. It's because, I don't know, he's on holiday, something like that. We can also reassign these from the list here.
You get a full overview of all of the tests that have been created in Impero. I have this improved way here. I can add these multiple filters here as much as I want. I can use the quick search bar here to narrow down my data to have a complete overview of what I'm interested in. Yeah. I think that was it from this part here. I'll just stop sharing my screen so I can give it back to you, Jasmine. This is, yeah, basically where we are at the current state. There are a few things that might be missing for the general availability. Luckily, we are aware of these. We have listed them. These are the items that we're currently working on. It is an overall activity list for the control testing programs.
I just showed it here, but there are a few improvements that we still need to do. There is this bulk creation. Again, if you have, let's say, 50 controls, 50 entities, then it is a whole lot of tests that you need to create. Doing this manually will be a pain. Having the way of some bulk operations where you can mass populate these tests has to be rather key, so that we are working on. It is the export of these results. Basically, the output that we can have of all of these test results here. Now we have been out in the organization taking the time to fill in all of these conclusions here. Now we need to work on that data. That will be possible in our exports.
If you have an overview of your pending tests, I showed the workflow out of an email. You can also work out of the activity list here that I just showed, but it will not be a personal view as what you're used to when creating or, sorry, when entering controls. We'll do a specific page for these pending tests that currently lies on your desk. Again, we do know you are smaller teams out there performing a ton of tests. Just to have an easier overview of that, and that's also upcoming. The final one is to ensure the visibility of assigned tests. It will be in our user management section.
Basically, to ensure that when you're doing your housekeeping of Impero as well, someone leaves the company, changed position, all of that, that you're not accidentally deleting a user that was assigned to a ton of tests without knowing or without reassigning these to different users beforehand. We want to make that a part of the overview as well. This was a little bit on what we've learned, where we are at the current state, and what you can expect coming up as well on the control testing part.
Awesome. Thank you so much, Morten, for that update on the beta for control testing. With that, we have wrapped up the main kind of parts of the presentation, but we do still have a couple of things before the Q&A that we wanted to get to.
One of them was highlighting, based off of what David was saying, we would love to understand how your thoughts are in terms of artificial intelligence. There is going to be another poll launching here in just a second. We would love to hear about—let me just move this poll. We would love to hear about, are you using artificial intelligence in your work with risk and internal control today? We know it is very different from organization to organization as to whether or not you are allowed to even use artificial intelligence. We know a lot of organizations are looking into it, but we also know that there are different players out there who do not feel that AI is something that they would like to use in the compliance domain. There are also people who simply have not started looking into it yet.
I'm going to leave this open for a little bit, but would love your feedback. It's definitely something that we are looking into. The usage and the implementation of it will, of course, vary depending on your feedback. I'm just going to leave it open for a couple more seconds. I can say so far, it looks like the overwhelming majority of you, 43% of you, are looking into it. That's very interesting. We look forward to following up perhaps at the next quarterly product update webinar to see if you've made a decision on it yet. I'm going to close out the poll now. I'm also happy to share the results here. 8% of you are actively using it. Very cool. Very interesting. There are, of course, lots of applications for AI in all kinds of different areas.
42% of you, as I mentioned, are looking into it. There's about 21% of you who don't wish to use AI in this domain. Also something that we've had a lot of discussions internally about. About 30% of you are not quite sure yet. Would love to hear next time as well what steps you guys have taken afterwards to examine a little bit more how AI could play a role in your compliance processes. I also did just want to highlight before we jump into the Q&A some of our resources. If you're not signed up either for our product or our marketing newsletter, please do that. We highly recommend it because it makes sure that you get invitations to webinars like these ones, but also any events we might have or any exclusive content that we'd be working on.
Another great way to stay connected with us is by following us on LinkedIn. As I mentioned before, we're also putting all of our product-related resources in the help center. Things like this webinar will be made available there. Before we jump into the Q&A, I can see we've already started getting a couple of questions ticking in, so that's fantastic. I did also just want to launch one last poll, and I'll just leave this open while we kind of start with the Q&A. We'd be very, very thankful if any of you would be interested in giving Impero a G2 or an OMR review. If you're not familiar with it, it is a review site.
Other people who are considering our platform and just want to hear about your experience and your honest experience, that would be fantastic if you'd be willing to share. It's always just a great way, just like all of us when we're out shopping for new software, it would be nice to know. If you're interested in participating in either case study or webinar with us, that'd also be fantastic. If now's not the right time, that's totally fine as well. I will leave this open while we jump to the Q&A. The first one that I have is actually probably for me, which is when will the next product update webinar be hosted? Great question. As I mentioned, we're going to be doing these quarterly going forward.
The plan is to do the next quarterly product update for Q2 towards the end of June. Stay tuned for that. There will be an invite just as this time. You can also go to our webinars page and keep an eye there. We do also try to put an in-tool message as well in the Impero platform so that you can also get updates there on when the webinar invites start to come out. The next question that we have, and I'm just going to close out the poll. Thank you so much to all of you who are open to different things. We'll be following up with you. The next question that we have, I think, will be for you, David.
Is there a planned functionality that will enable process visualization for users to map process steps related to risks, controls, roles, and responsibilities, etc.?
We have actually discussed it at one point. We're a little bit far from that right now. It's definitely not something that's planned currently. It will require that we are further with control triggering and a few other mechanics of tying data together within the platform in order to be able to produce a meaningful visualization. I think it's really good feedback, and we would be happy to pick up discussions after this if you're willing to. Product management will reach out.
Awesome. Fantastic. Thanks, David. Yeah. Great that control triggering's being looked at already. That's a good stepping stone to that.
I think the next one would be for the next couple of questions are probably for you, Morten, with regards to control testing. How and where would we demonstrate within the documentation that the control attributes are being met? For example, if this is just a radio button or dropdown, the testing would need to be reperformed by the reviewer in order to see that the control attributes have passed or not.
Essentially, when building out these tests, setting out these sample conclusions, a lot of those we've had in the beta already have a framework in place. What I showed today might be, let's say, the light version of that. You can actually be rather specific in what is it actually that you want the tester to test, but it will be based out of radio buttons, dropdowns, etc.
I mentioned that for some of the users, there's not a review flow for some of the customers. There's not a review flow. That's simply because, okay, it's a control that's been performed, and then it's been reviewed afterwards. In some cases, it's also been through a second reviewer. We're sample testing it, and we're taking that out and then having a look at the conclusions on that. You can have a review flow on that as well, but it will be based on radio buttons and dropdowns that you'll build into your test. Reach out again if that doesn't completely answer the question, and we can go in details on that.
Perfect. Thank you, Morten. I think another question with regards to the sample testing as well.
Has it been decided to show or not show the individual sample test conclusions in the overview, or do you need to click in on each individual sample to see the results like you showed?
On the current stage, you'll have to do that. We discussed this yesterday, actually, David, on how to do this visualization as well. What we've basically talked about today is, okay, what does it take before we can make this a bit more general available outside of the beta? This is also what I talked through today. This doesn't mean that the flow ends here. We'll have a continuous development process on this.
We want to continue to add on value to all of you with all of our releases, but we'd rather get something out that you can use, get some value out, and then you can basically add up on it as we go.
Fantastic. Thanks, Morten. One more question for you on control testing here. If I'm interested in the—someone wrote that they're interested in the beta, but wasn't aware that it started in January. If they were interested in getting started or testing it, how would they go about that?
Yeah. Yeah. We've also reached out to a few for the beta part, but reach out to your main contact person here in Impero typically. It will be your customer success manager who can assist you in how the next steps will be moving forward. If you are unaware of who your customer success manager is, you're more than welcome to reach out to us as well. We will route you in the right direction on this.
Fantastic. I think the next couple of questions that we have are for you, David. There are quite a few people who are interested in the point around AI-generated control description. What more can you tell us about the functionality around this, and when can we learn more about it?
Yeah. Definitely. What we have done so far is we've compiled a huge list of different potentially relevant features that we could use AI to enhance. In this internal test that we've done, we've decided to work with control descriptions. Basically, auto-generating a control description based on the current control program that the control lives in. It basically assesses the sibling controls.
Based on the title and the context of the general control, it will suggest a description that is, during test, fairly accurate. I must stipulate that we are only doing this in a separate test environment currently, and there's no language model being utilized in the production environment or no customer data being utilized for this. It is very interesting to see once we have actually started working with this, how many potential use cases that are out there. We will definitely comply with all regulations and adhere to all concerns of the customers. Any AI will be completely separate. When we do launch AI in the general platform, it will be separate from each tenant, meaning that you won't be able to experience any data bleeding or anything else from your data and other data. We will not train on any of your data put into the platform, which is extremely important.
Thanks, David. As you guys can hear, there's a lot of considerations going into this. We are very excited that you're excited about it. Hopefully, we'll be able to share more at one of our upcoming product update webinars. The next question that I have is for UCC, and it is, will you consider expanding the tag categories to the user setup as well?
Yes. It's a very relevant feature extension. We would like to improve the better user management, for example, to label the user with more attributes such as entities. Yeah. Also, especially, we also want to look at how to manage the assignment of controls to different entities that are set up as assignment tags at the moment.
Yes, that is something we would like to look into.
Fantastic. Thanks, Xisi. Lots of great ideas from everyone. Lots of great questions. Morten, I have a couple more questions for you here on the control testing. There are a couple of people actually who are wondering, in the case of larger sets of samples, are we looking into the randomization or the ability to select samples at random?
Yeah. It's a valid question since it's a part of the process that you do control testing in the initial general availability version that we talk about also, what we have in the beta right now. It's not a part of that. I'll revert a little bit to my answer from before. Obviously, this is also a feature that we'll continue to explore and we'll also see, okay, what is the need for this.
Now, there were a few questions on it here today. For some of those we've talked to during the beta process, it's been less important because they did it on their own already. Obviously, this is something we'll continue to explore and see if there's a specific need for in the future.
Awesome. Thank you so much, Morten. As a cloud-based software platform, it is not that we launch something and we're not going to do improvements. There are continuous considerations and improvements. We do appreciate all of your thoughts and questions as we release things because we do take them into account, as David mentioned in planning the roadmap and their future priorities. David, the next question is actually for you, and it is, what was the timeline for the sequential control triggering that you mentioned, and when will we be able to use the functionality?
Another very excited person, which is great. That's good.
Actually, it is part of one of the upcoming releases, but unfortunately, only for one select client that will test it out being part of their specific requirements. Once that has all panned out and we are very sure that it will be applicable for all clients, you'll have an update on this in the regular channels.
Fantastic. Thanks, David. We continue to get lots of great questions. Xisi, I have one for you. Will you consider a functionality within controls where you can add an FYI user? The user is not the performer or the reviewer, but would just need some info about the specific control.
Yes. Thanks for the question. Actually, that is a feature we are planning at the moment. To set up notification recipients to exactly know who should be informed about the completion of a control. Not only the reviewer should be informed, not the admin. You have the flexibility to set up who receives it, and that person would receive an email about the completion.
Yes. Great. Super excited to hear that that's something we're already working on. We have one last question, and I think Xisi or David, one of you might be best suited. It is, do we intend to have a framework where you can centralize and retrieve all the documentation that control owners have uploaded in Impero?
Not being exactly sure what the depth of the question, whether it's all the assets that's uploaded in controls or if it's also the activity of the control performed.
Also, whether it's a framework, you can actually extract anything control activity-related currently from the API, which would make a lot of sense. Maybe we can follow up on the specifics of the need.
Yes, let's do that. Great to see so many questions. I'll take one last question. I can see there's still a couple more, but we'll do our best to follow up with you afterwards. I just want to be conscious of time. The last question, and David, maybe this is for you in relation to the control triggering, is do you plan to introduce conditional flow basing on an answer control is sent further or completed?
I understand the question. Yes, that is definitely part of the ultimate requirement for control triggering. However, in the first release, it will be a simpler version.
It will be a much simpler sequential control triggering. As you also pointed out before, during the past year, we've shifted a little bit the way that we work. We are getting features in the platform, and then we have a continuous commitment to improving those features instead of baking huge complex features. We are gradually improving them on the way and testing while we do that.
Fantastic. I know there's a couple more questions we didn't get to, but I can see who has asked those questions. We'll make sure I'll work with Xisi and the product management team to follow up with all of you personally. Thank you so much for all of your wonderful questions. It's great to see you so engaged and interested.
Before we wrap up, I did also promise just to put the QR code here as well for our new tutorial with our fantastic implementation specialist, William, who does walk you through how to use task-based reports. I think Xisi and I talk about this all the time. We cannot recommend it enough that you do not only use the control status reports, but also start using task-based reports because it will just make the way that you work with risk and controls and compliance that much more effective. I highly recommend that you check it out. It is also in the tool. I just wanted to leave that up here for a second. With that said, I did just want to say a big thank you to all of you for joining the webinar.
A big thank you to David, Morten, and Xisi for sharing an update, sharing all the information about our priorities for the Impero platform. Of course, save the date for the Q2 product update in June, later in the second half of June. We look forward to seeing you all there. All right. Thank you, everybody.