Name: Unlock the Future of SaaS Management with Josys AI
Uploaded: 2025-07-02T18:01:10.199Z
Duration: 45 min 4 s
Description: Unlock the Future of SaaS Management with Josys AI

Transcript for "Unlock the Future of SaaS Management with Josys AI": And thank you for joining us in the versus webinar today. My name is Nathan Archie, and I'm based in Sydney, Australia. I'm the GM for The US and CAU market. It's a real pleasure to have you join us today, and we're really excited to be able to share with you the AI journey that Joseph has been on. And I'd like to introduce my copilot for today, Sruthi Soma, who is based in Bangalore and is the director of product. So welcome, Sruthi. She's been instrumental she's been instrumental in much of the product features and rollouts that the business has. So we're really, you know, very honored to have you be able to take us through, what we've got today. And, Srini, maybe you can just start with a little bit of a question that I have. Why is, you know, AI is so prevalent at the moment. It's so important to a lot of businesses around the world. Every business is racing to implement AI across their infrastructure and and to to, you know, make a significant difference in terms of the way their product platform, is it can be enhanced and utilized by customers. Why is AI so important for the Josys platform for and the Josys customers for us to, you know, implement it, as a priority? That's a great question, Nathan. I take it in two parts of the question. I think the first one is scale and enhancing the IT experience. I think, by nature of the space, we are in every SaaS application is unique, and an AI engine can provide us the intelligence in dealing with the nuances of each application when it comes to, integrating those application, enhancing the discovery engine of the Josys platform. And also in terms of providing, directed insights, instead of a rule engine and AI engine would, help in understanding patterns and, better provide insights to the IT admin. The second facet to this is the, end user experience. I think, everybody around the world is now used to talking, to a human in the form of your, chat GPT. Right? So, we have the potential to unlock a similar experience for, employees, using our own employee portal or, interfacing with, Teams and chat for Teams and bot, Slack bots, etcetera, to help enhance the end user experiences as well, where they can have natural language queries and users can help resolve it for them without having to go to tedious forms and, ticketing, mechanisms that we have today in place. Thanks, Trudy. And that that's really insightful. And I know, through the rest of the talk, you're gonna take us into a bit of a deeper level. But I will just just step back for one second before I hand over to you more specifically, just for those of you who with us who are not sure what Josys is all about, or what SaaS management is. That's something that's also quite important. So in terms of Josys, as a business is Japanese headquartered, we've been around, just around over five years and got, now offices across across the world. And we've really invested in being able to, develop our sales management platform quite significantly, especially in the last sort of six to eight months. We've gone changed so dramatically. And, Sruthi, you've been at the the crux of that. And SaaS management is really around how do we empower a business to take there's just so many SaaS applications that a business has to deal with these days. On average, on average, it's around over a 125 SaaS applications that are this around the world has. And with all these different SaaS applications, there may be a better way to make sure that we've got visibility we are being utilized across the business. And secondly, do we have, oversight of as to who has access to what type of applications? And then there's also another sort of layer of security and compliance in terms of access management. So it has access management rights. These are the that's specifically important as well for different types of audits, whether it be commercial or security or as well. So there's a whole bunch of Russian reasons as to why SAS management is really, really important, and we're just seeing the, the space rapidly expand at the moment, and we're really excited that Josie is at the forefront of that. So without further ado, Sruthi, I'll hand over to you, and if you can maybe share with us some of the exciting features from an AI perspective that we've launched, Josys. Thank you, Nathan. I think, this slide let's start over with what the Josys core engine is. Well, and encapsulate, what, Nathan was talking about. As Josys, our core mission continues to be to help, IT admins manage their SaaS stack. And, this translates to key three key pillars on juices, which is, enhancing visibility, enabling governance, and providing value. Visibility or also what we call as discovery is essentially our engine which enables IT admins to get complete visibility into their SaaS stack. This means understanding what apps are being used in the application, what are the users who who are the users using those applications, what is the spend they are incurring. The core of this here is that you cannot govern or optimize what you don't see. So this becomes the first key pillar of our SaaS management stack where we allow the IT admin to be able to visualize everything SaaS that is happening within their organization. The second pillar is the governance. This essentially ensures that IT admin through the different features that are available on the platform, we want to enable IT admin to be able to ensure that the right user has the right access to the right application for the right duration and in the easiest, most efficient way possible. So the the governance pillar is essentially directed towards building everything we can on the platform to enable this process for the IT admin, which enables them to have a more secure SaaS stack, and also the most cost efficient SaaS stack. Together with visibility and governance, they can generate the value of optimizing their licenses as well, because once we ensure that the only the right people have access to the applications, approximately on average in the industry, 25% of the licenses are over provisioned. So we end up surfacing those, information to the IT admin to quickly reduce their SaaS spend as well. And the last one is comply. Once again, in different layers of, Josys both in visibility and governance, we need to ensure that they are complying with both the industry and, organization policy, for their SaaS stack. With that over Sorry. I'll just jump in very quickly. Yeah. So I just I did forget to mention at the beginning, if anyone has any questions, there is a q and a chat on the side. So please post your questions, and then we'll come back to Sridia at the end to answer those, number one. And number two, we will have a little survey at the end that we'll send to you to fill out. Sorry for that interjection. And and Cool. I'll continue. So with that, let's go to the next slide, which is on what are we covering in this particular, session and what's new on the process platform. So we've added three, in three areas. We'll be focusing in this session on three areas, which is visibility and, managing and automation, which are part of the governance engine. We talk about four q four key AI and automation capabilities that we added. The first one is the AI based risk assessment, for all applications that are being used in the organization. The second one is, enhanced and automated identity classification. The third one is the AI based policy generator. And last but not the least is the automation workflows for onboarding and access review automation. Even before we get into, what the Josys solution is, I think a good thing to first understand I want to spend some time on understanding the, current state of IT process in terms of evaluating the SaaS risk. This continues to be a huge challenge today for the, IT admins. I think as, Nathan mentioned, an average organization has more than one twenty five SaaS applications, and these are that are somehow being in some capacity being managed by the organizations, either by the IT admins or, by, different department heads who are running those applications. And discovered apps, which is basically applications that are just being used by, employees by just accessing the SaaS website directly could go well over 500. And, this makes it very difficult today for the IT admin to, understand the risk profile of every single application. There's no centralized repository of risk information. There's also not a standardized risk assessment. There are several things that go into evaluating the It involves understanding the, data privacy, how the data is being handled, what kind of, control controls and mechanisms that the application has in place to ensure, that, you you can secure the application when they are when when your organization is using that specific application. There is also a new era of risk now with generative AI. IT admins are still any getting accustomed to what the risks are with generative AI, and employees are every single day going forward and using newer and newer Gen AI applications. All these together today make it very difficult for an IT admin to evaluate the risk holistically for their entire SaaS stack. So this is where Josys comes in. We have introduced Sir, can I just can I just add something there? I think, you've made a good point. Like, one of the examples with one of our clients at the moment is exactly as you said, you know, the the CEO has mandated to the business. We wanna implement more AI tools. And so everyone across the business is trying to find new AI tools that they can implement. And there's no central way to identify what is the risk of these AI tools that they're trying to implement, number one. And number two, firstly, on a risk level from a security perspective of incoming threats, but also from a risk perspective of taking company IP and putting it onto these AI platforms and what's happening to it. So being able to have visibility and control over that is something that's quite significant. So what you're sort of saying is, Josie enables that, and you're gonna take us through exactly how that works. Is that that's correct? Absolutely, Nathan. That's that's what we get. So, so we have introduced a new AI powered SaaS risk analyzer, which gives you, a comprehensive risk profile of every single SaaS application that is being used in your organization. When an application is discovered, you will automatically, within, seconds, see the entire risk profile of that application. I think the first thing it empowers the IT admin. We empower the IT admin is with the numeric score and a clear risk level label. Risk level label indicating whether it's a high risk cap, it's a low risk cap, or a medium risk cap. And in addition to that, we also provide a numeric risk score, which allows the IT admin to, objectively prioritize what the lowest gaps are and identify which ones they want to pay more attention to. And how Josys gets this information. Josys AI relies on different sources of information to be able to generate this report. We're going to be open source intelligence itself. We are also looking at publicly available data of every single application we are providing the risk risk for. We are also looking at attributes that are specific to the application. We are also using other reputed, SaaS, ranker profile, profile authorities to generate this score. So several different data sources have been combined and consolidated to generate, this risk profile for the, IT admin to visualize in one specific page from Josys for all the applications. The second thing, I think the interesting thing which Nathan you asked about was the Gen AI insights. So, in addition to providing a consolidated score, we've also added a specific section called as Gen AI. This is applicable for any general AI application, where we are talking about the models that are being used. We also talk about, how they handle the data. If the data that you are pushing into that application, is it going to be used for training? And we are also linking the generative AI policy link upfront there for the IT admin to review. So within even the rating itself, we take into consideration how that specific application handles the, PII data, the data that we expose to the, application. So it ties back into the score as well. And, also, for the IT admin, we provide a block of information specifically regarding generate way and how they are using your data. The next, two areas we've considered into this is the security poster and the operational risk. This primarily looks at the controls that application has in place to ensure that the your when your organization is using it, you are secure as an organization. So we look for indicators like, hey. Do they have SSO? Do they have MFA? Do they allow for auditing capability? In case the application entirely goes down, then, what is the disaster recovery system they have in place? What is their general uptime looking like? So even parameters like this have been considered in terms of helping you evaluate what the risk of that operation is. Last but not the least is legal and compliance certificate, a huge component of the risk scoring. We do look at these, certifications that the, applications have. And, if they have, like, GDPR or soft two compliance, we know that they are handling data security lean and bystander. So they such kind of certifications help the help improve the application risk score. So all of these together go into the risk engine and create a numeric score for the IT admin. At the first glance, they can see the score and the risk level, then they can get into the detail and, review the entire report of that application. And as you can see on the image, we also plug ins different sources, where you can get more information of the application. So once again, it is a one stop shop for the IT admin to review the report. They don't have to scramble across the web to find out every single detail of the application, which was one of the problem statements they have today in terms of, handling this risk profiling for hundreds of application. So we provide an overview, and we also link them to the right, destination they want to go to if they want to get further information. Hi, Sruthi. Thanks for that. We've got a quick question that's quite pertinent and relevant to, what you're talking about at the moment. The question is, earlier, Josys was running risk assessments using Netskope. Yeah. How different is the current risk assessment using generally they are buying? So how how does it differ from the old system that we used to run? Yeah. I think a few things. I think the first thing is there is a difference in terms of some of the parameters we have taken into consideration in terms of, rating the, score itself. We will also be sharing a detailed document after the session on, what are all the parameters that went into considering the risk score. The second thing is that, I think a numeric risk score, which has been a long pending ask from, a lot of our customers to provide a numeric value on what the risk is. Just a label of medium or high does not help the IT admin, evaluate, in in-depth on what is happening on the application. The third thing is we have enriched the risk profile information. We were only having a label of whether the risk is, medium or low without a y. So with our own engine, we are able to generate, an intelligent overview on what is the reason we are calling something as medium or, low risk or high risk. And, last but not least, we've also added the generative AI capability with our engine, where we are specifically tagging the, new issues that are flagged with GenAI. Thanks, Shruti. Makes a lot of sense. Okay. I'm gonna move forward to the next, set. So this is the first thing that we worked on, which is basically the disc enriching the Discord engine, empowering you with a better risk thing. Now let's move to the manage part. Within manage, we had two features we worked on, which is, basically the we've introduced, which is AI based identity classification, and merging. So this is primarily a tool that will help IT admin, enhance their operation in to enrich the identity information. So there are two parts to this. The first one is the human and nonhuman identity classification. So whenever we fetch information of user profiles into Josys, either using your IDPs or, using a CSV upload, we don't inherently always get the, user category. That is whether they are an employee, they are a system account, are they a contractor, are they an external, employee. So information like that, is not, inherently available to Josys. Now with Josys AI, with a single click, Josys provides a recommended classification for all the user profiles in your system where it will indicate whether it should be a human identity or a nonhuman identity. And within the human identity, the different classifications I talked about. This helps the IT admin create a richer identity profile, which can be used further by creating your access reviews or, access policies or workflows. Whereas an admin, you may choose to have a different, policy for onboarding for employees versus an external, guest who's coming onto the, application. So that those kind of workflows can be, realized once you have the right, user profile information. So, with this classification, we, allow the IT admins to do that with a single click. The second one is duplicate identity merging. I think another big pinpoint for the IT admin, as Josys because we are an engine that, takes in data from hundreds of sources. One of the issue that happens is, we do end up creating duplicate identities in certain scenarios for users because every application sends identity information differently. Josys could consider email as the primary identifier for your account. But, another application, like, say, Atlassian may consider the first name of the user as the primary identifier and only dump that information and not provide the email information. Now, currently, in that case, we end up creating two identities for the same user. And, the IT admin is tasked with actually going and mapping these duplicate identities. First identifying, hey. This is a duplicate and then going and mapping it to the original identity of the user, which as you can imagine can be a tedious task. So now with the those AI, again, that is also one click of operation. They can just click on auto sorry. Rectify user profiles with identity conflict, and, automatically, the Josys AI engine will give a recommendation on, what are all the duplicate identities that can be merged. Another interesting thing we've done here is provide, the IT admin with the confidence code so that before applying the, change, they actually can review anything with low confidence. Or if they want to only apply the merging for high confidence identities, they can just select the high confidence ones and go ahead and apply the merging. So this feature together helps the IT admin both clean up their identities, maintain the hiding required, and also enrich the identity with data that is required to power forward flows. Once we have the rich identities, the next logical step is to generate the access policy for them. So, I think, we in the beginning of the session, I spoke about, one of the key pillars of a SaaS governance, engine is to ensure that the right people have access to the right applications. This feature essentially is targeted towards making this super easy to implement for the IT admin. So let's first talk about what are the complexities today in access policy. Again, going back to the fact that on average, there are one twenty five SaaS applications in, like, a midsize form. So creating a base policy of, hey. This department should have access to these applications. This rule should have access to this level of application is a very daunting task, can be a very daunting task for an IT admin. One thing is there are a lot of applications. The second thing is that applications owners are also dispersed. Not every single application in an organization is managed by the IT admin, working very closely with the department owner to understand the usage patterns, and then defining an access policy is manually it's difficult to do it manually. It's a very overwhelming task and also is very time consuming and it requires a plethora of people in the process to ensure that the right policy is generated. The second thing is that even after the policy is defined, it becomes very hard for the IT admin to ensure that, hey, everything is being, onboarded or, assigned provision based on the access policy. Because, again, going back to the fact that every application has, different owners. We have IT applications. We have department owned applications, making it very difficult for the IT admin to ensure that every single application at every any given time is following the access policy. So overall, the and with the lack of the detection of policy violation, it makes it very it defeats the purpose of the IT admin putting in all that work for the access policy definition. So there are significant gaps today in, how access policy is generated and also, enforced. So we're trying to solve this with Josys in a new interesting way where, the first one is policy generation. Once you connect your application to Josys, if you're already using a 100 apps in Josys sorry, in your organization. And once you connect Josys to these applications, sorry. Once you connect these applications to Josys, Josys instantly analyzes all users' patents across all your applications, and it creates a base policy for you. Josys will create a recommendation of different policies for different clusters of people and applications, and present it to the IT admin. All the IT admin has to do is they just need to verify the policy and create it as a, enforceable policy within Josys. So something that could have taken weeks of effort, once you connect the application to Josys, it can be done within minutes. Josys immediately generates a policy for you based on usage patterns, and, the IT admin can quickly enable that policy in the organization. The second thing is drifted detection, which is nothing but detecting policy violation. Once this policy is created in your instance, Josys also is continuously monitoring whether every single access or every single provision that exists in your organization is following that policy. If there is any policy violation, the IT admin is immediately notified, and he's also presented with two options, both the ability to upgrade the policy itself because organizations evolve. We introduce new apps to do, your organizations. We add new departments to those applications. So keeping that in mind, we can with a single click either upgrade your access policy or you can also go ahead and choose to entirely delete the approved access from the application. Again, with a few clicks, both of these can be done. So just summarizing with this access policy generated in detection, we simplify the entire access, policy creation and management process for the entire life cycle of the user and the application. New policies are generated and recommended to the IT admin. They just have to approve it and we create the policy and all the, violations are reported back to the IT admin. So now that we have the access policy in place, and we also have the rich identity information, let's move to the next one, which is automating the implementation of, provisioning as well. Okay. So before you jump on, there was just another question. Yeah. Sorry. There was just one more question just relevant to that. The question was so basically, it's Josys suggest the access policy to be implemented. Can Josys evaluate existing policies and highlight the gaps? Yes. So, in this drop, we are what the first preview drop that you have available this month, will only be Josys giving you the policy recommendation. We are already working towards allowing, admins to share their policy, and we can just flag the gaps based on that policy as well. So we do allow you to create your own policy. So, there's no restriction on that. But if you have a policy in the form of a document, is that easily running through that and creating the rules based on that is also something that we are working on. So if you already have a policy, you can create that as an access policy in Josys, and Josys will keep flagging any, deviations that are there from your manually created policy as well. So you can create the policies recommended by Josys. You can create new policies manually. And lastly, we are working towards the ability to upload a doc and generate the policy roots from the doc directly. Cool. And move on to the next bit, which is automation of, workflows. So, again, I think, one of the key areas IT spends a lot of time is on employee onboarding and offboarding. In the absence of any kind of automation, a typical employee onboarding is essentially IT admin getting ad hoc request on who are the new employees coming in, what are the applications they need to be added to. And similarly, different department owners getting a request for provisioning them on those applications depending on, what the kind of application is. So, as you can imagine, this is a manual, tedious tedious process and, also a very poor experience for the employee because they might not end up with all the access they require in, on day one because multiple people are involved in this onboarding process. So that's where JOSYS comes in. We are trying to automate the onboarding process entirely for the, IT admin. So they just need to we've added a new onboarding flow called as, sorry, workflow called as onboarding workflow, where you can set up a trigger that whenever a new employee is onboarded or an access request is raised, select the application based on the conditions that you want to configure, and automatically add user to different applications. So if you take the example on the screen, we have that whenever an access request is raised, or when employees onboard, the trigger can be either of them. And if the status is the employee, the full time employee, his work location is and his job title is manager, automatically go ahead and provision this set of applications to the user. So whenever the new employee is added with this attributes, it's a one time setup again, and the IT admin does not have to worry about how the onboarding is happening. And, again, he does not, it also takes away the responsibility from different department owners to manually run the process. And the employee has a smooth experience of getting all access to all the applications on day one the minute they get onboarded onto the organization. Another important thing here is, I think like, we spoke about access policy. Even with workflows, it can be very tedious to actually actually write down all these rules and configure who should get access to what application. Because, again, at one twenty five apps on average, creating anything as a policy and automation can be complicated. We will, we see similar issues like we saw in access policy for workflows as well. So with this workflow templates, we also make sure that operation is really easy for the IT admin. So what we've done is we've created some default workflow templates for, onboarding or whenever a shadow user is identified. In addition, we've also created intelligent AI powered workflows for onboarding where we are plugging the access policy generated through the application itself. So whatever policy we are saying is recommended here, we also recommend you to create the workflow directly from the workflow page. So once again, the intelligence of, identifying the usage pattern and recognizing who should have what, not only helps you with identifying the setting up the policy and identifying the violation, the same policy can also be used to automate your entire operation on workflows. So each of these conditions and add users block don't need to be configured from scratch by the IT admin. We do provide the capability to from the provide the template to you. The IT admin can just review all these prefilled conditions and create the operation in sorry. Create the workflow in just a couple of clicks. So once the workflow is created, then, the any onboarding request continues to go through the workflow. Again, we provide a very good audit trail of all the functionality, all the users that are being onboarded. Every time a work workflows and an IT admin is notified. So you continue to have the required visibility that you need to to ensure that all the automation is running as required. And every failure is also intimated immediately to the IT admin so that they can take action, on, remediating those failures if there is any failure. I think the last but not the least, content that we wanted to cover in this session was access review automation. Again, in essence of ensuring the right user has access to the right application for the right duration, another key things that IT, key operation that IT admins periodically undertake is, reviewing the access of application. This happens either quarterly or, biannually where IT admins review whether all the users in that application are legitimate and should they do they need to continue to have access to the application? Now, this can either be done directly by the IT admin or it can be passed on to the department owners of the application because more often than not, at least 40 to 50% of the applications are actually department owned. So, different reviewers participate in letting the IT admin know who has access to what application. We already had this feature in place. We've added another layer of automation here where IT admin does not have to review the responses manually and take action. Now going forward, whenever they set up an access review, if the reviewer says, no. This user should not have access to the application, the IT admin can set up an automation to automatically delete the account for the user. So if on average, if your organization has, 40 apps with 100 accounts, you're probably reviewing about 4,000 accounts on a quarterly or, by annually. Now at that volume, it becomes very difficult for the IT admin. Even after the reviewer reviews it, it is difficult for the IT admin to manually check the response and take an action. So they can automate the whole thing where they set up one single access review for all the 10 apps and choose the option to automate action based on the response given by the reviewer, and the entire operation is taken care of in the background. And one more thing we do is because access reviews sometimes lead to no response. And based on your organization policy, you may have a policy that no response is received. In ninety days, you might want to, anyway, delete the account or, send an escalation to email to the manager. So workflows like that are also possible. So we have the the workflow allows you to branch into generating action based on every single scenario. That is what have their if they respond a to this, if they respond to b this, or if they do not send any response after x number of days, then go ahead and take this action. So with this, the access review, periodic access review becomes again a one time access review creation for probably five, ten minutes for the IT admin and the rest of the operations running in the background for them. That covers majority yeah. Oh, we've got a couple of questions really just on yeah. I mean, look, the access review is super critical as well. But just, on a couple of the, questions around the workflow just very quickly. The first question that's come through is, can we set up the onboarding workflows based on projects instead of departments? So currently, we are allowing the onboarding workflow to be the attributes can be the user profile attributes, essentially. All of these attributes are attributes that are available within our user profile module, which is work location, job title, which are the default attributes that are there. Another feature that we added, just this month was ability to create custom columns where you can add any information you want. And we are in the process of propagating that information to workflows. So short answer, as of today, you can only use, the existing user profile fixed attributes, which is status, work location, job title, user type, etcetera. Within the next quarter, you should also be able to create any custom column and use those attributes in conditions. So that essentially includes any column that you want to create as an attribute. If that is project, yes, you can use project as well. Great. That's great news. Thanks, Archie. And the next question we had was, each SaaS application can have a current owner. How does this workflow connect with those owners in getting the application provisioning during the onboarding? Each SaaS application can have an owner. How does this work for connect with those owners in getting the application provisioning during the onboarding? Understood. Notification for the email or Slack? Got it. So, there are two two ways. I think the first thing is, once we integrate the application onto Josys, and I think the first thing is the alignment with the owner on what the policy is, that or the policy should be set up in accordance with the application owner itself. The second one the second is intimating the, department owner whenever a new user gets added. This is already part of our, provisioning, workflows where the application allows you to configure whether, you want to update the department owner. And the same can be done using the app level configuration while they are configuring the action on this page. So you can determine who the, information should go to. That is one thing when you leverage the application information directly. The second thing is Josys also offers another action called as send an email. So at the end of the workflow, you can have two actions. The first action is adding the user to the application. You can configure a second action where you see that after the configuration is done, send an email to the admin with the details of whoever was onboarded. So you can leverage both of the flow, either the native app flow where the Google Workspace itself is sending the application. Or if you would like to use Josys to send the email, you can add a second action at the end of the workflow. And every time the add user operation runs, an email also will be sent. Thanks, Tracy. Okay. That was the last, review I had. So just, last last workflow I I had. So just summarizing the access policy and workflow. With this new capabilities, we are empowering the IT admin to create easily create a policy, manage the violations of that policy, get flagged and manage the violations of the policy, and also automate the implementation of that policy throughout the entire life cycle of the application and the identity. Thank you. Thanks, Sruthi. I mean, we've had really fantastic questions as well, so thank you to the audience for sharing those. If there are any further questions, please feel free to ask. And in the interim, you'll receive, in a few minutes seconds a survey. So if you could fill that out, please. And just what's so just last we're wrapping up. So, Sruthi, thanks so much for sharing some amazing information about the AI journey that Josys is on at the moment and and what we're what we're currently doing. It's it's really quite you know, it's so important in terms of being able to provide a platform to really enable our clients in so many, many ways, especially on the policy side. That's super important. We have just had another question coming through. So I'll pause for a second and ask you that. A question on security. Can we run risk assessment on an application before we start using, before it falls under discovered apps? For example, we want to evaluate assess application on various parameters before we start using it. Security is one of the key parameters we want to under understand. If this is possible, what's the procedure? Yeah. I think question. It's a two part answer. The, drop we have currently allow you to view the, risk application risk assessment for apps that we do discover in your organization. We are working on the capability to allow, the IT admin to be able to view the risk for any application in our, application DB, shortly. So the answer is currently no, but, it's already being worked on. We will shortly allow you to analyze any application, in the future. Thanks, Trish. So some really exciting, releases ahead, which will, again, as I said, this is over the first release on the, first step in the journey in implementing AI across, the Josys platform, and we're super excited to see what comes next out of these brilliant minds, Sruthi and her team. So, Sruthi, was there any sort of last comments that you wanted to share with anyone around, you know, future status or just, you know, SaaS management in general? Yeah. I I I hope you'll like the new capabilities that we brought onto the platform. And like, Nathan rightly mentioned, it's just the start. This is the our first introduction into, using AI to, enrich those capabilities. They're already already looking at different things to enable, better shadow IT management, allowing for deeper integrations into doses, of different applications, leveraging AI in all of those, areas as well. More to come in the next webinar. Amazing. Thanks so much, Ricky. And thank you everybody for joining us today. We look forward to seeing you at our next installment, and enjoy the rest of your morning, afternoon, evening, wherever in the world you are. Thank you. Thank you.