Video: What’s Next for Sana from Workday: Superintelligent AI That Gets Work Done | Duration: 2332s | Summary: What’s Next for Sana from Workday: Superintelligent AI That Gets Work Done | Chapters: Webinar Introduction (1.76s), Asana Platform Overview (148.485s), Platform Demo Walkthrough (573.67s), Asana Roadmap (1244.01s), Q&A Session (1622.23s), Change Management Strategy (1825.64s), Beyond HR Tool (1966.55s), Workday's Competitive Advantage (2094.605s), Closing and Next Steps (2234.965s), Closing Remarks (2325.525s)
Transcript for "What’s Next for Sana from Workday: Superintelligent AI That Gets Work Done": Hey, everyone. We're gonna get started in just a minute. So welcome to today's webinar on what's next for Asana from Workday. Few brief housekeeping items before we jump in. First, you're gonna receive a copy of this recording within twenty four hours, so keep an eye out for that. Second, please submit q and a in the q and a tab on the right side of your screen rather than using the chat. We have someone on our side who will be responding to questions live throughout the webinar. And then there's also a survey after the webinar, so please provide any feedback you'd like after the event ends. Finally, there are some links to various resources in the docs tab, including a link to a May 5 webinar and a link to request Asana demo, a few among a few other things. And then the obligatory product statement. So any unreleased services, features, functionality, or enhancements referenced in any Workday document, road map, blog, or website, press release, or public statement that are not currently available are subject to change at Workday's discretion and may not be delivered as planned or at all. So customers who purchase Workday services should make their purchase decisions based on services, features, and functions that are currently available. So now that we have those things out of the way, a few brief introductions. So I'm Katie Haines. I'm a senior go to market manager and a member of Workday's Asana Center of Excellence. I'm based in our New York City office. And my role is really focused on driving the successful launch and adoption of Sana Enterprise across Workday's customer base and beyond. And really excited today to dive a bit more into the products through an overview and also a demo. And later on, I'll also be joined by my colleague, Maruna. She is a product manager for Asana Enterprise, and she's based in our London office. She focuses largely on the orchestration layer of the product and how Asana speaks to other Workday and third party agents to create rich experiences with, of course, human in the loop validation. So super excited to have her representing the product team today and share more about our roadmap later on. So let's jump in. I like to start by framing this conversation around what we're seeing in the market today and how the AI landscape has really shifted. So over the last three years, I think it goes without saying that AI functionality has grown exponentially since from something that was really good at search and summary to now where we have agents and AI powered workflows that are actually capable of doing work. But, like, despite this explosion in technology, we haven't seen many organizations that are able to capture ROI from their AI deployments. And, typically, we think this is for a few reasons. One, knowledge and business context is spread across so many tools and systems, and there's no centralized way to access or act on it. So agents aren't acting by understanding your people, your money, your business processes. Then secondly, I think a lot of AI tools are providing answers or summaries, but they're not stitching together information to actually complete work or execute tasks. And then finally, governance and security still remain a concern, especially as AI agents sprawl across organizations. It has become really hard to track what they're doing, who's using them, why, and how. And so we've designed Asana as an agentic AI platform and front door to work to really close these gaps. So from a context perspective, we've built Workday within the Workday infrastructure so that it sits on top of your organization's people and money data, but is also deeply integrated into other tools across your tech stack. Secondly, we've developed a fully natural language platform that can democratize access to AI for all employees, and it provides them both the opportunity to utilize prebuilt agents and workflows or create their own in natural language. And all of these workflows and agents can actually execute full end to end workflows by tapping into both Workday, but also your other third party tools. And because Asana lives within that Workday ecosystem, it retains the same governance and security posture and also provides full visibility into how your agents are being used across your company. So to make it a bit more tangible, what can Sana actually do in practice? I think to set the scene, Sana is a web based platform. You can either pull this up by yourself using your Internet browser or you can jump into Sana via your Workday instance. But the foundation for Sana is really its access to knowledge through third party integrations. So you'll see a small subset of those logos along the bottom of this page here. But it's not only integrated with Workday data, but also connected to hundreds of tools like Teams, Outlook, SharePoint, ServiceNow, etcetera. And once Sonna ingests information from these tools, you can then execute tasks broadly across these four categories, find, act, build, and automate. When it comes to find, this is Sonna's enterprise search and chat functionality, all done in natural language. So you can find information, ask questions, and summarize data across all of your tools. Then act is the ability to push updates into third party tools from Sana. I think a great example of this is, say, you want to grant an employee access to a particular tool in ServiceNow. I could simply request that update from Asana, and it can write the update directly into Sana into ServiceNow without me having to leave the platform. Then build takes your knowledge and turns it into ready to use outputs like dashboards, documents, and analyses. And then finally, I think automate is where Asana becomes so exciting because this is where it actually starts doing work for you. So you're able to build multistep workflows using natural language that can execute end to end on your behalf. So for example, if you wanted to submit expenses or get help preparing a performance review, Sana can be set up to orchestrate that work by tapping into Workday, SharePoint, Outlook, your calendar, etcetera. Moving on to kind of packaging and and from an offering standpoint, we have two pricing packages for Asana. There is core and enterprise. I'd say both drive value at different levels of depth and automation. Enterprises, what I'll talk about first, this unlocks the full platform. So this is every surface, agent type, all connectors across your tech stack, the orchestration engine, and also the optional agent system of record, and Workday security all grounded within the Workday identity. We think of this package ideal for organizations that want to do work across all of their tools, not just Workday. And then core is really the same architecture, but scoped exclusively to Workday. So this is prebuilt agents, embedded experience, multi step automation, all running on your existing Workday data. This is a flex credit based package. So you pay in a consumption model for what you use, and it's the fastest, lowest risk path. So really increasing your ROI within Workday. So I wanna visualize what this looks like in practice through a few different use cases or examples. So here you'll see different prompts or queries in both Sono Core and then if I wanted to execute them via enterprise. So let's take the example of payroll. So with Core, you could ask a question directly to your Workday knowledge like when is my next paycheck and how much will it be after taxes? But with enterprise, I think it takes it one step further and can be a bit more complex. So let's say I relocated from New York to London. Can you check if my tax withholdings, benefits, and payroll have been updated? Then if not, draft an email and send it to HR. So here, Asana is searching through multiple systems and drafting an email to send on your behalf. Next, for onboarding, imagine you're onboarding a new employee as a manager. With core, you could ask a question like, I have an employee starting on Monday. What do I need to complete before their first day? But on enterprise, you can actually set up the entire preboarding workflow and execute that entire workflow on your behalf. So you could say set up everything for my new hire starting on March 3, including my profile, laptop request building access, etcetera. You can even set this up to be done on your behalf every time a new employee starts. And then finally, imagine you're finishing a trip to see a customer site and you have to do the dreaded expense report. With Sonicore, you can ask Sonic to start an expense report or submit a photo of a receipt. But then with enterprise, you can actually ask Sonic to pull receipts from Outlook, gather context from your calendar, and then match it to the right, client based on your calendar, then draft that expense report. So a few different examples here in different levels of depth through which you can engage with both Asana and Workday information. I'm now going to jump over into a demo, but first, just wanna talk through the examples that I'll show in Asana. So I will walk through maybe five or so use cases in the platform. I think first, I wanna show the example of how can you seamlessly create a job requisition, something that many, many people have to do, during their careers. Next, an example we talked about previously, how does Sana make expense reporting more seamless and easier? Next, I'll also walk through how can you create and submit performance reviews and have an AI tool like Sana support you with that. And then finally, I'll do an example of preboarding. So have Sana take us through the entire preboarding flow and automate steps along the way. So I'll jump over into Asana now. So welcome to Asana. I said before, Asana is a web based platform. You can access this through your Internet browser or through the Workday portal. In the future, we'll also have Asana embedded directly into Workday so you can use the chat functionality from your Workday instance as well as a mobile app. For today's demo, I'm going to largely operate in the web platform since I'll be showing some more complex workflows. But when you open your own instance of Asana, your Homepage is going to be slightly custom to you, but it will consist of an agentic chat feature here. And then on the left hand side, you can navigate to your inbox and to your workflows. And you can use the agentic chat feature to ask questions about company policies, your payslips, PTO, expenses, but but it could also tap into other third party systems. So say you want Sana to summarize something from SharePoint. To show a quick example of, you know, a really easy query in Workday, maybe I wanna know what my PTO balance is. Sana will then quickly pull up that answer for me, and it's also breaking it down now into what types of PTO days do I have, or those vacations, sick days, etcetera. But to show something a bit more complex and how I can interact with the chat feature, I'll use an example of creating a job requisition. So say I wanna hire a new data analyst on my team, I could simply type something like job rec for data analyst or create a job rec. Sana understands who I am and that I have the adequate permissions to create this job rec, and it also knows my team's budget for the role. But Sana is going to ask me some follow-up questions, like specifying what team I'm hiring in. So here it's asking me for the team, and I can submit that I want this to be for the growth team. So now Asana is compiling information and market data, and also referencing historical company and Workday data to build a job rec. So but say I wanna make some edits to this. I can review it directly within Asana. And maybe this is a bit too junior and I wanna make this role more senior. I can prompt Asana to do that on my behalf. So it's now going to adjust this role, including the compensation range and the description to actually be for a senior research specialist. So now this all looks good, and I wanna send this to Workday, and I can do that directly from Asana. So I can also accomplish other HR related tasks directly from Asana. So say, for example, one of my direct reports recently received a promotion. I'm able to update his role and status just by prompting in the chat. So let's say Alex became a senior software engineer. Again, Asana understands my org structure and hierarchy. It knows that I have adequate permissions to approve his promotion. So it's now going to adjust Alex's title, base salary, and his bonus to reflect his new role. And I can push those updates directly into Workday. Alex then will also get an email notifying him of this update, which I'm sure will be exciting for him. I'll now move on to one of my most dreaded personal tasks, which is managing my expenses. And so rather than having to individually submit each one, I can just ask Asana to handle them on my behalf. So I want Asana to create an expense report based on in policy receipts that you can find in my inbox, and I'll submit that here. So Asana is now going to search in my inbox. It's verifying my receipts against company policies. It's also referencing my calendar to understand more context around what I was doing when I spent that money. And now it's found that all but one of my expenses are within policy. Here, I bought a book that is not going to be approved by Workday. And so I can go ahead and submit this report directly from Sana. The next thing that Sana is gonna do here is actually offer to turn this into a recurring workflow. Obviously, expenses are something that I have to do on quite a regular basis. So I can set this up and templatize it so that it runs automatically in the background for me. So I'm gonna say, yes. Create a workflow for this. And Asana's automatically now putting that string of prompts together. Here, you can see now it will be triggered on the last business day of each month, and it'll follow a similar process to what I just walked through. So looking in my inbox, gathering more context from my calendar, verifying against expense policies, and then creating the report in Workday. One thing I think might be helpful here, though, is, like, anytime I submit an expense report, maybe I want my manager or the expense reviewer to actually be nudged on Slack so that they review my expenses more quickly. So I can prompt here and nudge the reviewer on Slack. And now Asana, you can see, has added one final step to this workflow. So save that now, and then I don't have to worry about handling my own expenses. I can have this running in the background. And when it comes to workflows, there are many others that can help me augment repetitive tasks in my day to day so I can dedicate more time to value added work. Here is just an example of our library of automations. And I wanna dive into one specifically, which is performance review prep. So say I'm coming to performance review season. I wanna gather some data on my performance before I put together my self assessment. This is a routine process that I am typically doing at least once a year, maybe twice a year. So we've set up a pre prepared workflow to help me do this. You can see it's going to be prompted seven days before the meeting in my calendar of yearly performance review. It's going to read my historical reviews, understand from Workday what my developmental goals are, and then it's also going to cross reference Jira, GitHub, or other project management tools that I would typically use. So I'm gonna run that now. And you can see that Sana is now instantly looking through my historical reviews in Workday. It's cross referencing my developmental goals and also the prior feedback that I've received. And now it's going a step further, and it's checking Jira, GitHub, and my meeting recordings to actually see what projects I've worked on. And then it's going to begin to compile my self assessment. And so kind of just like that with a few clicks, I've been able to create a draft of my self assessment without having to rely on my own memory of the work that I've done, but it's actually grounded in real data. And I can go ahead and submit this to Workday. The final thing that Sana will do here is actually prepare talking points for me. So it understands that I'm having a meeting with my manager. It knows the amount of time that that conversation will be for, and it's given me an agenda and talking points. So now I feel prepared for my meeting and and ready to go. I'll now head over to my inbox, and this is where Asana is going to notify me of anything it's been working on or where it might need my input. And I can actually see that one of my workflows is already in action because Asana is notifying me that one of my new direct reports, Marcus, is starting soon. So So Marcus is going to be an HR director, and I wanna see how Sana can help me with his preboarding. So it's already gone and prepped all of the key systems that Marcus will need access to based on his role and seniority. It looks like largely these are collaboration tools or the productivity suite, but it's also given him admin access to Workday given his director role in HR. And, largely, this looks good, but maybe I know that he will probably need to do some data visualization, in his role, so I want to add Tableau. And now it's updating the list of systems that I wanna give Marcus access to, and I can actually just click give access to him here, and it's going to push that update directly into ServiceNow. So now we've covered his system's access, and there are typically other communications that you might need to have with a new joiner before his or her first day. So say, for example, you need to know what Marcus's laptop preference is. Sana has already figured out that Marcus needs a laptop, and it's prepped an email for me to send to check his preferences. So I can edit that directly within Sana here. So maybe let's make this 15 inch, and then I can send this off to him from my Outlook to his Gmail. It's then going to go one step further and actually make this request in ServiceNow once it has, recorded his response. I think, like, notice no one had to tell Sana any of this. It already knows Marcus's role level team start date and who his peers on because it's reading from Workday's knowledge graph. So an exciting way to tap into that data to complete some work on your behalf. So now the last step that I will go through with preboarding is helping Marcus schedule one on one so he feels welcomed in his first week. Sana has already identified key people for him to meet across other teams. It's checked their calendars and found windows of availability. So I can just go ahead and approve these invites and send them across. So that saves me tons of clicks and a lot of back and forth between Marcus, IT, and myself. And you can see here, this was 18 tasks I would have needed to normally tap into five systems, and I was just able to do it all through Asana workflow. So those are all of the use cases I think I wanted to walk through within Asana today. I'll now pass it over to my colleague, Maruna, who's gonna talk through the road map and what's next for Asana. Perfect. Thank you, Katie, for the introduction and for walking us through, our use cases here. And once again, I welcome everybody. I want to give you a sense of what you can do in Sana today and also the exciting things coming very soon in our product through this, roadmap. So if you think back to the pillars that Katie showed at the beginning, we've really been working on the find, act, and automate layers, and we're building following soon after. So today, if, you go to Sana, you can already query your Workday knowledge sources like benefits, policies, payroll info, people from Workday, and more. In addition, you have access to a broad set of third party systems from your core enterprise apps like file storage, calendar, email, project management tools, and more. And these are live connectors, so it means that you can use live business data to provide, precise contextually relevant responses and also take action on your behalf by updating records directly in those systems like Katie showed you. But more fun, just around the corner for our June release, we really envision Sana as the main orchestration layer on top of the Workday agents and data, starting with a self-service agent and resolution agents. This will allow you not to only query that data, but also take actions in Workday and other systems for our connectors, and most importantly with human in the loop validation, keeping you in control at every step. And this is all for Otsana. You don't need to leave the platform to do all of this. This ties in closely with workflows and our interactive inbox, which Katie gave you a sense of in her demo. So for that, you can set up your workflows from the performance management reviews, preparing for sales calls, automating preboarding and offboarding, and really any workflow that you have in your daily and weekly schedule, either in the schedule or based on triggers in your systems, be it an employee starting, receiving an email, getting a meeting invite, and many more. And you don't need to be an expert to set these up. You can just describe what you want to achieve to sound a conversationally, and it will build all the steps for you. The workflows will just run-in the background, and you'll find all the results and information you need in your inbox, personalized to you, ready to review and approve. In addition, we're launching over a 100 off the shelf connectors and a deep integration with your meeting tools so you can seamlessly use the recordings as well as a source for your chats and workflows. With r two, our goal is to bring an even richer experience for all of the Workday agents and data. For many complex use cases, we recognize that you require that persistent context that you can easily get back to, and this is what we want to solve for. So imagine that in Asana, you're gonna have dedicated spaces for your recruiting agent, IT agent, travel agent, and so on with tailored dashboards and widgets for each case. So for example, for your recruiting agent, you can easily see under the dedicated page any recent updates for your candidates, your hiring pipeline, gaps in your teams, and take action on any of them with proactive suggestions by Sana as well. For an IT agent, for example, you could monitor ongoing tickets and requests, see frequently asked questions, and so on. So Sana will be the place where you can seamlessly find and interact with them within the full context of your use cases. No need to go into different systems, different places. Everything will be easy and seamless. All of this will, of course, be backed, as Katie mentioned, by the same level of governance and security that Workday operates with today with role based permissions and sharing and auditability of workflows and actions. But we also know launching and enchanting product is not enough. Understanding how people use it and how to drive change management is key. And that's why Sana will allow you to evaluate the business impact of, your workflows, your agents, and so on with actionable analytics dashboards and data that you can chat with to understand where your organization is at, where it can improve, where you can increase usage, and find more opportunities, for that in your user groups. As always, we'll keep expanding on our enterprise connectors with suggestion and discovery flows as well based on your actions in the system, role, and other data. So this is a quick taste of what's to come, and we have many more exciting things on the way. So a couple of things we're already planning for is, of course, integrating with all of your Workday agents, embedding Sonna in Slack and Teams as bots, allowing you to connect with your own build agents into our orchestration layer, and more. So to summarize, we want Sonna to be your front door to enterprise AI, bringing together your Workday data, data from your other enterprise apps in one unified interface where you can automate your workflow seamlessly. How can you get started with all of this? The first step is that you can reach out with your Workday point of contact to execute the U MSA. I saw a couple of questions about that, and the Sana Enterprise SKU to authorize your deployment. That's a very first step, and then you'll have your Sana Workspace already connected to Workday. From there, you can connect other third party integrations, ingest your knowledge sources, and enable the experience for your users. If you want to learn more and stay up to date, again, we have all the list of docs on the right hand side, and you can see all the latest that's happening on Sana on community as well. So this concludes our presentation for today. And now we're going to, go into a Q and A segment. And for this, I'll invite Katie back up on stage. Hi. We had a couple questions that were, submitted in advance. So I'll I'll kind of start. I think, Myrna, a few of them are more product related, so it would be great to get your take on this. But how do you see Asana fitting into the Workday landscape? Yeah. Sure. So as mentioned before, the way we see Asana is it being the overarching orchestration layer for AI in the Workday landscape. So it sits on top of your Workday tenant using governed governed ACM and finance data at its core context and reaching out into the rest of your tech stack. So what I was mentioning about the integrations with hundreds of connectors that already are available to you. So in practice, this means that Sana can orchestrate all of these Workday agents as well as we're planning for second and third party agents all within that single interface. So instead of employees needing to learn multiple AI tools for you worrying about where to go, you can come into Sonra as this unified front door for enterprise, and as mentioned, grounded in Workday security model, and, extended basically across your broader applications. And this is really our core goal with this. Awesome. Thank you. And what kind of data sources and knowledge is Sana actually able to work with? And and I think you touched on this a little bit, but what kind of connectors exist today? Yeah. So, of course, as mentioned, the Workday integration is fundamental. So it can search that index knowledge across your policies, knowledge sources, people directly, and that HCM finance context. And I think the other very important bucket is, the support we offer for over a 100 connectors. So, top ones that we see being used are, for example, file management systems, like SharePoint and Google Drive, IT integrating systems, ServiceNow, CRMs like Salesforce, project management from Jira, Linear, Notion, Confluence, Slack, and Teams. So it really covers a very broad range. And one good thing to know is that, yeah, they connect real time to your data, so you can get those answers, like, instantly. And similarly, you can take actions in them. And also, you can use triggers from them in your workflows, as you've shared before, Katie. So for example, if you have a new meeting invite coming in or if you have an email coming in, anything of that sort, a type of Slack message, you can actually use those type of triggers in the workflows to seamlessly integrate them into your day to day task. In the near term, we'll also have the ability to connect to any app via MCP. And, what we're aiming for is to bring this number higher to a thousand connectors depending, of course, on, what we hear from our customers as well. Exciting. A thousand connectors is crazy. We're getting there quickly. Yes. So I think those are a few of the questions with, connectors and products. I've seen also a couple that maybe I can ask you, Katie, more on the commercial side of things. Yeah. Yeah. Absolutely. Right? So we talked briefly on the road map about how we want to offer these insights into Sonam, in terms of the usage. And we know that change management is a key part of effectively deploying any AI application. So can you tell us a bit more about how we support change management and adoption? Yeah. I think at Asana, our general perspective is that no matter how good the technology is, if there isn't an adequate transformation and change management plan in place, then you're not going to end up getting the ROI that you want. So at Sana, we really treat AI as a change program rather than just a software rollout, and we pair technology with a dedicated engagement team of AI implementation experts. So these are largely people who are coming from McKinsey, Bain, and BCG backgrounds and have vast experience in change management and transformation at really large organizations. And they then co own alongside of you your adoption journey. And I think the goal here is to ensure that there's really high adoption of those use cases and also deliver measurable ROI across your org. So what does that look like in practice? With every customer, we tend to agree on a subset of, high value use cases. So we'll prioritize use cases and then define clear success metrics and also look at who the target persona is for those use cases. Then we follow a really structured implementation plan with some defined timelines and owners. But then also, I think we support throughout the duration of your contract with Asana and Workday. And so we run regular check ins to review usage and impact and measure ROI broadly. And we also work alongside of you to do upscaling, boot camps, etcetera, so that people know how to use the technology and are using it well. And so I think this is one of the really exciting offerings of Sana Enterprise is the ability to co collaborate with us and partner on this broader transformation journey that I think we see as really essential to capturing value from AI. Amazing. Thank you for giving us an overview into that. Now the next question I want to ask you is, maybe phrased a bit aggressively here, but let's go with it. Is SADA Enterprise just an HR tool, Katie? It's a good question because obviously Workday, I think, lives within the HR tech space, finance tech space, etcetera. But we really see Asana as a horizontal enterprise platform that's, yes, deeply embedded with Workday and that native integration into core HR, finance, and IT workflows exists. And I think because it's built directly within Workday's ecosystem, like, Asana does have that privileged access, to that system of record data, especially around people and money. And I think this this is a big right to win for us, right, is within the HR space. But, like, at the same time, Son is not limited to those domains while its foundations in Workday. And that, I think, gives us a unique advantage. It's ultimately designed to be flexible in a horizontal platform that extends across business functions. So this means it can support a wide range of use cases, I think, beyond HR, finance, and IT. Some of the ones that we've been talking about internally and have been building out are sales enablement, customer support, operational workflows, and also just, like, general productivity and cross functional collaboration. Obviously, as someone who's on the sales side, I'm really excited by the potential of, sales automations and workflows. And so we're building out use cases right now around RFP and due diligence creation or deal renewal processes and even things just like meeting preparation and follow-up that can really help you just do your job more efficiently so you can focus your time back on value added work. Yeah. And, we can only echo that from the product perspective, and I think the wide range of connectors beyond really empowers that. So no matter what kind of role you're in, there's really a lot you can do with Sono and the automations that we offer there. Yeah. So, Katie, I also want to ask you, what do you see as Workday's right to win within the enterprise AI space? I I love actually, love this question because I do think it overlaps a little bit with the last one, right, where we'll have this concrete advantage in HR, IT, finance, etcetera. But I think beyond that, the advantage is really deep business context and understanding of roles, responsibilities, and processes of your people. So, like, at a surface level, there are lots of AI tools that can deploy agents really quickly, but they're operating largely outside of your core enterprise knowledge graph. And so it's hard for them to be doing jobs correctly with the right permissions and the right information. So when you think about Sonnet Enterprise, you actually have access to that authoritative people and money context. We think that agents can only be as as effective as the data that they're acting on. And with Workday, agents are understanding real time hierarchies, reporting lines, roles, definitions, and even financial controls, budgets, etcetera. And so I think without this, your agents are operating maybe on stale data, partial data, or you're having to do, like, really complex integrations to reconstruct that context outside of Workday. I think also we have native governance and this control layer, and, ultimately, agentic systems need guardrails to work. Workday already encodes these rules, and I think without it, governance has to be rebuilt externally. And we've seen that that leads to a lot of shadow automation, compliance gaps where you just broadly don't understand what's going on with your I AI across your organization. And then finally, I think Workday offers this unified orchestration because it's already been designed to be a system of record control in orchestration. And it provides really that, like, safe org wide scalability that's aligned to your organizational structure. And it just, in general, helps you, I think, manage cost and ROI and keep consistency across your business units. Great. Thank you for that. I think maybe one thing that I want to quickly address as I saw it popping, quite a few, quite a lot in the chat is, the connector availability. So everything I mentioned, all the connectors I mentioned, so far are already available in Sana. We have roughly, we have 90 over 90 connectors available today. So all of these, you can already access and use in the context of Sana Enterprise as, Katie, described the differences there. Fantastic. So this, brings us to the end of our time for today. We'll finish up a bit earlier, and we're been answering the questions in the chat. If you haven't gotten a response yet, we will make sure to cover those topics or get back to you for sure. And as Erica pointed out, we'd love to hear from you. So please, feel free to fill out the survey. This will help us learn more about your impressions, what you'd like to see more in future calls as sorry, future calls with us as well. And as a final reminder, in the doc section, you can register for our next webinar and learn more about Sana as well as get a demo of Sana from your Workday representative and our team. Awesome. Thanks, everyone, and thank you for joining. Thank you.