Name: Claude Rearview Roadmap Review
Uploaded: 2026-10-22T22:16:42.000Z
Duration: 43 min 8 s
Description: Claude Rearview Roadmap Review

Transcript for "Claude Rearview Roadmap Review": Hi, everyone. I'm really excited to talk to you guys today about our Claude rear view road map review, for the last month, everything that shipped because there is a lot to go through. Let me get my slides there. I'm Steph Soderborg. I'm... I am on product operations on the enterprise and verticals pillar. And behind the scenes with me today is my partner in success, Isaac Payne, who is on enterprise and solutions marketing. Okay. So there's gonna be three areas today that we're primarily gonna cover. One, what did we ship for your people? What can your employees do now that, they couldn't before, especially across the apps? Two, for your builders. What can your builders build now, especially within your processes and for your products? So think about this as shop... Shifts for Claude platform. And then three, what are the foundations that underlie all of it that make it safe and trustworthy for everyone to adopt, Claude across our organization? K. So one, more capable for your people. If you take anything away, it is that every day Claude is becoming more and more capable, and you should definitely give it more and more work. So first, the big launch I wanna talk about today is that chat and Cowork are becoming a unified Claude experience. So you can see basically on the left hand side here, you used to have to choose between chat and Cowork. Now it is a single entry point for both. And why this is valuable? A few things. One, you don't have to figure out. I mean, I I personally work at Anthropic, and I'd still sometimes be like, where do I start? Do I start at chat? Do I start in Cowork? work? You don't have to figure that out anymore. It's one surface. It makes it much, much seem... More seamless and easy. Two, it runs in the cloud. So this means that it can run anywhere. You can be on your desktop or web. You can move to mobile. Yesterday, literally, I was just so happy that this was the case because I was working on this deck actually at the office, and then I needed to get home. And I could go on my phone and keep working on it as I was traveling. So it runs in the cloud. And then three, it enables everyone to have agentic higher quality work. Four for admins, this is really nice because we've simplified you have one single product to govern. How do you turn this on? So, for admins today, it is not default on. And so you need to go into organizational settings. You go into capabilities. There are two things that must be on in order for you to then enable the unified chat and Cowork. One, you have to have chat on, and two, you have to have your Claude Code execution toggled on. Both of these can be found in capabilities. Then once both of those are toggled on, you can toggle on the chat and coworker unified. If you do not want to give this to everyone, you can also do role based access control for this. And so you can go into your roles, and you can decide who you wanna give access and who you don't. That will be under your organizational settings, roles, and then the capabilities for the roles. I went through this quickly because there's another, and we will socialize this as well. There is another webinar next Wednesday, specifically on this to answer all of the questions on what does it mean for my... Me and my company for Unified Claude. Another thing that we launched to go hand in hand with Unified Claude is something called efficient mode. So what this is is the ability for you to set... Switch on efficient mode. And what it will will do is anytime a GENTIC work starts, it will remove Opus as an option. So it automatically defaults to Sonnet, and you have the options of Sonnet and Haiku, but you do not have Opus as an option at all. And this is basically a guardrail that we have given all of our admins so that you can set it role by role. You technically can set this at the organizational level. I do not recommend that because then that means that you have cut off access to Opus for basically any agentic work across the entire company. But if you have certain roles where people are on chat only today and you'd wanna make sure that when they go and do agentic work that they are not defaulting to an Opus model or accessing an Opus model, you can actually go and set on efficient mode specifically for that role. Okay. Next big launch. Claude Docs, Slides, and Design. If you cannot tell, I'm currently using Claude's slides right now. So what is this? This is a new set of artifacts that... Where Claude delivers finished work for your team that you can then go in and edit. And what's really, really amazing about this is you can have one conversation, and you can have a whole set of deliverables from that one set of conversation. You can start anywhere. So you can start in your Claude desktop or web app. You can start in Claude Code, and you can also go directly to the artifacts tab where it will have, like, do you wanna start a doc, or do you wanna start slides, or design? It will give you the options. You can edit it your way. So that mean... What does this mean? There's three different ways to edit it. I can click into this like it's any other PowerPoint or Google Slides and just, like, edit it directly. I can type in it. I can add text. I can add images. I can do whatever I want. I can also click with a comment on a very specific part and then ask Claude. Talk a natural language. Hey, Claude. Like, for this one, I remember being like, can you expand the spacing between these? And it'll just automatically go into all of that for me. I can also pull up a full chat and just chat with Claude as I would normally, and it will do changes throughout your deck or your doc or your design. So this is the first one where I am actually going to walk through a... I'm not gonna call it a live demo. I will be very honest about this. I didn't want everyone to sit through ten minutes of Claude thinking and producing things for me, so I recorded my screen. And then I asked Claude to take that and just turn it into a video of pretty much exactly what I did. Okay. So I'm gonna press play here. So you can see I am asking Claude to find me all the most recent product launches from the last month in Slack and put them into a doc that I can share with our go to market team on what launched, when, why does it matter. So one, this is using a connector, which is great. It's... I don't have to go into Slack and find all these things. Claude is doing this for me. And then Claude has put it together in this, like, really excellent deck that has links to where the resources were. I could basically go share this with go to market as is. Now I wanna turn this into the deck. So I'm saying, can you turn these launches into a slide deck? I wanna present this at a customer facing webinar on recent launches titled Claude rearview mirror that you guys are sitting through right now. It's gonna ask me some clarifying questions here to make sure it does the right things. Like, who is this for? How many slides? I could also just give it more information in the chat itself. And now it's going through, and it's created me this, like, really exceptional looking deck. And as you can see, like, it's going through. Once again, it's gonna give me some, like, resources, what it left out, speaker notes are already in here. And this is... You can see a variation of, like, what I just... I'm showing you guys today. And finally, I'm like, alright. Well, I gotta go promote this on social. So can you make me some images for a social LinkedIn post to promote this webinar? It realized I didn't give it a time in a day. It's asking me what size, and then it's gonna go and, again, all in the same chat. It is going and it's creating me these really exceptional, resources that I can now download and go and use on LinkedIn. So what's really great about all of this is you can do this all in Claude. You can also download it. You can export it. So all of this is accessible where you work today. So you can create it here, and then you can get it into the systems that you're already using. What's even cooler is we keep building more of these. So we GA'd launched and GA'd our docs, slides, and design, but now we also have in public beta Claude dashboards. So what is this? Basically, you hook into all of your data sources, and in natural language, you can go and ask Claude to just build you dashboarding and resources. It basically gives everyone the power of viewing and understanding and analyzing their data without having to go ask a product analyst or an analyst or someone who knows how to write SQL. But what's even better about it is that you can click under the hood and you can see the queries and the SQL or whatever it used to pull that data in and double check and make sure it's correct. One caveat, the three I showed you before that are GA, those are default on right now. This is default off. You have to go turn this on. And I'm gonna tell you where to do that in a second. Alright. The other artifact that we launched was Claude motion. I'm sure you're noticing a lot of the images in this deck have motion and are moving. I do not have a designer that did this for me. I do not have any design skills whatsoever, actually. Literally, all I said was, hey, Claude. When you make these slides, can you also do some animated motion in here to, like, demonstrate what I'm trying to show? And it did it throughout my entire deck. That was the entire prompt. And if I didn't like it, I can, like, click on it, and I can edit it, and I can tell it to do something else. So this is super powerful because now anyone can just explain an idea in a video, and it can just, like, create something for you. So all of these, these are all called artifacts. This is where the admin side comes in. So artifacts are default on except for dashboards and motion. However, if you have custom roles, you still need to go, and and those custom roles are set to only selected, which means that, like, they do not add a new things unless you've selected them. You need to go to those custom roles and turn these things on. Also, you have role based access control on every single type of artifact. That's what you're seeing in this image. So you can say everyone has design on, but only certain people get docs, or I'm gonna turn dashboards off for everyone. Okay. Next launch. I know we're going fast here, but there is so much to get through. Claude for Google Workspace. So there's actually two different Google Workspace launches. This one is where if you actually can open up Claude inside of your Google Workspace. So if you're working on a doc, you're working on slides, you're working on a sheet, you can open up the side panel that you see here and chat to Claude. And so it basically meets you where you are working and where you are. To to turn this on, you need to have a Google super admin install it and then choose who gets access to it. Let's give this a second. There we go. On the other side, your Google connectors within Claude actually enable inline editing now. So what this means is it used to be, like, you would kind of, like, open up your Google Doc, and you would open up Claude, and you'd copy and paste things over. Now with your connectors, you can literally just open the Google Doc directly in Claude. You have the chat. You have the ability to highlight and comment all the things that you wanna be able to do in your Google Docs and just engage and edit with them directly in Claude. And those changes are live in your Google Doc. I'm using docs, but it's really like Docs, Slides, Sheets, any of those things. And so the only thing you need to do is if your Google connectors are already on, this is enabled. If you do not have Google connectors enabled for your organization, make sure that you have both Drive, enabled as well as the Google Docs sheet and slides connector. And then I'm sure most people have seen the news and the big announcements, but we have also partnered with Salesforce and then more recently Workday to have these applications operate inside of Claude. So what is so exceptional about this is if you are, say, an AE, you can now come into Claude and you can use Salesforce within Claude. You can talk to Salesforce. You can update your records. You can pull reporting. If you wanna do something for Workday, basically, you can, like, do all your Workday things, like check your time off for file expenses directly in Claude, and it is working directly with these other applications. These are both in beta, and you need to actually have your Salesforce admin or Workday admin apply for access to get these. Okay. Another set of, plugins that we have available, we launched Claude for financial services. So really what this is is we figured out eight different skills that are very specific to financial advisors, And then all of the connectors to the tools that they need to do their jobs exceptionally well, you can see a bunch of them here on the screen. And we package them into a single plugin. So that if you were a financial advisor, you now have this kind of, like, package solution that you can go and access directly through Claude. Super easy to get to this. You just go to your plugins page and you download it. Okay. I'm not gonna go through all of this because, actually, this will be provided to you afterwards. But for all of these for your people, we have a checklist. So these are all of the things that you, as an admin, should do. Okay. We're actually still in for your people, but now we're gonna talk about your coding people. So this is a big launch. It's another one I'm gonna show a demo of, code review. So code review has actually been in research preview since March. It's now generally available. What does code review mean? Basically, it is where Claude can review each of your GitHub poll requests and then comment on them and, find the bugs, leave, like, is this serious? Is this a net? Is this something that preexisted? Something to be aware of, this is never going to block or approve a poll request. You as a human still have to do that in merge, but it's going to do all the commenting and reviewing for you. And to turn this on, you just go into admin settings and Claude Code. Okay. So there is a video. Oops. I went the wrong way. I apologize. Sorry, guys. Okay. So next demo video. Alright. So you come into your admin settings. You toggle it on. You choose your repositories. For each repository, you say how often does this run, every PR, every push, how deep do I want the review to be, like something quick, something that's standard or very, very deep. And then you'll see it's actually running within your GitHub account. You can see that it's running here and it's reviewing. And then line by line on each of the areas where it has a review, it will leave comments for each one. So this is red because this is, like, something you definitely should fix. And you can click to see even more reasoning on, like, why it did this. Yellow means, like, you probably wanna fix this. Purple, it already existed, but just flagging it showing up here as well. And then you can also see all of the reviews for a single PR in one place. And then if it gets resolved in your code, it clears out itself. So it's just a way... Claude Code has enabled us to launch code exceptionally fast, and so the backlog has been their reviewing of said code. And now you can actually just review this code, much, much more seamlessly with Claude. Other things that I've launched on Claude Code. Claude Code sessions in the cloud are now generally available. So earlier, we talked about Claude, for unified Claude. This is the same thing where it's available anywhere. It runs across both your desktop, your CLI, to your phone. It's just available everywhere. So to turn this on, organizational settings, Claude Code. Mod. So this is where you can actually create a modification for your Claude Code interface. And it's basically where companies have specific things that they wanna show, along with Claude Code. So in this case, you would create a plugin, and it it will be things like, hey. Every time we write code, show the status panels and safety checks before something can actually ship. You basically get to design this and then decide if you want to deploy it into your Claude Code environment. And then auto mode. Just to call out, auto mode is default on. It's free to you. It does not cost more. If you want it, this basically means that you're not being asked every single time to review permissions. Anything that is safe or deemed, you know, not risky will just automatically be approved, but you can always disable it and turn it off. Okay. Claude Tag. Big one with Claude Tag, is that now you can have Claude Tag not only in guest channels, but also in shared Slack connect channels. And then you can also decide how much, capabilities you wanna give Claude Tag within that channel. And so you can say you can only look at the channel information. It has full access that tag would have across all of your stuff, or it inherits the workspace, controls. So you can basically choose, but the big thing here is that if you have channels with other companies, you can now both use tag in it. Also new in tag, personal connectors. So it used to be that the admin would set whatever connectors were allowed for tag, and that was it. Now if you, as a personal user of Claudetag, have connectors, you can just leverage those connectors. So it has the same... It knows that you asked the question and you have access to certain data, so now it can go and look at that data. Federated agent access is for Claudes. Basically, we now enable short lived tokens for Claude, providers so that you don't have to... It doesn't have to log in with, like, a permanent secret API key. And then Claude Tag admin. We have enabled a specific role just for you to set up a admin for Claude Tag so they don't have to be an owner anymore. So it just gives you more abilities to have someone specific in your company actually go and manage Claude Tag that is not a full owner. K. Once again, we have the checklist for Claude Code and Claude Tag. I will share this with you all. Alright. 3P. The big launch for desktop 3P, p, so on the third party applications, is that there is now an admin console available. So it used to be if you wanted to set up desktop 3P, you had to use MDM and Bootstrap, and it was just, complicated and hard... Harder to get it set up. Now you can just use the admin console. The one caveat is you still have to ask your Anthropic, representative to help you get it set up. But then once it's set up, you can manage everything through this. Also new in 3P, we are very quickly closing any of the parity gaps between our 1P product and our 3P product products. So the built in browser is now available. Claude and Chrome is now available. The admin API and analytics are now available, and unified chat and Cowork is also available. Once again, there's Checklist. Okay. So now we're gonna move on to part two. This is building a stronger platform for your builders and what's shipping in Claude platform. The big ship here is dynamic workflows have come to managed agents. So it used to be if you wanted a Claude managed agent to do something really, really complex, you had to set up all the pipelines and all of the complexity yourself. But now, we have the ability for you to have one agent that can spread a job across a thousand agents. And it just gives you the ability to run these big jobs without custom orchestration. The other thing is is you can set a budget on it so you don't wake up and find out that your, swarm of agents has accidentally spent way too much money, we give you the ability to set a limit on how much you can spend. We also have open telemetry now available for Claude platform. So, again, this used to be that you had to set it all up yourself and kind of build your own tracking. Now you can just use the OpenTelemetry that we provide. Also new for builders in the platform, computer use and browser use, are both using the SDK now. So again, like, you can use the tool kit that we've provided. You don't have to go build this yourself. You can turn off API creation... API key creation. So once again, we offer, workload identity federation. And if you wanna make sure that no one is using long term stored API keys and they're using that instead, you can just turn off the ability to create an API key now. And the CLI session viewer is basically where in your CLI, you can watch what Claude managed agents is doing in a session and steer it directly from there. So you can work within your terminal and kind of, like, monitor your your agents. Okay. We are moving on now to foundations. I think we are actually on track for timing. So enterprise foundations is basically what enables us to give enterprises the confidence and the ability to adopt all of these things that we have just talked about and we have launched. It's building all of the foundations of trust and security across the organization. So there's five kind of, like, big areas. I wanna be very clear. I am not going to be talking about everything that is available for enter his readiness. We have so much more that... Than what it is showing here. I'm also slightly biased because I manage our enterprise readiness program, so I'm very, happy with how much has shipped in the last six months. This is truly just what is new on enterprise readiness. So the five areas, security and compliance, making sure that you meet the regulatory bar, Identity and admin controls, can you actually provision access to Claude to everyone that needs it? And can you actually manage this at scale? Cost and spend management, is your spend predictable? Can you control it? And then you marry that with visibility and value. Do you actually understand what value your spend is getting you? Can you see where it is going? And then finally, connectors and reach. Can you actually bring in the data that you need to run Claude effectively? And then can we govern that in a way that is, makes it so you can actually connect all your data? K. Alright. So first big launch on enterprise foundations, is that HIPAA now covers Claude Code and Cowork. You do still need to go through your account team to get this enabled. But the... You... We've been expanding where HIPAA is available through the BAA. So as you can see, it covers Claude platform. It covers Claude and Microsoft Foundry. It covers chat. It now covers Claude Code local and Cowork local. We are working on getting it to cover this unified chat ex... And Cowork experience, and so that will also be coming soon. Compliance API. So the reason I like to touch upon this is so often I hear from customers that they do not even realize that we have a compliance API, and we have been growing the surfaces at the compliance API and the depth of the compliance API, extensively and rapidly. And so the compliance API is available across across Claude enterprise, Claude platform. It works in chat. It works in Cowork, both remote and local. It works in Claude Code. It works on the unified chat and Cowork experience with artifacts that we talked about. It works on artifacts that Claude docs. Basically, it can incorporate them as a word file. If you leave instructions for Anthropic, that is new. That is now also in the compliance API. It works for office agents. So as you can see, we have admin API across almost all of our surfaces. The big outstanding one here is Claude Code Claude sessions, which, again, will be coming at some point. So if you have any questions on is this in the compliance API, do we have compliance API, The answer is most likely, yes. We have it. Alright. Some other big security things that have launched. Inference hooks, which have been available now for, like, probably a month or two. They GA'd, this week. And along with that, we also have added in tool calls. So inference hooks are basically where you can set up all of your policies and prior to a prompt and now also a tool call, even going to Anthropic, basically, it will run against your policies and make sure that it is not in violation. And if it is, it can stop it. So these are now available across Claude, Claude Code, Cowork. We also have launched up to a 100 partner integrations for your compliance API. So this is basically where you can flow your compliance API into the tools that you already have for things like eDiscovery or DLP, and we work with over a 100 different partners for this. And then this is a minor one, but I just like to call it out just in case, any admins need to go and check something. The activity feed used to have file names in it. Now it is an ID. So there is a chance that you need to go check your SEI, a STEM, oh my gosh. I'm sorry. SIEM settings and your DLP rules because something may have changed here. You can still access the file name. It is just somewhere more secure, so you have to have the approval to use that key versus just having the file name because sometimes they have sensitive information in them. Okay. Now we're gonna move on from security and compliance and talk about some of the really amazing things that have shipped around value. So smart reports is the really big shift that what, like, has come out of the number one ask from so many of our customers, which is... I think it is great that we can see the dollars that we have spent and the surfaces that we have spent. But what we really need to see is where are we getting value out of Claude. And so what smart reports enable is by session, by team, by a set of time, You can go in and say for, like, the last fourteen days, show me everyone in the sales group and run the smart report, and it will come back and say, here are the sessions, grouped by the type of thing they were doing, percentage of sessions, how much spend went into them. So you can... They might be a little bit small here, but some of these work streams are things like, we had 14% of your sessions in this time frame based on launching a seasonal marketing campaign for a client or preparing daily briefings and call prep materials. So you can actually truly see where your spend and where your team's work is going. It will also highlight waste and friction, and it will show you the highest value work and give you the tools to scale that by, like, creating skills or seeing the workflows and encouraging them to get spread across the company. This is where I'm going to actually go show the third demo video. So this is is a recording of me going through one of the smart reports. Alright. So as you can see here, once again, we have, like, the work streams, and then you can click into all of these, and you can actually see more and more details. You can click into those further and see the sessions that make up those details. You can come in here. You can see what sort of things are actually being built, the percentage of spend or the actual amount of spend. And so you can see, like, are people building reusable stuff? Are they just answering questions? You can see where there are inefficiencies that kinda sped past that, but it might be like, hey. A lot of connectors got broken. And then you have recommendations, and you can click in. And it will say, like, here are repeatable things that you may wanna turn into a skill. Or here are some spotlights or, like, really amazing work that one individual did that you may wanna go and share across the entire organization. And then you can click into this, and it'll actually give you the skill that you might wanna build and who to talk to at your organization to confirm, like, is this the steps that we should really be taking? Is this the skill that we wanna be creating? Okay. So for admins, where do you go and turn these on? You have organizational settings under capabilities, and you can toggle on in the analytics section, smart reports. There is one other thing that is really important to know about this. You also probably want to toggle on the allow attribution to individual users. Because what this means is that when you click into those drill downs, it's actually gonna show you the names of the people who are doing these things. So if you have someone who's doing something, like, really exceptional, you may wanna go and talk to them and understand who is doing this. And so that is what the two different toggles are. Totally understand that some organizations may not want to toggle on the individual usernames, but, that is what this gives you the ability to do. The other thing that we have built is that the owner or the admin can turn smart reports on, and then you can also set up a unique role, for, like, say your department heads where they can have access to smart reports for specific groups. And so what this enables is saying, like, I wanna go and give our head of sales the ability to see smart reports for all of the different sales teams, but I don't necessarily want them to be able to go and see it for the finance teams. So we've given you the ability to set up very well scoped controls for who can actually access smart reports and which teams can they run them for. Okay. So that was all about understanding and seeing the value of the work that is happening in Claude. Now we're gonna go into some of the shifts around controlling that spend. So we've always had where you can set an org spend limit. We've had where you can set individual spend limits. And then we had where you could set what's called a group spend limit, which meant everyone in this group has the same spend limit. It was just an easy way to set really individual spend limits without having to go through every single person. So we could say everyone in sales gets a $150 as their spend limit, and it's individually applied to everyone in sales. What we heard over and over and over again is that's great, but really, I have a departmental limit. So I don't want to give everyone in sales the exact same amount. I just wanna make sure our department does not go over a certain budget. So we launched what's called pooled group budgets, and, basically, this lets you set a limit on an entire group. And so you can have... You can still have the individual spend limits, and you can have a departmental or a group spend limit. Whichever one of those gets hit first is when that user gets cut off. And so our recommendation and what we have seen a lot of our customers doing is figure out what your departmental budget is and definitely set that. And then make sure that your individual users, especially the power users that maybe are getting cut off early because they're doing that really great agentic work, which by the way, you can figure out who those are by using the smart reports that we just talked about. You can give them a higher cap because they might want to go and spend more individually than some of your less powerful users, but you're never now gonna have to worry about them blasting through the entire department budget. Because once that department budget is set, like, it's done. It's spent, and admin has to go and and increase it. So to turn these on, you go into organizational settings, usage, spend limits, and then you can set it by group or tier. And, again, you can set individual. You can set group where everyone in the group has the same individual limit, and now you can set pool, departmental or group budgets. Another thing that we launched around cost and spend management, especially on the visibility front, is where you can now see the blocked, the blocked hours and blocked seats within your organization. And so it shows you who has hit the spend limit and how many days they are losing of work within Anthropic because they are blocked by the spend limit. It will also give you a forecast of where it expects that spend limit to increase to. Like, if they stay on that trajectory, who's gonna hit their limit and when are they gonna get cut off? So it's giving you the visibility to understand, like, maybe I need to go in one... Look at the usage of these people and see if they're doing great work, agentic work that I wanna include, or I need to talk to them about, like, hey. You're gonna hit your limit. Like, we need to be smarter about how we are using Claude. So this is just giving you the visibility that you need to understand, like, who's hitting limits, and then you can also change all your limits through the spend management admin API. So you don't have to individually go in and adjust limits. You can actually set this up so that you can program programmatically manage it. Alright. What are some other controls that we have for admins that are new? You now can share projects by role. So, again, this is another role based access control. But it just gives you the ability to say, like, these groups can share with these groups. These people cannot share, giving you some more of those barriers where you need them and then unlocking the sharing capabilities across your organization when you don't need those barriers. The admin API, which I just talked about, we have an admin API for spend management. We have an admin API for user management. I'll talk about a new one. We have one for plugins. The admin API is now available in every SDK and the CLI. So it's just giving you more ways to access this admin API. And then on the spend front, we o... We already had what we call, model entitlements where you can actually set, like, what models are allowed. So, you know, certain groups can only access certain models or the org can only access certain models. That's model entitlements. We have model defaults where you can say, okay. We want this group to always start on this model, but they have access to other models. Now we have what's, you know, where it always defaults to restarting on the default. We call it a sticky default. So if I had a default set of Sonnet 5.5 and I changed it to Opus 5.5 for some agentic work, if I have sticky defaults on or start on your default on, basically, what that means is the next time I start a session, I'm going back to Sonnet 5.5. Whereas prior, it was, like, once you changed it as an individual, it just stayed changed. So we're just giving you more and more controls to say, like, how do you wanna control how your team members can access models and where it defaults to? And then finally, we launched Claude for Intune. So this is basically... If you have a company managed phone or iPad, and it's managed by Microsoft Intune, we now give you the ability to, like, actually use Claude and have app protection from Claude via Intune. Okay. So skills and plugins. This is kind of the last bucket of, launches that we're gonna talk about. And skills, plugins, ins, and connectors are really, really powerful because they're truly how you... Connectors are how you bring in all of the x, you know, external data and information and all of your other tools and systems to Claude to make it more powerful than just chat. Right? I think you guys saw in my earlier video how when I asked it to go pull all the launches, I didn't have to go find every launch post in Slack. It just used the Slack connector. The skills and plugins are also a way to, like, tell Claude how to run a specific task, or plugins kind of bundle skills and connectors together. And so we launched something, skills and plugins, where they were security scanned. And basically, anytime someone would upload a new skill or a plugin from the Internet, we would go and scan it to see if there's any malicious content. And this was, like, a really big ask from enterprises who said we wanna enable our users to add in skills and plugins. Like, these are highly valuable. We do not want them to introduce any sort of malware, or something malicious into our cloud instance, and therefore, you know, what we're doing as a company. And so we need these to be scanned. So the scanning was launched, and now it is also default on. As everything, you have the ability to go and control this. If you had selected it not to be on, it won't then automatically turn on. But if you, you know, it's... For anyone who had not made a selection, it is now default on for all of your skills and plugins as they are loaded in. And you can go double check this as an admin under your organizational settings. You go to plugins and skills, and you look at your policy. Okay. What else changed for admins on skills and plugins? So another big ask that we had over and over and over again from our enterprise, teams and customers was... I think it's great that everyone can go and publish skills, but I need to review these. So anytime someone is adding a new skill or adding a plugin, I wanna actually be able to approve this. So we have put into place a a approval flow. And so this is now the default. You can always turn it off. You know, if you're like, nah. Trust everyone. We're good. You can turn it off, but we have an approval flow for skills and plugins. This goes hand in hand with also with the ability... Again, this was a prior launch, but I'll just mention it. You also have a bunch of controls around who can actually upload skills, who cannot upload skills and plugins, who has the ability to approve. So all of this is tailorable through, your role based access controls. We also have created a single place, one inventory, where you can see all your skills and plugins that are available. In one single list, it says who added it, who is it available to, because sometimes skills and plugins are only available to certain groups. How much is it being used? And did it get scanned? And is it, like, thumbs up or good? There's no malicious content in this. So there's a single inventory where you can see all these things. The other thing I want... I like to mention around, like, all of the skills and plugins. So we talked about that you have, the ability to control who can upload them and who can add them. You have the ability to control who, like, who can actually share them. And then we also recently introduced the ability. It used to be either a skill could be shared one to one or share... Shared to the entire org. We've actually launched the ability for you to be able to just share to one group. The way I like to think about this is, like, maybe I sit in legal, and I made, like, a really exceptional legal skill or plugin, but I don't necessarily wanna share that with my, like, 5,000 person org. It's only really relevant relevant to my legal team, but I also didn't wanna individually go and share this with a 100 different lawyers. I can now just share it to the entire legal group. So it doesn't have to be for the whole org, and it doesn't have to be one to one. And then finally, we have a plugin API. This basically just allows you to manage all of your plugins programmatically. So you can upload them, you can publish them, you can version control, you can roll them back. So it's just an API to give you more and more control. Alright. This is our final checklist. It goes through all of the things that you probably wanna check out that has changed in the last month to make sure that you are up to date on all of the things that you need to do. Where to learn more? So there are two big events that are coming up. Next week, I highly, highly, highly encourage everyone to go join Unified Claude for Admins webinar. Because I ensure, as I, like, talked about this, all of you have hundreds of questions specifically around this really amazing change that is coming, but it is still a change. Please go to the admin webinar. You will learn a ton there. Then we are also having a knowledge work briefing, November 10. And this is gonna be focused all around all of those amazing things we've been launching, for, like, artifacts and docs, and there's just a lot more that's coming. And it's basically highlighting and showcasing the future of work of, like, how we meet you where you already are within your Google and your Microsoft systems, but also how Claude is continuing to grow and give more and more agent... Agentic capabilities and the ability to produce more work. So if you are interested, I highly encourage you to check that out as well. And with that, I managed to do this with two and a half minutes left in our session. So I don't know how many questions I am going to be able to get to. But thank you all. The other big thing I will say, this was the first time we did this webinar. We are going to do it every month. So keep your eyes out. I'm being told I've been assigned some questions. I don't even know how to begin to look at those. So we'll see if I can figure that out. That said, come next month. Maybe I'll answer your questions from this month there because I don't know how to use Goldcast, and I cannot figure out where the questions are. But I really appreciated everyone showing up. I hope this was informative, and please come back next month because as you can see, there will be plenty plenty of things that we have shipped in the next thirty days.