Transcript
Yeah, let's do it. Yeah, self-serve. The goal of this is we wanna reduce the amount of tickets that you have to manage saying, can you please install this on my machine? Can you please help me do this with my machine? By consolidating some of that into this self-serve hub. So the way that this works is I'm going to make some software available to users in my environment, come here, pick a piece of software. Again, to start off, this is a list of software that we're curating. As we get this a little bit more developed, you'll be able to bring your own packages into this list of software. So if we pick something like DBeaver for my engineers, then the next step for me once I pick that software is I get to assign it to the right people. So I don't know if I have a group in here for engineers specifically. So I'll just say all devices. And so all devices will have this software in their self-serve hub on their device. They can go in, click the button, and it will deploy the package for them. So what does that workflow look like for the users? Are they going to a web address that's specific to your org? So it's going to be an application that lives on their machine. Like you can think of it similar to- Like a managed software center. Yeah, like a managed software center. There will be some flexibility around exactly how users interact with it, whether it's coming from system tray or something they can open from a start menu or other like desktop shortcut, and then the equivalents that we have on the Mac side as well. Let's show the setup screen. I think that everyone's really curious about how that will- Yeah, what is it going to look like? So here's the easiest way for me to demo that right now with what we have in this environment. We're missing Josh today, so we had to have him represented somehow. This sort of gives you two things. It first gives you a little bit of a preview of what the self-serve hub will look like on your end users' devices as far as on the left, you've got options for your software, your actions. You have this bar across the top, and this is where you can put in your customization rather than Josh's face or IT team's face, probably company logo or something like that. No, I definitely recommend sticking with Josh's face. We'll make this image the default for everybody. But yeah, something, oh, it's not typing. There we go. Something like company name here. And then we've gone and we can thank some of our design team for this, curated a few nice looking color schemes that you can pick from. You can preview these both in light mode and dark mode. It should just go based on whatever the system preferences your user has. And if you don't like any of those, you can pick your own colors for the header of the button. The engineer who demoed this previously picked some really fun colors and I've just left them in there because I get so much joy out of this pink and brown combination. Anyway, this is what it's gonna look like for end users. You've got software and actions. So question about actions, what is that? How does it differ from software? This is where you can actually come in and pick any custom package that you have prepared. So it could be a custom package that installs software if that's what you want it to do. Some of the customers that we've talked to have mentioned like it'd be nice to have a package to install a printer or do some sort of disk cleanup. I was about to say some, yeah, disk management. Yeah. Cleaning up temp files, things like that. Exactly. So it's sort of the world is at your fingertips. You can put whatever you want in there. If it's something that you can deploy from Connect, you can make it available to your end users to deploy as well. There was a question about how do you limit who gets what software in their self-serve portal? So that is fully configurable. That is done by groups. And so for a specific piece of software, you can say this software in our example a moment ago, one password is available to computers in these groups, but maybe not in these other ones. So if you have like in Michael's example, some software that's really only for engineering, you don't need the rest of the company to see that in self-serve, you absolutely can restrict it in that way. And that targeting of software or packages to individual groups is done per software. So you don't need to create multiple templates or profiles of a self-serve hub and then pick which one of that group of software goes to some group of computers. It's just each one of these will target dynamically whichever devices end up in the groups that you put here. Okay, great question about can the groups be tied to AD groups? The answer is yes. And I think that there's probably a little bit more that we can do there. First thing is, I don't know if we have a good demo for it here, but we do have an integration with Active Directory where you can pull in some groups and to connect and use that data to target AD groups. What a lot of people are interested in though is that the groups be user-based. Today, the groups that we pull through the integration are computer-based. We don't yet have user-based groups in that. And that has been some pretty common feedback we've received from customers as we've demonstrated this feature. And so we're talking with the engineering team right now about expanding that integration so we can pull in user groups as well and then ultimately make this feature more targeted at the people that you wanna get software access to. I saw a question about multi-tenancy. So the way this works is each tenant has its own self-serve area. So you can configure the tenant, the self-serve by tenant but there isn't a primary where you, or you manage it just purely from the top level. I think people are gonna love this feature. I think, like I said, this is one of those that people have been asking for for a long time. They wanna avoid the phone calls, they wanna avoid the tickets. Like, great, just go install it yourself. Well, we've had customers do it, but it's required, like we're using the API or on-deploying inventory, even getting more creative with how you do it. Yeah, I saw someone on Reddit where someone was like, oh yeah, I'm gonna do this with the API. I'm gonna build out the self-service hub. And I was like, you might wanna wait just a little bit. Yeah, yeah. Maybe save yourself some time. What's nice about this is you don't have to worry about user authentication like this because it's accessed on the device. So you access it through the system tray or through another means there. And so there's not like a separate username and password to log into the self-serve portal. It's right there on everyone's computer. Really easy to click. And as an IT person, you don't have to do a lot of custom coding to make this thing work. You just configure it just like we did. There's really no coding needed at all. Right, yep. I'm seeing some questions about when. Just a couple comments about that with regard to both policies and self-serve hub. These are both like the primary focuses for their respective engineering teams right now. And we're getting pretty close to ready for early access for both of these. Not sure on the exact dates, but we're talking about a matter of weeks in both cases. Awesome, that's soon. Yeah. Yeah, I love it when we're showing stuff off because unlike movie trailers, where you're like watching, they're like, hey, coming 2028. And you're like, what? Why are you even showing me the trailers? Like, no, we show you something and it's coming out in like a few weeks. Yeah, this is all real code. None of this was like fake or screenshots. This is all like legit product. Thanks for watching this segment from PDQ Live. If you like this, you'll love the full show. Check it out every Thursday at 10 a.m. Mountain. Oh, and like and subscribe, please.
