Name: Simplify Your Path to Workday Innovation: UMSA and Data Contribution
Uploaded: 2026-09-02T17:30:50.247Z
Duration: 58 min 40 s
Description: Simplify Your Path to Workday Innovation: UMSA and Data Contribution

Transcript for "Simplify Your Path to Workday Innovation: UMSA and Data Contribution": Hello. Thank you so much for joining us today for this looking forward with Workday webinar, where we will discuss how to simplify your path to a contribution. During this session, we may share a few forward looking statements that are subject to change. Please note that they are covered under our product statement, and I'll give everyone a moment to review the product statement while we let give folks an extra moment to join the webinar. My name is Marie Francis. I'm on the product marketing team here at Workday where I focus on our commercial model for AI. And I'm joined by Bridget Hoffman from our global legal services team. As the new technologies and opportunities of AI are changing all of our workdays, we are hearing both enthusiasm and customers want the incredible capabilities of AgenTic AI, Asana, and data transformation, and they wanna adopt these innovations with the confidence that they are mitigating risks and focused on business value. So today, Bridget and I will dive into how the universal main services agreement or UMSA helps your organization confidently move forward with innovation adoption. Then I'll discuss how the flex credit model for usage based AI helps you get started with reduced risk, helps you see the value, and scale with confidence. We're gonna answer many of the common questions we hear from customers about the UMSA and flex credits, and we're gonna save plenty of time for your own questions that you brought with you today. Just a few quick guidelines about the webinar to you're muted. Take a moment to locate the q and a tab so you can submit your questions at any time throughout the session, and we'd appreciate it if you completed your survey at the end of the, webinar as well. See, we've got some freezing. Okay. We'll keep going and find out if we've got a challenge here. So great. I'm back. So today, we're going to cover the UMSA as your pathway to innovation, how to move to the UMSA. We've got a self-service model, or you can work with your account team. We will talk about how you can control your data contributions and the flex credit model, how it gives you fast, frictionless access to AI. We're to save some time for questions at the end. So to get us started, Bridget Hoffman from our global legal services team is gonna dive into the UMSA. Sounds good. Thank you so much, Marie. Let's dive right in. So our new UMSA is designed to make it much easier for customers to take advantage of Workday's latest innovations. Most importantly, it gives faster access to new AI and agentic products, including Sana platform and Workday agents across HR, finance, and IT. So that means customers are not waiting on lengthy contracting cycles or additional paperwork every single time a new capability becomes available. Instead, the new UMSA creates a more flexible foundation that allows Workday to deliver innovation faster and customers to adopt those innovations even more quickly. So a key benefit here is that customers no longer need extensive addenda for each new product. This helps simplify the process. It reduces some friction for everyone and also accelerates time to value. On the other hand, choosing to delay the migration creates some real limitations for customers. Customers who remain on older agreements may not have access to new Agentic products, may not be able to use flex credits, and may actually be locked out of next generation innovations including Sona enterprise. It can also make renewals a little bit more complex and prolonged because the agreement structure has to be addressed later under more time pressure. So moving to the new MSA is not just a commercial or legal update. It's a foundational it's a foundation to start accessing Workday's next wave of AI agents and the platform innovation itself. So customers sign the universal amendment to the MSA, which actually layers on top of their existing agreement. It becomes effective either with an order form that references it or a stand alone amendment. The current MSA still remains in full force and, in full force except where specifically amended. So what changes here is just the structure. We're moving to a product agnostic baseline set of legal terms, replacing the product addenda with product terms, and introducing enhanced features frameworks with explicit AI and ML feature lists. Which of these are in instance data contribution controls for most products? Workday also provides thirty days notice for changes to existing product terms. What's staying the same? It's the customer's core MSA. So this is not a renegotiation of their legal terms. It's a structural update here that gives Workday and customers a better framework for delivering and adopting innovation. So how do you move to the UMSA? Kind of how I started to address it, but there's two main ways to move to the new UMSA. First is at a subscription renewal or another sales event. The UMSA will be provided with the customer's next renewal order form. And by signing that order form, the customer moves to the new framework. This may change feature enablement steps, but it doesn't change the feature availability. The second option is an early migration. So customers can sign the early UMSA migration amendment outside of a sales event if they want to move in a little bit sooner. However, this might not be available for customers purchasing through a reseller or through certain vehicles such as NASPO. So the key takeaway here is that customers can migrate either through their normal renewal process or where available or through an early migration path including our brand new pre signed UMSA amendment, which we have linked here on this slide. We just wanna quickly show you here what the UMSA amendment community page looks like. If you scroll down on this page, you can read more about the MSA as well as navigate to the link to execute our very simple pre signed amendment. So now let's quickly take a look at some common questions and concerns that customers may have about moving to the new MSA. The first concern that we can hear is, will Workday train on my data? The answer is that customers shouldn't have to worry about uncontrolled use of their data. Workday will only use customer data to train or improve AI systems as permitted by the agreement. And for most products, customers will manage Workday's use of that data through their own instance configuration. Second, will I lose control of said data? Again, the answer is no. In fact, the new framework intended to provide more visibility and more control than ever before. For most products, customers can manage Workday's use of their data directly inside of the Workday instance through an updated user interface. So rather than relying on only contractual language, customers also have the operational controls within the product experience. A third concern is around dynamic terms. Customers may ask, does this mean that Workday can change anything at any time on these dynamic terms? The answer is no. Dynamic terms are not limited. Workday cannot make updates that materially decrease the customer's security, privacy, or SLA protections, and changes to product terms actually require a thirty days notice. The purpose of dynamic terms is to allow Workday to continue innovating and improving products over time while still maintaining the important customer protections. A fourth concern is you might hear customers need to redline this before they sign it. The important message here is that the UMSA migration is not primarily about changing the customer's contractual bargain. It's about updating the agreement structure so it actually aligns with Workday's new AI delivery framework. That way customers can adopt the new AI functionality more quickly without unnecessary contracting delays. Customers may also ask, do we have to renegotiate our contract? The answer is no as well. The purpose of this new agreement is to give customers faster access to the new AI functionality. It's not intended to be a retrade of core contract terms. So the net net in summary here is that the UMSA gives customers better access to innovation while still preserving meaningful protections and giving them more visibility control over how their data is used. Two more common concerns. Some customers may want to keep their old MSA. The old MSA may feel very familiar, but it was not built for the way that Workday is now delivering AI and agentic innovation. The UMSA creates the contractual foundation that allows customers to access these capabilities more quickly and more efficiently. There is a deferral process available in certain cases, but it's important for us to set expectations here. The deferral process does not remove the need to migrate. It only pushes the migration to the next renewal. Customers can defer in some circumstances, but staying on the old MSA means delaying access to Workday's next generation of AI capabilities. After a UMS activation, customers have fourteen days to adjust their data sharing settings before any data is shared. So they can also opt out of specific enhanced features, including disallow data contribution would be for when anyone is concerned about how data is being used for AI. So let's go over some of the key changes that the MSA addresses. So some of the structural updates here, one of the first ones would be the shift from the term tenant to instance. Historically, Workday used the term tenant to describe an environment that was generally associated with specific sets of product lines and hosted in a single geographic region excluding backups. As Workday has expanded into new product lines and introduced more AI enhanced features, the model has evolved. Customers may now have multiple instances supporting different products or capabilities, and those instances may involve different data storage locations depending on the product in the future. So the language is being updated to better reflect how Workday's platform and product architecture works today. Rather than committing that an instance will be hosted in one specific region, the UMSA uses a more modern framework that reflects the broader range of AI products, AI capabilities, and data storage models now available. That being said, this change does not mean customers lose any visibility. Workday is providing a list of all data center locations and customer business teams, including name support contacts, that can access the linked information to verify their location instance. Let's move to the next shift. So a new terminology update here is the shift from customer data to customer content. The purpose is to consolidate different data types into one unified term. Previously, the agreement used separate categories for different kinds of information such as innovation services data and extend data. So under our new framework, those are grouped together as customer content, which covers the electronic data or information customers submit to service. The contractual benefit here is that this updated language brings Workday helps Workday to deliver enhanced features. And as identified in the applicable product terms, it also simplifies the agreement structure and makes it easier to provide new capabilities to customers. A key message here is that this is a simplification of terminology, and it is Workday and customers a more consistent framework for supporting enhanced features under future innovation. Okay. So how is Workday simplifying customer obligations under the new UMSA amendment? Workday is moving customer obligations concepts into the main agreement instead of keeping them spread across separate product agenda attached order forms such as MediaCloud or the innovation services agenda. The benefit of a universal set of customer obligations that applies across Workday products and service skews. This creates more of a consistent and a streamlined contracting structure. Examples include the customer's responsibility to ensure that they have necessary rights to use a service and to comply with applicable acceptable use policies for the relevant service applications. The takeaway here is that this is about consolidation and consistency. Customers get a common set of obligations across the Workday portfolio rather than having to track separate obligations across multiple product specific addenda. Now let's let's next go over Workday's move to the universal exhibits for security and data processing. Our goal here is a universal standard. Under the UMSA framework, customers operate under the universal security exhibit or the USC and under the universal data processing exhibit or the UDPE. What is changing is that customers now have one single set of USC and UDPE terms that apply across all service SKUs. Previously, different service SKUs could be governed by different security or data processing terms. So, for example, an extend SKU may have its own set of terms that differ from other Workday services. A benefit to moving to the universal exhibits is consistency and simplification. Instead of managing different security and privacy terms across different SKUs, customers can get one framework that applies across the workday services that they use. So this makes the agreement easier to understand, easier to administer, and better suited to a broader platform model where customers may adopt multiple Workday products and enhance capabilities over time. So how is Workday expanding the compliance reporting framework under the MSA? What's changing here is that Workday is moving from a narrow audit framework to a broader, more future proofed approach. Historically, the focus was primarily on SOC one, SOC two, and ISO certifications for more core Workday products. Under the new structure, Workday is expanding its obligations around audit report compliance to better reflect the full Workday ecosystem, including new products and acquired products. That means the scope now includes other third party assessments where applicable. This is important because Workday's product portfolio continues to evolve, and customers need compliance reporting model that can evolve with it. From a customer transparency perspective, the reference details for the expanded scope are available in our product terms. Customers can also access all in one compliance charts on the community portal. The chart maps applicable auto reports to each product line, giving customers and their name support context clear visibility into which reports apply to which areas of the Workday portfolio. So a key takeaway is that this change gives customers a more comprehensive and scalable compliance reporting framework. It expands beyond the core product only model and provides a clear visibility across a broader Workday ecosystem. Next, let's go over how the product addenda, is replaced versus product terms. Historically, Workday's base MSA was designed around core services like HCM and financial management, and product specific addenda were only used when additional terms were needed. That structure no longer fits the way Workday operates today. So Workday's updated model is AI centric, a platform for managing people, money, and agents, all of that with AI increasingly built into the core experience. So under the UMSA framework, prior product addenda are terminated and replaced by new product terms. This gives Workday and customers a more scalable and a more consistent structure for supporting a new AI and agentic capability. Now let's take a look at the changes around our limitation of liability exclusions. Customers are required to comply with the acceptable use policy or AUP that's referenced in section four of the MSA. The AUP sets expectations for how Workday services may or may not be used. Because those acceptable use obligations are part of the customer's responsibilities under the agreement, the limitation of liability section needs to account for situation routes where those obligations are not followed. In simpler terms, this section helps to ensure that if a customer uses the service in a way that violates the AUP, the standard liability limitations may not apply in the same way. That gives Workday the appropriate protection for misuse of the service while still reinforcing that customers are responsible for their using of their service in accordance with the agreed acceptable use requirements. Customer outputs. As of June 2026, the UMSA amendment confirms that customers own their own AI outputs. That directly addresses a concern that customers often come to us with. Who owns the results generated by the AI functionality? The answer is that the customer now does. The amendment also confirms transparency commitments, including for acquired for products. That's important because Workday's product portfolio continues to grow, and customers need consistent visibility across both native and acquired capabilities. In summary, customers retain ownership of AI outputs, and the MSA provides clear transparency commitments around the broader workday ecosystem. Now I'm going to hand it off to Marie to go over our data contribution model. Thank you all for letting me know I was on mute. I'm so excited to tell you about this. I'm excited to start over. So let's start about how we activate AI. Because as Bridget just discussed, when you sign the UMSA, AI features are delivered enabled to your tenant. Am I still on mute? Let's fix this. No. I think we're clear. Great. Thanks, everybody. Okay. So AI features are delivered enabled to your tenant, and, some features require require configuration before you can get them started. Now you have the option to disable data contribution. You can manage this at a feature level or for an entire product line. I'm gonna show you just how easy that is. One exception here is advanced search where data contribution cannot be disabled. So once you've configured and activated the AI features, you get immediate benefit from the AI. You do not have to wait until you a lot of data has gone to the system. The AI is gonna deliver a benefit to your, to your instance, to your use of Workday right away. So let's see how easy it is to control your data contributions. You can, with a single checkbox, disable AI features at data contribution for an entire product line. You can also exclude data contribution for specific countries only, again, with a few simple clicks and pick lists. You can click into view data collected to confirm what data is and isn't being collected. So let's also see what that looks like. And as you can see, it is very, very simple, very clear about what data is or isn't being contributed, and you can confirm once you've opted out that, indeed, that data is not going into the system. You can also see the different definitions of the data so you have complete clarity into your data contributions. We want this to be easy for customers, so we've really tried to make it as simple as a few clicks. So, we also have our AI fact sheets available. They are highly detailed, gonna answer a lot of the questions that I've seen now about what type of data is contributed for different ML and what's not. All of these are readily available on Workday community. You can get them right away. You can share them with the folks you need to in your business. We wanna make sure that our customers have the information, and we're giving you guys the transparent needs the transparency you need to move forward with confidence. So as Bridget mentioned, we have, strong policies around how we notify customers about new features coming. So let's go over that one more time. We will provide notifications to your selected users thirty days before the release of any new or updated ML feature. An email will also be sent out to the users you have configured in your tenant for such notification, so you're in control of who finds out and when. You're in control of who finds out and how. And there's gonna be an additional reminder once the feature is actually released. And if needed for the feature, data contribution only starts fourteen days after release, so you also have time to make some decisions. So now that we discussed how the UMSA and controls in Workday allow you to manage your data contribution, let's discuss what else happens when you sign the UMSA. You get access to our incredible agents in Asana through the flex credit model. Workday flex credits is our usage based pricing model for AI and platform innovations. Flex credits charge for the actual work AI completes on your behalf, And that means your investment is tied to usage and the value you get, not to your headcount. And this change is rooted in the fact that agents and AI innovations are fundamentally different from software. They take actions on behalf of your people, and the more you use them, the more value you gain. Our approach to AI pricing delivers measurable value to customers, not runaway AI costs. Our guiding principles for the flex credit model give customers the safety and support you need to take advantage of the transformative, capabilities of AI without the pricing pitfalls that you might have seen elsewhere. Our model offers simplicity. We have a single credit type for usage based AI, not multiple currencies. Our model offers predictability. We have a standard subscription purchase with locked rates, not unpredictable monthly bills. We offer value. We meet our completed AI tasks and clearly defined actions, not every token used. And we offer you control. We offer the data and the tools that you need to move forward with confidence, not unmitigated risk. So think of the flex credit model as a four step process that allows you to get started with agents and sauna at no cost. You start by testing before you invest, then you can see how your usage is delivering value to your organization with data and tools. And when you're ready to scale, you buy a flex credit subscription. And as your strategy evolves, your credits shift with you. So let's walk through the model in detail and see how customers can get started. With our flex credit model, you can test before you invest, and it all starts with signing the UMSA. When a customer signs the UMSA, they receive their complimentary flex credits, which are based on your employee size. It's enough credits to explore agents and test in production, and you get them annually on January 1. You get free nonproduction testing for most agents in persona. You get access immediately to the generally available agents that are entitled by your underlying products, both in production and nonproduction. You get access to Asana in Workday, and your tenant security admins will receive the setup AI admin security permissions tasks in all prod and non prod tenants to help you set up your configurations and get moving. Using Asana or agents in production will consume credits. That's what your complimentary credits are for, to help you get started and get real data so you can move forward with information with real information about what it means to your business. But remember, you control what happens in your tenant and your environments. Agents do not turn on automatically. You decide whether they are activated, and you decide who uses them. Next, you can see your usage and the value you're getting through two main tools, the platform consumption console and the agent system of record, both of which are simply available to our customers. They are these are not separate SKUs you need to purchase. The platform consumption console is the source of truth for your credit usage and balance. Importantly, the PCC is available in nonproduction with unlimited credits, and that's how you can test and plan before you spend. In PCC, you can see in-depth metrics on your credit consumption, identify specific activities that may be triggering higher credit burn, and you get automatic alerts at eighty, ninety, and a 100% of credit usage, so you're not surprised when you approach a negative balance. Importantly, please know, we do not immediately turn off access to any agent or technology because of a negative flex credit balance. Your people will not see an error message mid compute, and you won't have to suddenly shut off things that you've been using that are valuable. If you exceed your available credits, you work with your account team to get your credit the credits you need. Plus, you can configure the PCC right now and see your API usage. This does not mean that your API usage is being metered, or charged. It's we wanna give customers the ability to see the data that their needs need to move forward. If you, without the signing signing the UMSA, configured the PCC today and saw your API usage, please know that does not mean you are getting charged flex credits. So the next tool available to help you manage your, your agent AI use is the agent system of record. This is where you activate and manage your agents across the agent life cycle, and the agent data it gives you helps you understand the business value that you're getting for agents. You can see who is using agents and how with detailed logs of agent input and output. So our AI model is gonna help you budget for AI and not budget for surprises. Because with the real usage data and free nonproduction use for most agents in Sana, we're gonna help you scale with confidence. Buying a flex credit subscription scales your AI with predictable pricing. It's a bulk annual purchase of credits that draw down as you use them. Your rates are locked on your rate card, which is on the order form when you purchase flex credits. So you're protected from rate increases, but we still give you the benefit of any rate reductions that may take place over the term of your, contract. Real usage data from your company credits and a detailed estimation with your account team are gonna take the guesswork out of how many credits to purchase. And you can buy additional credits on Workday marketplace at your negotiated rate. That's a new capability that we just recently released and we're really excited to put in customers' hands. When you buy flex credits, you also sign the flex credit and platform entitlements policy, which defines your platform entitlement and the annual application API use included in your subscription. The platform the platform entitlement is based on your size and the products you use, and we have designed these levels to account for so so that the majority of Workday customers have their API usage accounted for. But in the event an overage does occur, you do pay for that overage with flex credits. And we recognize this is a change for many customers. That's why we're providing you the data you need for this change. As we mentioned, you can see your API usage right now in the platform consumption console without signing anything. And we also have new API reports available to customers, and these API reports help identify which integrations can be driving higher usage so you can start making adjustments if needed. Finally, the last piece of our model is that flex credits shift with you. We have one type of credit for simplicity. You don't have to juggle multiple credit types to use different agents or innovations. You receive access to new agents the moments they are made available, provided you have the underlying SKUs that support them. And you already have the the means to use them with the UMSA. No new procurement cycle or logging a ticket. You can start experimenting right away. That's the flexibility of the flex credit model. So let's talk about where flex credits apply. Sana is part of the flex credit model. Sana for Workday, previously known as Sana Core, is the new UI for our Workday agents and gives you access to Sana capabilities right in Workday. Using Sonnet in Workday in production consumes credits. And remember that Workday meters completed tasks, not every token used. So if you prompt Sonnet to use an agent, metering takes place when that agent completes the task. We do not meter the request for that agent or the prompt for that agent in addition to the work that that agent is doing. Sana Enterprise is also part of the flex credit model. Sana Enterprise has a subscription that includes a usage entitlement that if exceeded, use above that entitlement will consume flex credits. Agents we discussed are part of the flex credit model, and all generally available agents and platform capabilities listed on the rate card today, plus all the new agents and capabilities as they become available, we use flex credits. Platform innovations like Workday data cloud and agent ready tools will consume flex credits. Pricing and packaging for these products is still underway, and you will know when they are generally available and pricing is ready. And all of this innovation is possible thanks to Workday's over platform, and that's why platform entitlements are part of the flex credit model. So let's take a moment to talk about the value of the open platform. Historically, our platform was something of a walled garden for data access. But now customers are getting exceptional value from our investments in open platforms, such as more open APIs and enhanced integration tooling. Today, Workday interoperates seamlessly with your entire infrastructure and powers enterprise AI. And this tremendous shift has led to an increase in usage that we've never seen before, and we know it's going to continue to grow exponentially with AI adoption. And this jump also tells us that customers are seeing meaningful value from the platform and the investments we've waited opening it. And with the flex credit model, we're gonna continue to provide this exceptional platform, continue to open it up, and expand the value that you get from your Workday investment. So let's talk a little bit more about how platform entitlements work. In the flex credit model, you receive an annual platform entitlement, which defines how much use of application APIs are included in your subscription. Application APIs are traditional APIs built for sending data between static applications. Not every API you have is in tie is metered under platform entitlements. Much of your API use is simply included and doesn't come under doesn't, count against your platform entitlement. We have very detailed documentation and community that's gonna help you understand what is metered and what is not. But at a high level, if it's something that, if it's an API that is connecting Workday products to each other, you're not going to need to that's not gonna be metered against your platform entitlement. Application APIs do differ from the new agent ready tools that share data between Workday and third party AI and agents. And when those agent ready tools become available, they will not be part of platform entitlements. They will be a separate product. The platform entitlement level is a fair usage level for all customers that covers normal activity based on your size and your SKU footprint with fees only applying if your usage goes beyond what is considered fair. And these entitlements were set by analyzing typical use and expected growth across all customers with similar profiles. So what does that look like? A customer with a 100,000 employees has a higher entitlement than a customer with 50,000. In addition, customers with student, accounting center, procurement, extend, prism, or financials has a higher API entitlement than customers without those products. And if your application API usage exceeds that entitlement, you pay for that additional use in flex credits at the rate defined on your rate card. Today, that rate is 60 credits per 10,000 API calls, making making each call over your entitlement a fraction of a penny. And it's important to note that usage above entitlement isn't inherently a bad thing. It's a signal that you're gaining a lot of value from your Workday platform more so than the average customer. And if this excess use is you decide is not driving value for your business, there's probably ways to optimize your API use. Work with your account team to help identify the opportunities to optimize. We are here to help you. We want you to get the most out of your Workday investment. Our motivation is not to get you to use every credit that you possibly can. We want you to work together. We wanna continue to be your transparent partner in this AI transformation. We recognize that this is a big change for long time customers who have never had to examine their API usage in this way, and that's why we're offering an API grace period. Between 05/30/2026 and 01/31/2027, customers will incur no overage charges for application APIs. At the end of the grace period, customers who have signed the flex credit and platform entitlements policy will receive their platform entitlement. Their entitlement usage will be reset to zero. Use of application APIs will resume metering, and any use over the entitlement will incur flex credits as we've already discussed. So we really encourage customers to take this opportunity to look at their API usage, take the time to make the optimizations they need, and in the new year, get ready to move forward with the transformative AI that your business is looking for. Now I'd like to take a moment to look at the flex credit rate card and go through an example of credit use. This is just a snapshot of the card of a few of the agent platform capabilities we have today. As you can see, the rate card clearly defines the skills and capabilities available now and how many credits are used for those skills. And remember that one flex credit starts at 10¢. So let's look at payroll agent, which has multiple skills. You can activate at the skill level in agent system of record. So you only need to start with the skills that you know you want your business to use without worrying if activating that agent is going to incur usage and skills you're not yet ready to use. You just don't turn those skills on. So that first skill, payroll data monitoring and notification, monitors for errors before payroll is run and consumes credits based on the number of worker records run. To estimate your flex credit usage for this skill, you need the number of payroll cycles in your business and the number of workers. These are both predictable numbers for your business to get you a really strong estimate. Lastly, you'll see API requests on this list. And remember that these rates apply only if you have signed the flex credit and platform entitlements policy and if you exceed your entitlement. And if you were to exceed your entitlement, each API request over the entitlement is only point zero zero six credits. So at ten second cents a credit, that's a fraction of a penny. It takes a significant amount of API usage to end up in a bill that's gonna be a problem for your business. So now that we've seen how the MSA and the flex credit model helps you get access to Workday's AI and innovations with the control and transparency you need, let's talk about your next steps. You can start the MSA process today on Workday community as Bridget described. The self-service process makes it really quick and easy. Average turnaround is only two days, and I have heard that it can be as fast as one hour. So maybe one of you on this call today will beat that record and convert to the UMSA by the time this webinar is over. And as always, your account team is here to help you. If self-service isn't right for you, reach out to your Workday account team. You can also request a discovery session to evaluate how to get started with Workday agents, Asana, and new innovations like data cloud. Your team can analyze your historical usage data and planned AI use cases to help predict your credit needs. We are your partner for AI transformation. We are here to help, and we want to do this together. So let's now welcome, to the group Maria Engelson from our global legal services team who's going to help us answer some of your questions. Welcome back, Bridget. Welcome back, Bridget. Okay. Thanks for joining us, Maria. Okay. See that Sarah Travis has asked, could you run AI engines through your entitlement credits if you're not over your API usage for the year? So if Maria, I believe you're on mute. Yes. Good, Marie. I'm gonna let you finish the question that you start, and then we'll. go through to some other questions in the chat. credits allow you to you, help you use agents in production. If you have signed the platform and tie the flex credit and platform entitlements policy and your API usage is being metered, if you go over your entitlement and you have not purchased any flex credits, it will start to consume your complimentary credits. So the platform entitlement doesn't enable any API, any agent usage. But if you go over your API usage, it will consume your flex credits if there's no other credits available for you to use. So if you want to try some agents without, if you want to reserve a group of your complimentary once you sign the UMSA, you are not yet being metered for API usage. So you can test and experiment with agents without API metering. So my recommendation in this case would be sign the UMSA, get your complimentary credits, make a plan for how you wanna use them to get started, and that's gonna give you the data you need to move forward. But there's really not a scenario where you can, there's not a scenario where you can take the usage for your APIs and apply them to agent use. It doesn't work that way. Thanks, Marie. And I hope you can hear me now. I was I was gonna do this so that we kind of shift a little bit between the contrast, questions. and the commercial questions. And, Marie, you've been talking a lot, so I'll give you a little bit of a a pause here and move over back to Bridget. Bridget, we get a lot of questions in the chat around data contribution. And, obviously, it's important for our customers to stay in control over data contribution. So can you can walk us through that again? Does is the customer able to control data contribution for all products or just some of them? And, also, if you do nothing, is data gonna be collected by default? Or how does that work? Can you request it again, please? Definitely. So customers control data contribution directly within Workday. So under our UMSA framework, customers can use the data contribution for Workday AI task report. It's in their tenant to review any enhanced features, and they can see what data may be collected and manage whether that data is contributed or not. So controls are actually available on two levels. They can disable their data contribution either at the individual enhanced feature level or also at the product line level. So if data contribution is disabled at a particular product line level, contribution is disabled for all features within that product line. So, basically, it could be product by product, but it can also be on an individual enhanced feature level. I also saw. some questions around some dynamic terms and why we have those, and I'm happy to address that as well. Someone asked why do we have dynamic terms, and Workday does use dynamic terms because of our service, our legal obligations, security practices, and product capabilities that we need to evolve over time. So the MSA is designed for one to many SaaS model. So certain operational and product security, privacy, and data processing terms will need to stay current without requiring a separate contract. So this will be helpful so that we don't have to require a separate contract amendment every single time there's a new product enhancement, a legal update, or a new security control, or change in applicable law. So dynamic terms also allow Workday to give customers current product specific information as the service evolves, And it also keeps the core MSA product agnostic and consistent across customer base. Importantly, it's not intended to reduce customer protections, but Workday does commit that security and privacy commitments will not be materially reduced. And certain product updates do not become effective until thirty days after publication. Thanks so much, Bridget. And maybe we could also, we have, responded to many of the questions, directing people and you covered it a little bit as well to the customer facing migration page on community where we have where we have FAQs and we have an an annotated amendment, which goes through line by line, what we're changing. And we're also responding to some of the common questions that we get, around dynamic terms and data contribution, for example. Maria, handing it back over to you. One of the questions that we're getting is around Sana. And, if you need to purchase a specific SKU in Sana, maybe you can, go over again how the the free usage, works, the promotion that has been going. on for a while. here. There are some questions on that. Yeah. Thank. you. So when a customer signs the UMSA, they are able to set up Sono r. a okay. So feedback. So when a customer signs the UMSA, they are now able to set up Sono workspace. By setting up the Sonna Workspace and giving users, security access to Sonna, your users will get access to Sonna within their Workday environment. They will have access to Sonna capabilities, which are defined on the rate card, and they will be able to use Sana to call whatever Workday agents may also be available to them. In addition, Sana Enterprise is a product purchase with a SKU that entitles a certain level of Sana usage, and above that usage, you use flex credits. Sonnet enterprise is the way to use Sonnet to integrate across your, your tech stack and connect Sonnet to your workflows across your business. So Sana in Workday is available with the UMSA, and Sana to integrate across your business and be the front door for work is a product purchase. I hope that's helped. Hope that helps. Yes. That's that that's good. Thank you, Marie. And I'm looking at the, out votes that we're getting to here, in the in the chats. And, a lot of, a lot of questions, are circling in the uploaded ones around predictability, how much, you will have to pay or how many flex credits, are gonna be used for, your use of of agents. And, can you go over that again, please, Maria, and maybe drill down a little bit in more in detail how customers can make sure that they have that visibility and control? Yeah. So the best thing to do is plan a session with your account team so you can go through the way the different types of agent capabilities that are available, how you think you might use them for your business, and your account team is going to get access, is going to be able to access and share with you historical usage data that's gonna help inform your flex credit purchase. This is the best way to understand what your credit needs might be. I've also seen customers, get extremely proactive and dive into the rate card and use the rate card to make their own calculations. And that's another great approach as well if you want to do that work of really, I think of it as kind of a self-service estimation. It is absolutely possible with the data on the rate card to come up with your own estimation and then validate it with your account team. But your account team is here to help you. We have calculation tools that are gonna take into account your intended data that's gonna help get to the right number for you. So, again, we are here to partner with you on this. We wanna help you find that right number. We wanna help you right size based on, your. plans. Will you get a notification? I'm sorry. I was gonna ask, Something you get a notification when you're starting to get looked at the. yeah. So, in the the platform consumption console, you receive alerts at 80%, 90%, and a 100% of your credit usage. So you don't get surprises when, should your account, be approaching zero or go into the negative. My recommendation to folks is when you're setting up the PCC, think about who needs that information because it's platform consumption console admins. People have admin rights to the PCC who are going to be able to see that data and get those notifications. So it's a great moment to kind of as an exercise in your business, ask the question, who's going to need to know what our credit consumption is? Because those folks are going to need the role of PCC admin. And one of just flagged folks, if you, look. over next to the chat in the doc, you can go right to, the Workday flex credit page on community. I know we get a lot of questions about, like, what types of APIs are and are not included in platform entitlements. We have really detailed documentation that's gonna help you understand. And, of course, your account team is always here to help. But a lot of your questions have the documentation available, and we are constantly working to improve and provide the additional detail that our customers need as questions are coming our way. So if you do have a question, I'm also happy to drop in the chat a link directly to, the specific information around platform entitlements, inclusions, and exclusions. Because we really want folks to remember two important things well, three important things about platform entitlements and API usage. The first, the UMSA is not what triggers API metering. No API metering takes place until you sign the flex credit and platform entitlements policy. That takes place when you purchase a flex credit subscription. Number two, not all API usage is metered. And number three, we have the API grace period. So between now and 01/31/2027, no API, overcharges will take place for customers who have signed the policy. So I saw some other questions in the chat here as well. One anxiety that I see is, will there be a log of dynamic changes? And, actually, yes. Workday does publish updates through its standard customer communication channels. So customers actually have the ability to subscribe to the universal contract terms update. We have a notification form on community. So that way customers can receive notifications when there's any applicable dynamic terms that are updated. For product terms, updates are published on Workday's universal contracting page, and those updates don't become effective until thirty days after publication. I also saw another good question. Ellen asked, is there a single document that explains what it means to contribute data and how our data is safeguarded when contributed and how, privacy is ensured? So good starting point is the supporting privacy and Workday AI features document. It provides a general overview of data contribution, privacy roles, customer controls, model training, and safeguards. For specific details on a specific AI feature, we have applicable AI fact sheets that actually provide an exact data processing, detail for each product line. And it also goes over our training approach and our privacy and security considerations. I also saw another question in our chat. Marie, maybe you can answer this one. Does moving to the UMSA change our current subscription cost? No. Absolutely not. Thank you so much for bringing up that question, Bridget. I'm very glad to tell people. Absolutely not. Signing the MSA or being on the flex credit model has no impact on your underlying products, your underlying, your underlying product pricing. That's awesome. That's great to know. Let's see. I'm gonna there I'm gonna. give it a try. I know my my audio sounds stable, but, how are we gonna share information from this one? Are people have been asking for, recordings or the slide deck? And what about the q and a? I know we have a big team trying their best to answer all the questions that come in, but are we gonna, share any of those answers as well? Yeah. To be determined, it sounds like. But but, what I can say is that there is. this migration page, that I mentioned, and we're constantly updating it. So, the the feedback and the type of questions that we're getting from this webinar is gonna help educate us on what questions costs have as they're migrating. So we'll make sure that migration page keeps getting updated. And if we're able to, we can post some of the resources from this webinar as well. And all your questions. are being logged and we will make sure that they find their way into our FAQs and, the resources on that migration page. On that migration page, there's also a click through agreement that you can use to get to the UNSA without having to, work through, your account manager. If that's a simpler way for you to do it, you can do so on that migration page. So, Yeah. Maria, it looks like we'll be sending a recording and following up with some q and a responses afterwards, and we'll also be sharing the presentation as well. Sounds great. So I do awesome. see that we're still getting some questions about, Sonicore versus Sonic enterprise. I know we talked about this already, but really want folks to walk away with a clear understanding when, because we have, we are retiring the term Sonacore, and I think that might be causing some confusion. When you sign the UMSA, you get access to Sana, and that is what we have previously called Sonacore. Sonicore shows up in your Workday instance. Your customers pardon me. Your user our customers, you, our users, can use Sonicore, as soon as you sign the MSA. Using Sonicore in production does consume credits. Sana enterprise is a separate product purchase. And, with with Sana enterprise, you gain the ability to connect Sana across your tech stack and help make Sana a front door for work and connect your workflows across your business. That product is a separate purchase, and it comes with a, base usage entitlement. And then use above that, incurs flex credits. It's a really great moment to talk to your account team about the opportunity of Sana Enterprise. We have seen customers do the most extraordinary things with this product. I'm not even going to begin to try to describe it in two minutes. I'm not gonna do it justice. But it's a similar structure to platform entitlements where there is an amount of usage that is already available. It is a generous amount designed for you to get an an extraordinary amount of value from that purchase. And if you are, happen to be using Sonos so much and it's starting to drive your business, which we do see happen, you're going to start to see usage, above your retirement level, and that doesn't car flex credits. Again, usage is tied to value. We are metering for completed tasks. We're metering for work done. It's not every token used. And so I really encourage folks, I think part of the AI mind shift here, which is challenging, is that usage is value. If you're using it to that level, you're getting great things out of it. So if there's something I could kind of encourage everyone to think about as they're going through this, it's that if you are using something a lot, it's driving value for your business, and you're gonna have the data to confirm that. Thanks, Marie. My pleasure. And then we get so so many good questions and, there's so much activity which which is great to see. There will be more of these kind of webinars. And so we encourage you to to join in on those or work with your account owner with the questions that you have or go on the migration page on community. We're going to wrap this session up by thanking Marie and Bridget for, doing, great presentation with so much fact stuffed in there. I'm glad that we're able to share the the presentation with everyone after and the recording. And, with that, thanks for all the great questions that came in. Thanks to our presenters, and, see you next time.