Oktane18: How Does the Okta Integration Network Let Me Do More with Okta?

Speaker 1: I'd like to welcome our fabulous presenters today. We have Chuck Fontana, VP of Integration and Strategic Partnerships, David Nissen, Director of Product Management for the Okta Integration Network, and Maggie Law, Director of Product Design at Okta. Thank you. 

Chuck Fontana: Thank you. Good morning. Hi everybody. Delighted to see you all. I'm Chuck Fontana, as she mentioned. I lead Okta Integration and Strategic Partnerships. I've been at Okta about six years now. I really came aboard to lead the overall Partner Program and the ecosystem. Success for today is really to share with you where we're going in the context of the OIN, the Okta Integration Network. So we want to make sure that, from a business development perspective, and how I manage the partner ecosystem, and some of you are here from that. Thank you for being here. 

Also with our product organization, how we're delivering new experiences in the OIN, which we think will unlock a tremendous amount of value for all of you. For those of you, hopefully all of you attended Todd's keynote, there's a phenomenal amount of things that were announced. If you think about what the keynote was about, the keynote was about the Okta Integration Network. It was about the integrations, because integrations, at its core, are what Okta is about. Securely connecting people to all their applications, all their constituents, and all their devices, across the network.

So today we're gonna go through, as reflected in the disclaimer, some more forward-looking things, where we're going, what's the strategy behind the OIN? From a product perspective, David and Maggie will take you through the capabilities and things you're gonna be able to do. 

This is us. Perhaps we'll continue on the way. So we announced the OIN back at Oktane 17, right? That was really the realization that as Okta had built out and connecting our customers to the cloud, that these one-to-one integrations that were around single sign-on and provisioning, that in fact we've actually listening to our customers, and listening to our partners, we started really connecting in to things that were really more than just applications.

We were connecting in to the very fabric and fiber of what our customers needed us to connect to. Into back-end systems and network firewalls. Security incident response systems, things of that nature. So a lot of times, one of the challenges that we have, and hopefully- how many of you are existing Okta customers in the audience? Show of hands? Okay, a lot of them.

A lot of people perceive Okta from how they use it, or how they actually see it if you're an end-user. Right, so a lot of people think of Okta as a catalog of apps. A lot of times, we're our own worst enemy, talking about 5,000 applications in the Okta catalog. It's really more than that, so Okta is more than single sign-on and provisioning. In fact, when we think about it, it's like saying Google does search, or Amazon sells books. Really Okta at its core is about secure connections into everything, and the partnership between ourselves and the partner organization, and the product organization, is figuring out use cases that are from you. 

Things that you want us to connect to, things that you need us to enable and transform your businesses. So yes, it is all these things. It is is a catalog of applications. But really the OIN is really how we're delivering transformative employee experiences, right? How we tie into HR systems, other systems that are directed to make the life cycle of an employee a seamless experience, connecting them to their apps, connecting them through their ITSM systems. 

Really through our partnerships that we have with HR systems like Workday, Namely, SuccessFactors and others, even RingCentral, is a directory that which we're able to deliver phone numbers, mobile numbers and things like that, to make the employee experience connected into everything. 

The OIN is how our customers are securing the business. It's how we hook into security incident response systems, SEC ops, SEC analytics type of products. Through partnerships which we're continuing expand upon with Rapid7, ServiceNow, these are the things that again Okta is trying to deliver more value, by delivering identity context into the systems that you're using. 

So not everybody is driving everything from the Okta dashboard. Their security teams are sitting there in Sumo Logic, they're sitting in the ServiceNow systems, and if we do what we do well, and what we do best, is we're gonna provide identity context into all those things. 

The OIN, of course, is how we're hoping to get you closer to your customers. Through the work we do with API proxies, through the work we do with delivering secure API elements to our developers, and delivering developer-centric tools and systems, or even to in fact make you closer to your customer, such that it's a more secure connection. 

When we look across all of our customers, wherever you're a big enterprise customer, to a smaller customer perhaps, smaller enterprise, these are really tangible benefits we've shown, and we're able to measure that what we're able to look to deliver in the context of higher employee productivity. A more secure company, and it's really about removing friction in how we enable our employees, and because as a customer even Okta, we're more than just a bunch of employees. It's how close we are to our partners, it's how close we are to our supply chain, our workplace teams. Every enterprise is more than just themselves. 

I think if we continue to do that, that's what in effect will make Okta a success. So at its core, yes of course, Okta is a catalog of single sign-in and lifecycle management provisioning type integrations. But the things that we'll be sharing with you today, through the extensibility investments and the APIs we're building out, we have now built a more comprehensive ecosystem of advanced integrations, that tie in again to the very fabric of how you modernize I.T., how you're gonna drive your business. How you're gonna take your company to the cloud. 

If you look from just network security, we have the ability to deliver two-factor authentication and to net security parallel to firewalls. To hook into CISCO VPNs. To partner up and deliver governance with partners like SalePoint, for instance, delivering the best of breed of governance with identity. 

If you look at what we deliver again around identity context into security systems, that's a very compelling means for which Okta can provide you just value from what we do. And again, that's really at the I.T. products level, what we're really well-known for, but where we're going, and from building out the ecosystem, the thing I'm very excited about, is you look at our API products. Our API products are what we're delivering around systems for developers. Giving them more secure capabilities and more identity context, and identity systems for their gateways, for proxies, and again with partners like Acuant and others, we're delivering identity-proofing for when you're building portals, right? 

So, the the thing that we want you really to take away here here is this. Okta's more than a catalog of apps. We're building with your feedback. We are building with you, on customer-driven use cases, we're building something that's actually far broader. We are actually building- oops, sorry. We are building things that are gonna actually deliver to you the ability to do more.

With Okta's partnerships, all the partners you saw at today's session with Todd, those are all in fact things that we're not done with. Those are things we continue, through your use-cases we'll continue to build out. What I'm excited to show you next is really to have David Nissen from our Product team tell you how we're manifesting those integrations, and delivering them to you so you can do more with Okta. 

With that, let me introduce you, in fact I would be very pleased to introduce, David Nissen

David Nissen: Thanks Chuck. Am I on? Yep. So, I'd like to talk to you a little bit more about some of the investments that we've made since the last Oktane for the Okta Integration Network, and you'll hear these terms a lot. Neutral, best in class, best of breed, and that one of the big differentiators for Okta. We think it's a strategic advantage that we're a dedicated identity company. If you think back about some of the legacy identity products, a lot of them were built around on-premise applications, where someone delivered first one on-prem application, and then they built out a suite of on-premise applications, and they realized that they needed to provide a single set of credentials to log in to all those on-prem apps.

But they build those products as a lever to try and sell you the other applications that they were building, and you see that also today in some of the newer identity players. They're building an identity product not because the identity product is core to their business, but as a lever to sell you the other products that they build.

That's not what Okta does. We're neutral, we don't care what applications you choose to use, apart from obviously choosing Okta. We want you to be able to go out and look in any category, and pick the best of breed application in that category, and pick the application that's best going to deliver the use-case that you need it to deliver. 

So I have a couple examples here of areas where we've been investing. These are two great products, way up at the top of the list of the most-used applications by the Okta customer base, and we build best of breed integrations to both of these products, and we're constantly investing into those integrations. 

So I wanted to get up here and talk you through the list of features that we're implementing, I got shut down, the team told me, "No, no one wants to hear you drone on about individual features." So just at a high level, what I wanted to explain here is we're investing in all of these integrations, so we're neutral. If you want to use Office 365, use Office 365, and we will build you the best possible integration between your identity platform and Office 365, and similarly for G Suite, and we're continuously investing, continuously iterating on those integrations to make sure that we're integrating the features that Okta's building into the platform and leveraging those, and also leveraging the features that our partners are building so that those integrations evolve over time.

But it's not just Office 365 and G Suite. We're investing, we have a big engineering team investing in building out integrations to all of these applications and more. Another area where we're investing heavily is around mastering, and so this is both user mastering and attribute mastering. You can think about this as most companies started with their identity, their users starting from Active Directory, and using Active Directory as the source of truth for users. Over time, we're seeing that evolve to being moving towards using the HR system as the system of record. If you use any of these five HR systems here, we have an out-of-the-box integration to Okta, meaning that Okta can reach into that HR system and pull out the attributes that you want, pull the user data out, bring it into Okta, and then provision it out to all the applications that you use. 

But we're also doing attribute mastering, so you can take an attribute, let's say telephone number for example. When you create a user in Success Factors, typically you don't already have a telephone number, because often a telephone number is created by one of the other applications that you haven't yet provisioned the user into. So to think of this end-to-end flow, create a user in Success Factors, Okta reaches into Success Factors, grabs that user, creates them into Okta, pushes that data out to all the other applications, including out to Active Directory if you still have apps that are reliant on AD, but then provisions that user into RingCentral and RingCentral creates the telephone number.

But now you want that telephone number back into Okta, back into Success Factors, and then out to all your other applications that require telephone numbers as part of their user attributes. This is the kind of end-to-end flow that we're investing in building out. Again, neutral and best in class, so we don't care what HR system you use, and we want to provision out to all of the applications that you're using as well. 

So again, here's a list of features that I'm not allowed to talk about in any detail, but big investments here, so this is just since the Oktane, so our last Oktane was seven or eight months ago. Big investments in Work Day, adding new features in Work Day. Success Factors recently went GA, so this was an early-access integration at the previous Oktane, now general availability. More features supported there. 

And we're really excited about the Okta and Namely integration. Namely is an up-and-comer in the HR system market, and one of the interesting things about this integration is it as actually built by Namely. Okta didn't build this integration, Namely recognized the value of being part of the Okta Integration Network, and they built the integration and they own the integration. 

One of the reasons why we invest so heavily in the OIN is about time-to-value. We could deliver you a platform where you could do custom integrations and you could spend weeks or months integrating to any particular application, but we want you to get up and running fast. It's one of the messages you'll hear both from Okta, but also from our customers. Is that it's fast to deploy Okta and it's fast to start seeing the value of using Okta. And part of that is this broad suite of integrations that we have so that in minutes you can be up and running and federated with an application. Be using SSO, be provisioning users, doing integrations that previously may have taken you weeks or at least ... sorry, at least weeks or potentially months.

And so you'll hear these numbers, we often talk about there's five and a half thousand applications in the integration network. But it's not just about the number of integrations. It's that we're always interested in getting both breadth, so adding more integrations, but also depth. How do we take the integrations that we have and go deeper with those integrations? How do we deliver more to make sure that we can deliver the use case that you're looking for when you're integrating with the applications that you use?

And so, Chuck mentioned lots of applications here where we've gone beyond just single sign-on and provisioning, and looking to open up new use cases. We're also looking to open up new categories. So, as a great example of that, since the previous Oktane, we've been looking at our VPN integrations and for a long time we've had a generic radius integration. So if you had a VPN that supported radius, you could use that together with Okta and with some time and effort, you could go in and you could figure out how to configure Okta, how to configure your VPN, and you could make that integration work. 

But that's not delivering the time to value that is one of the key values that we want to deliver to you. So, since the previous Oktane, we've gone and built a whole bunch of out of the box integrations to VPN applications. And you can see some examples of those here.

So what does that mean? It means if you're using any of these VPNs, you can go and search for that application in the Okta integration network in the catalog. You can click a button, you can get the app set up. You can get easy configuration. So anything that is automatically defaulted will already be defaulted, and then you get a really clear configuration guide that guides you through the steps not just to configure Okta but how to configure your VPN.

So again, taking this project from something that might have taken you a week with the generic radius application to go and dig through the documentation from the VPN partner and figure out how to configure it, turn that around and make this an integration that you can have up and running in minutes. And again, we're delivering not just SSO here but also MFA for all of these VPN integrations. So easy integration and an increase in your security.

We also want to help you develop new services. So we built out integrations with API gateway providers like Apigee and Mulesoft. And we want to help you, if you're building a B to B or a B to C portal, we want Okta to help you to speed time to value. So how can we make it easier for you to get up and running quickly? How can you use your identity from Okta to secure your APIs? And then there's big cost saving. So Okta will help you to do that faster and save money and get time to value faster. But once you've built your B to B or B to C portal, how do we help you to actually deploy that?

And most of you are probably using one or more of these services. So once you've built you're B to B portal, you want to take that and deploy it to the cloud. And we've invested a lot over the last seven or eight months, particularly in our AWS integration. So we've taken our AWS integration and made it scale. So the previous integration had some limitations around the number of accounts that we supported. So that limitation is gone. You can use as many AWS accounts as you want. 

And the other change that we made for that AWS integration is we've made it seamless to configure a group in active directory and have that group map all the way through to roles in AWS. So you have a seamless end-to-end process for managing identity and access from AD through to AWS.

We also released support for AWS red shift since the previous Oktane, and we're working on a revision of our AWS CLI tool. So you should be expecting to see that. Over the next six to nine months we'll release a new version. We have a current version, but we're building a new, improved version of that AWS CLI integration.

One of the other things we've heard from talking to customers is that a lot of customers use more than one of these. In fact, a lot of customers use all three of these different platforms depending on the different use case that you're trying to deliver. 

Something else we're going to be looking at investing in later in the year is how do we make that then seamless for you to take a single identity from Okta and to manage that across all three of the cloud platforms? So again, just to make it easier for you to manage the infrastructure that you're using to deploy your applications on.

You'll also hear this a lot. So, network effect. We really want to drive the catalog to grow in both breadth and depth. And we know that we can't build all of the integrations. There's tens of thousands of applications out there, and Okta's always investing and building best of breed applications. But to really get reach out across that ecosystem, we need to bring people on board. We need to get other developers building the integrations on top of the platform. And in order to do that, we need to be flexible. We need to build tools and processes to make it easy for third parties to come on board and build on top of Okta to help us grow the network.

So we built out what we call the ISV portal. If you're a third party software application vendor and you build an application, we give you the tools, the processes to come and build an integration to Okta. It's largely self service. There's a team of support to help you there, help you guide, help guide you through the process. But largely now you can build your own integration between your application for both single sign on and provisioning to Okta. And you can see it's really gotten traction. So in particular since the previous Oktane, we've really started to see this build up. And you can see that some of the names on the right there, names of companies that you know that recognize the value of being part of the Okta integration network and have built their own integrations.

There's some numbers here. So, 20 new SAML applications a month, six new SCIM apps a month, 130 total provisioning integrations, and about 53 percent, so more than half of them ... More than half of the provisioning integrations are built by the ISVs themselves. 

And I sent this slide to our legal team to review, and they sent it back, and they said, "Your numbers look fine." But they said these numbers look a little small. They're not very impressive. 

And so before I came here, I went and looked at some of the competition. And I looked at one of our biggest competitors in the identity market. And they had 25 documented provisioning integrations. So we're at 130. We're adding six a month, and six a month built by ISVs who are recognizing the value of being part of the network. We expect that number to go up. We're targeting to get at least 200 provisioning integrations by the end of the year. And that's just provisioning integrations built by Okta and by the ISV partners. 

We also have another plan for how to grow that number significantly, and I'll come to that in a minute. One of the other key points on this slide is that customers are actually starting to say that they won't buy an application unless it's in the Okta Integration Network. And we encourage you to tell your vendors that. So if you are an Okta customer, and you're looking to go and buy an new application, and it's not already pre integrated with Okta, you don't want to build that yourself. You want to tell your vendor that Okta has a self service portal that they can go, as long as they support one of the standards, they can go and build that integration themselves. It's a quick and easy process, and it leverages all the tools that are there to get them quickly onto the integration network to help you as a customer. But also for them, it adds value for them. It puts their application in front of all of Okta's customers by putting it into the catalog. 

So I mentioned we want to grow the integrations, and in particular the provisioning integrations. So I'm really happy to announce today we have our first systems integrator built integrations published into the catalog. In the past, they'd all been either Okta built or built by the ISV themselves. But today we welcome Aquera into the catalog. They're a systems integrator. I was talking to jerry yesterday about their integrations, and he made me note that they're not a build and run systems integrator. They're going to build integrations and own them and manage them. And they're publishing them into the catalog. And they have about a hundred integrations already built. 

And they're building two cloud applications, but where they're particularly interesting to me is that they're building a lot of integrations to Legacy on premise applications. So you can see some examples here. They have connectors built to Oracle on-prem SAP, Symantec, IBM AS400. So if you have your Okta best of breed cloud native identity service provider, and you need to connect it to your 1990s AS400 Legacy infrastructure, which is ... You should use identity seamlessly across your entire ecosystem. And so Aquera is helping by bringing more and more of those Legacy products, bringing integrations for them into the catalog. 

And then finally, if all fails, if you don't have an app in the catalog, what we're looking at here is an extension of our application wizard. In the past, you could go and build a SAML integration yourself. If you had a SAML application, whether from a third party or an application that you had built yourself, as long as it supported SAML, you could go into Okta and you can use the application wizard to integrate for single sign-on. 

Just this month, we're launching a beta to add support for SCIM to that application wizard. So if you do user provisioning ... If you've built an app yourself or you have a third party application, as long as you have SCIM, you can go into Okta and easily configure an application to do provisioning. 

So I've talked to you about a whole bunch of the different features that we've been investing in, and we really are investing in that. My engineering team, I think, has grown more than any other Okta engineering team because we recognize the value of growing the integration network. 

But one of the things that we haven't done a really great job of in the past is getting this information out to you. So how do we make sure that, if you looked at one of our integrations 12 months ago, and you decided that it didn't quite support your use case, well, those integrations are moving on. In the last 12 months, we've added tons of features to tons of our integrations. And so maybe we support your use case today. But we haven't done a great job of presenting that information to you. How do we let you know about all the great work that we're doing? 

So with that, I'd like to invite Maggie [Law 00:25:03]. Maggie's going to talk to you about some of the changes that we're making around the user interface and how do we deliver that information and make it easy for you to find things. 

Maggie: Thanks, Tom. 

Hi. I'm Maggie Law. I'm director of product design at Okta. And I'm going to go off demo here. I think I can just ... No, I can't do that. My demo is actually in Chrome. Because what I'm going to show you is ... Think of this as a concept car. David just mentioned, we have a lot of ideas that we're thinking about. Future thinking, you saw the disclaimer at the beginning. So I want to make sure everyone knows that what I'm going to show you is a window into a bunch of ideas that we're really excited about that paint a picture for how we're thinking about the evolution of the OAN. But please don't look at this and think, "This is going to get delivered by X, Y, Z date," because it may or may not. It's just ideas. In the meantime, we're excited to hear feedback from you all and from other customers, so please take a look. If you wanna leave me a card or something at the end or visit the design booth at the Expo, in the Expo Hall, and have your bag scanned, we'd love to work with you on evolving these ideas.

For those of you who don't know, you're looking at the IT app. A familiar place to go here is the applications page. This is actually a re-designed version of what's there today. We're sort of evolving a lot of existing stuff, but the idea is that these are the integrations that we have already configured for our company.

David just mentioned that one of the things that might be challenging today is knowing of these integrations that you've configured in the past. They're working. You sort of set it and forget it, but you don't know, necessarily, that they're evolving. There's new functionality coming that's getting built into it that could actually add a great deal of value for your company. You just don't know it's there.

One idea we're thinking about is for there to be a way to indicate that there are updates. Over the course of time, you can filter this list and see, "Hey, look at this. This is now available for this integration," or, "Hey, they've added provisioning and that could be really valuable for us and our company." 

Sure, you wouldn't necessarily know that unless you actively go and look at that, but we want to highlight that because we want you to take most advantage of what Okta has to deliver.

Now I'm going to dive into the OIN itself. As I mentioned, this is your applications, your integrations, what you've already configure. Add an integration takes you into the Okta Integration Network catalog. 

Calling it a catalog is actually, I think, a little bit more accurate when you think about .. There are a ton of offerings in here, a ton of integrations. I can look at them in terms of perhaps by categories by default, what are the ones that have most recently been updated by the vendor. That could be useful. We could leverage businesses at work data. This is something that Okta uniquely offers to be able to show trends among all of Okta's customers. 

For right now, I'm going to talk you through a use case. Let's say, for example, I'd like to come in here. I'd like to see what in the catalog is available by Google, just as one example, so I can just see everything that's in here. The one thing that I want to point out is just that Google may or not be in the name of the integration, but it's the vendor for all of them. Different types of metadata associated with integrations could be interesting to search against, so we're looking into how can we connect you more quickly. It could be attributes ... any sort of thing that could be useful to you in a search.

Right now, really, actually, what I'm specifically looking for in this case is Box. I'd like to pursue this. I click on that, and now where am I? I've actually navigated to a landing page that tells me more about this specific integration. It's a detailed page inside this catalog. It gives you some information that we think might be useful. For example, who built the integration? When was it last updated? More interestingly, what is the functionality that it currently supports?

If you're specifically wanting to confirm what's already in there and if I configure this integration today and six months down the road, they add something new, then I showed you where we are. I could see that quickly through filtering.

Okay, now I'm going to go back and I'm going to show you a different integration. Of course, you've heard a lot about breadth as well as depth. This is an integration that doesn't just have an add button, because there's no add app wizard. This is actually an advanced integration that requires a different path. We think that this detail page, this landing page, can be useful to you just as a way to bring together into one convenient location all of the various guides and tools that you need in order to do this integration.

Today, rather than hunt it down in various locations, what we'd like to be able to do is let you just click and see. You can open up. Here is that integration in Splunk base. Here's the configuration guide. Here is where I would get my token from the Okta developer page, but just make it a lot more convenient for you so that you don't have to hunt things down.

That is what I wanted to show you all. Just a quick recap of what I showed you ... First, I showed you that you can highlight what integration additions, what updates there have been in case that new update is useful to you in your company so you don't miss it and you don't miss out on the value. A redesigned catalog ... You saw it's a card UI which looks a little bit more modern and more like an actual catalog, and a metadata search so that you can search on not just one or two attributes, but lots of different attributes that might be useful to you, and landing pages for those integrations so you can learn not only what the integration does. You probably already know, but just to be sure. You can see, more importantly, how this integration ... what features this integration supports.

With that, I'm going to pass it back over to Chuck to take us to the finish line.

Chuck Fontana: Thank you. That's pretty fabulous stuff, huh? Pretty cool. I think the key takeaways here, folks, is really this, is that the OIN we talk about is really again more than just a catalog of applications. It is integrations into the fabric of how you're going to secure your company, how you're going to enable your employees, how you're going to grow your business. 

A lot of times, when people talk about the OIN, is its Okta's competitive mode. It's not. It's really yours. It's your competitive differentiator. When you buy Okta, when you invest in Okta, we'll be able to provide the network effect into all your systems. The things that we built this ... We didn't build this on science experiments. We built it by getting close with our partners and close with our customers, who told us, "Hey, I need the ability to do these things."

Okta's entire journey has always been really about trying to deliver and connect, securely connect, you to your employees to your supply chain to your partners to your end customers, and to connect them into everything and to everything.

Really, this is your OIN. I really mean that sincerely. Our team will continue to work in concert between our partners and product to continue to incubate new use cases, so if you have them here, please come see us. Talk to anybody at Okta. That's what we are here about ... making you successful. We'll incubate it. We'll integrate it and as importantly we'll enable you, as Maggie showed you ... We'll enable you to extract that value to help you accelerate and differentiate.

This is about coming forward. We want you to hear, not just from us, but you want to hear it from our customers and our other partners about they're leveraging the OIN. How does a partner take the OIN and differentiate their customers ... how his customers are, in fact, leveraging these things.

These are some of the sessions coming up later today. I encourage and ask you all to attend them. I think they're really good ... Hear from that the stories of what they've done, what results they've gotten. That continues on through Thursday. These are all really some very phenomenal presentations. You're going to really love to hear about how you might get the wheels turning or how you might leverage Okta.

Whether you're a partner or a developer or whether you're a company that's building applications internally or externally, also this ... and leave you with this, is that Okta is relational, not transactional. Yes, you may be a customer, but we want a relationship with you that tells us where you want us to go. We'll always be there to listen and iterate. That's really at the core of what we're going to do.

To that point, please visit the OIN page. You're going to see on the OIN page, as David noted, and Maggie noted, we are committed now not to just create integrations and hope somebody finds them. We're actually creating more standard ... We call bills of materials, standard configuration guides, deployment guides, give you core messaging ... What is the application so you can find it? Eventually, as Maggie noted, we will get that into the catalog so that stuff is more readily available in your hands.

With that, what I would leave you is this. Again, the OIN, as Todd showed today, is continuing to evolve. We saw some great new capabilities. Sign on with Okta. We're Onramp with Okta. These are all things that deliver not just value to the ISVs ... more importantly, value to use end customers.

With that, I'd like to open it up for questions for myself, David and Maggie. Happy to take any questions you may have. Deafening silence. Okay. I'll tell you what. We are certainly here after this presentation to talk at any time. Please do fill out the surveys, if you will, because that is important to Okta. Then we want to continue to iterate. We want you to win this gift card. It'll be a good time. So just check the boxes, if you will, and hand them off to some of the folks at the door. I would encourage you to come see us. We'd love to talk throughout the show what we've been hearing to find out more about what you want from us, okay? Thank you.