Quarterly Product Updates: Q3 2023 Highlights

Before you log off, we’d love for you to take a quick survey just to tell us how we’re doing and if you have any feedback for us. It’s important for us to know for the future, so please take a look at that. Now, I’m Dana, a Product Marketing Manager here at Atera—nice to meet all of you. I’m here with Yasmin, who is the RMM Product Manager, and Yakov, or Yaki, who is the PSA Product Manager. They will be demoing some of the new and exciting features, which we will go through quickly right now. 

We’re going to be talking about a bunch of things today, maybe not necessarily in this order, so don’t get too attached to the order. We’ll talk about some sneak peeks of our AI co-pilot, things that are hopefully going to be rolled out very soon. We’ll talk about the new MSP ticket page that’s gradually being rolled out—some of you might already have this in your environment, some of you might not, but if you don’t, you will have it shortly. Yaki is also going to show us a sneak peek of ticket forms, which will be really exciting. Then, we’re going to hand the mic over to Yasmin, who will be talking a little bit about the private software repository, which will hopefully be coming out very soon, as well as some updates for Linux, including manual and automatic patching. We’re also going to talk about the new devices page, which is already out. Yasmin will show a quick sneak peek of the advanced filters that we’re going to be adding. If you haven’t had a chance to play around with the new devices page, I know some people were waiting for this specifically, so that’s super exciting that that’s coming up. Then, we’ll talk a little bit about scheduling shutdown actions, which has recently been released, as well as silent installation and uninstall prevention. Let’s go ahead and jump right in. Yaki, do you want to take it? 

Yaki: Absolutely, thank you, Dana, for the introduction. I’m excited to be here and share all these things we’ve worked on and are working on. I’ll apologize upfront—my computer is acting up, so I might try to turn off my camera at some point if things get slow. But let’s jump into it. I’m going to share my screen if I manage to. I’m actually not able to. Dana, are you still sharing the slides? There you go, perfect. Let’s see if it works. Looks like it is acting up a little, so maybe we can start with Yasmin and then go back to me. Yasmin, you ready? 

Yasmin: Yep, hi everyone. I’m very happy to be here and share some of our really cool features. So, sharing my screen coming up. Cool. I’m going to start by showing you about our private software repository. I also just mentioned that I’m sharing on our Dev environment, so things may look a little bit different from what you know. Don’t be alarmed—these are things that we’re working on but are not being rolled out just yet. 

Hopping over to software management, which is the current software bundle page, you’ll see we’ve added the new option for software repository. We’ve heard from many users that there’s a need to deploy some custom software that’s not necessarily part of the public repository that we offer with Chocolatey for Windows and Homebrew for Mac. So, we’ve integrated a repository and the ability to distribute custom software packages through Atera. This feature is currently out for beta testers only, which is why you might not be seeing it yet. We’ve started off by allowing you to bring your own repo. We currently support three different repository types: Azure DevOps, MGET, and JFrog. All you need to do, if you’re not currently managing a repository, is a one-time setup on one of the three options I mentioned, integrate it into Atera, and then all the management from that moment on can be done from within Atera. If I hop over here to manage repository, I’m already connected. I’ve got a repository set up in Azure. If you’re a Microsoft partner and you’re using Azure already, then it’s very easy to create a project and set up a new repository. You name it whatever you want, enter the source URL, put in your username, and generate a token. We have a knowledge base article that explains exactly how to do everything. But as I mentioned, it’s currently only open for beta testers. You can check out the KB and have a sneak peek and read how to do that. I’ve integrated here—it’s a one-time thing. If you have any packages that exist already in the repository, they will be synced and show up within Atera here. You can also upload software directly. Clicking upload takes me to this upload wizard. I can select an MSI or executable up to one and a half gigabytes, or based on the repository limits. You can add any parameters to the package—they will be packaged to that file so every installation will run these parameters. For example, if you want a silent installation or any other keys that you want to enter, name it, put in the version and the author if you like. You can also upload a logo or enter a URL and a description. We also offer another option to pull the software directly from a URL. This could be good if you have a custom installer that may be updated or have newer versions come out, like we have for the Atera agent. When you go to install the Atera agent, you can copy a URL that you share with your customers. You can enter any URL here, and it will pull the package in real-time when you install it on a device. This is a great option if you don’t want to manually upload packages and just have it download the most recent one when you install it. So, it’s the same process here—you upload, and then it will show up on the list here. If you want to install these packages, they’ll be supported everywhere in Atera where you can currently deploy software. I’ll show you some examples. I’m going to go to one of my devices. This is currently only supported for Windows devices. If you’d be interested in Mac and Linux as well, then please let us know. But we saw that the main need is around Windows. Let me just find an online Windows device and software installation. Here, this is what you know—this is what currently exists. But if I’m going to search for 7-Zip, then here, this is the 7-Zip that I uploaded directly to my repository along with all the other options from the public repository. I can just select this one, and I also have the option to add a parameter upon installation. If you added one to the package itself, then that will apply, and you can add any other parameters on top. You can install that directly from here, or you can also add this to a software bundle. 

Profiles I’m going to now show you how to select a bundle. I created one already. You come prepared. I try. So, I’ve got a bundle that has mixed packages. I’ve got my custom package here and also one that I selected from Chocolatey, and I can install that on my device. The results will also show in the recent processor report, as we do for any software installation today. We can also add this to an automation profile. So, I can go to my automation profiles and search for my profile here. I added the software bundle, so every time this automation profile runs, it will attempt to install these packages that are in the bundle on the managed devices. If you want to upload a new version of those packages, you can just add the newer version to the bundle, and it will update. The results will show in the automation feedback report, so successful installations will be added to the automation feedback report as well. You can always run the profile on newly installed agents to make sure that you have all the software and packages that you want on the device installed as they’re added to Atera. 

Dana: Before you move on, can you just show again where the software repository was? Someone was asking that in the Q&A. 

Yasmin: Yes, as I mentioned again, it’s still not open to everyone, so you won’t see it yet. But it will be under Admin, Monitoring, Software Management, which today is called Software Bundles, but it will be renamed Software Management. It will be here.

Great, thank you. No problem. So, that was about the private repo. Hopefully, it will be out very soon and can help you streamline your work. I’d love to hear some comments on what you think and if you currently manage your repository today or if you would need to set a new one up. That’s also very interesting. We are considering adding the option to have hosted storage within Atera, so that’s something we’re looking into for the future. It would be great to hear what you guys need. 

I’m going to hop on to the next feature, which is regarding Linux. In the past year, we’ve added a lot of new capabilities to our Linux agent, like remote control with AnyDesk, connecting with SSH, and we’ve expanded the capabilities as well. We currently support Ubuntu and Debian, and we’re looking into other operating systems as well. If that’s anything you use or don’t use but need, then we’d love to know. 

I’m going to demo what we’ve added now. We’ve heard the need around updates and patching. We currently support patching for Windows and Mac, and we wanted to expand and add it to Linux as well. So, we’ve added a new package manager here, which allows you to manage and update packages through Linux. We use APT-GET in the background, and you can see all of your packages that have an available upgrade with information about that package: the name, the new available version that you can upgrade to, any classification priority, who the maintainer is, and the installation size. You can also go to any official links that show bugs with those packages if you want to look into it further and decide if you want to upgrade or not. Any dependencies that will be installed with this package upgrade are also shown. You can also browse any existing packages and information about them. This will show you a list of all installed packages on your managed device, with additional information and links to the homepage and any bugs. You can easily select a package or all packages that you want to upgrade and upgrade them directly through Atera. I know that most of you probably do that today with the terminal or SSH, but we thought making it a bit easier and more accessible through the UI could make the job easier. 

The real feature that we wanted to get to is automating this. Security and compliance are high priorities for everyone, and we want to eliminate as much as possible any manual tasks and repetitive tasks that you do on a regular basis and automate them. We’ve added Linux package upgrades to our automation profiles. This feature will be rolled out in the next few weeks, so this is another sneak peek. We’ve added this new section here for Linux package upgrades. At the moment, it will upgrade all packages. We’re wondering if you need any exceptions, if you need to exclude any packages, or if you work on a whitelist or blacklist basis. That’s for future development, and we’d be really interested to know. We also support reboot if needed for Linux upgrades. If a package was installed and it needs a reboot and reboot if needed is selected, then that device will reboot when this automation profile runs. The results of the upgrade will be logged in the patch and automation feedback report. Here, we can see I have six agents under this report that were offline when this profile ran, so they didn’t upgrade. But I have eight agents that are up to date, and all packages were upgraded. Can we patch approval for Linux at any point? That’s something we’d be interested to know if there’s a need around it. What I’ve heard so far is that excluding patches or packages to be upgraded is something that is needed, but postponing is something I’d be interested to know if you do for Linux as well. I know there aren’t as many managed Linux devices as there are Windows or Mac, so it leads down to the need and priorities. Let us know in the chat if you need patch approval and postponing upgrades for Linux. 

If you have any questions regarding what I’ve shown so far, just pop them in the Q&A, and we’ll have time in the end to answer everything. I’m going to hop over to the next feature, which is our new devices page. We released the new devices page with the option to switch back to the old page because we didn’t have all the functionality ready yet, which was the advanced filters and custom field filtering. We wanted you guys to try it out and give us feedback. If you have any and you haven’t submitted it to us yet, then you can do that here. We’re constantly working on adding features and improving this page, so we’d love to know. 

Just a few things about what’s different on this page. We’ve changed the default view to be the compact view so you can see more devices on the list. I’m going to clean my filters so we can see everything. The compact view shows us small devices on the list, but if you want to switch back, you can manage your view. You can change the density back to the detailed view and see bigger tiles for each device. You can also manage the columns that you want to see, add or remove them, and move them around—just make it work for you. In case you didn’t know that was available, you can do that here. You can add this information and move it around. You can also sort by clicking on the column name, and you can save a view with all the changes you’ve made. 

Another thing is the quick customer filter here. You’ve also got it in the filter drawer, but if you quickly want to filter by a customer or site, you can easily do that from here. Here’s my Brad Pitt customer. The thing that you’ve been waiting for—the advanced filters. We released the page without it, and whoever needed to use the custom filters moved back to the old page in the meantime. This will be out very, very soon. We’re just running a lot of tests on it because we want to make sure that the best quality is delivered, and it’s touching data here, so we want to ensure everything’s as it should be. We’ve changed the logic to what the advanced filters were. Now we’ve created groups of “and” and “or” so you can create complex queries and different views and save them for your devices. We’ve also put the custom fields filter in here, so you don’t have a separate custom fields filter like you did before. Everything’s under the advanced filters here, and you can use them. We’ve added the search option so I can search for my custom fields. I’ve got quite a few custom fields, so I could just select my checkbox if it’s checked or not. We’ve done a lot of work regarding fixing the logic of these fields and added some more options under the last seen option. Basically, everything was reviewed, rewritten, and fixed, so it should be a really good experience using the custom fields and the advanced filters once they’re out. 

It’s also really nice because now we have the option to export to Excel. If you need to create some sort of report and generate a complex query for your devices, you can save it to a view or export it to Excel and continue to work on it outside of Atera. If you have any comments about the look, feel, functionality, or anything else you’d like to see or not see, let us know. We’re really interested to hear. We’re still allowing the option to go back. Sometimes change can be difficult and needs a bit of time to get used to. We’re still working on making sure the page is stable and fast. So, anything you’ve seen, please let us know. It’s always best to open a support ticket so they can escalate if needed to the dev team so we can fix everything. 

Dana: Agreed. Definitely try it out if you haven’t and give us some feedback because we do have that button, and it will really help us make sure that it’s right for you. So, definitely try it out. 

Yasmin: Yep, and as I said, you’ve got the give feedback button here. That comes directly to me. I get a Slack notification for each one of you that replies to that survey, so I see everything you write. But still, it’s great to open a support ticket so they can pull out any logs and information to escalate back to us so we can investigate if you have any issues or requests. Cool, so we’re going to jump on to the next feature. This was actually really highly requested for quite some time, so I was really excited to develop this one: scheduled shutdown actions. This is supported for all operating systems—Windows, Mac, and Linux. I’m going to show you how that works. It works on online and offline devices. Just for preference, I’m going to select an online device. Up until now, if you wanted to do a reboot, log off, or shutdown ad hoc, you could do it from here. You’d go to manage shutdown action and select the action that you wanted. If you wanted to schedule a future action, then you’d need to create an automation profile and schedule it to run. But we know that that wasn’t the best solution for an ad hoc restart if you wanted to restart someone’s computer during lunch or at nighttime or schedule a future shutdown. We know how sensitive touching users’ computers can be, so we came out with this solution. I can schedule a future action. I’m going to select a restart. I can choose to do it now as it was up until now, or I can schedule a future restart. It’s in 30-minute increments. I’m going to select to do a restart tonight. It’s 7:29 where I am now, so I’m going to give myself some more time.

Let’s say 11:00 p.m. and schedule. Done. So, we’ve got the restart scheduled here. You can see it there, and you can see it here that the shutdown action was scheduled. This device will go through a restart at 11:00 p.m. Once that happens, you’ll see the result in the recent processor report. If the device is offline, then, of course, nothing will happen, and we won’t send the command. But if it is online, then we’ll send the restart command at 11:00 p.m. and log the results in the recent processes report. It’s important to mention that it is the account time zone, so whatever the account is set to be, that will be the time zone for the restart. If there’s a need for additional support for other time zones, such as the device time zone, that’s something we can consider adding. Let us know if that’s something that you need. 

Will there be a notification for the end user? Yes, I was just about to mention that. The end user will see a notification on Windows, either a toast notification or an overlay, depending on the operating system, when a shutdown, reset, or log out is scheduled. It will tell them that it was scheduled by the technician with the name of the company that’s set in Atera. At the moment, for Mac and Linux, we don’t have these notifications. Also, you will be able to see that the action was scheduled here on the devices page with this little icon, so you can see at a glance that you have a scheduled shutdown action for this device. 

Last but not least, a few changes for the agent installation and uninstallation. We’ve had a lot of requests around making the agent installer silent. We thought about this a lot—how can we do it and also make sure that the devices are secure, ensuring that someone doesn’t accidentally install an Atera agent on a device where they shouldn’t. We understand how sensitive the RMM agent is; it basically allows you to do a lot of things on the device, and we don’t want someone who doesn’t need access to the device to have access. 

We made some changes to the installation logic. If you’re installing the Atera agent on a domain-managed device, meaning it’s under a Windows domain, then you would need system privileges to silently install the agent. If you’re installing it with user privileges, the end user would need to approve the installation. This is to make sure that the admin of that domain is the only one distributing such a sensitive system to the managed devices. You will be able to install via GPO, via Active Directory, anything that has system privileges on those devices. If it’s a non-domain device, meaning it’s part of a workgroup or standalone network, then the installation will be silent no matter what privileges it’s installed on. There isn’t a domain, and there isn’t a specific admin that has control over that network, so we’ve loosened it up a bit, and the installation will always be silent, meaning the end user will not need to approve that installation. Hopefully, this helps. If there are still any other comments, feedback, or requests, we’re always here to hear them, but hopefully, this will make it a bit easier. I know that deploying agents isn’t always the easiest task, so I really hope this makes your life a little bit better. 

Another thing we’ve added, which is a step in the way of the entire feature users requested, is the uninstall prevention. Under Admin, I’m going to hop over to my account settings under Agent. We’ve added the Atera agent uninstall prevention. If you turn this on and save, of course, the end user won’t be able to uninstall the agent from the programs list on their device. They’ll get a popup saying this is blocked, please contact your IT technician or admin to remove this software. You can uninstall it from the Atera console. There are a few other methods to uninstall it, and that’s listed in our knowledge base, but basically, it’s supposed to protect you guys from a mistake or an error where an end user is browsing through their device, sees the Atera agent, thinks “Oh, what’s this? I don’t recognize it, I’ll uninstall it.” If they really, really want to uninstall the agent, they can still do that. It’s not bulletproof, but it should cover most cases. There was a little bit of confusion around this feature because we rolled it out, and then there was an issue, so we rolled back, and then users said it wasn’t working. I really apologize about the confusion there, but it is out in production now, and it’s on the newest agent version. If you have any old agents out there, they won’t have this feature available. The agent automatically updates, so in most cases, we should be good. If you turn this on, then all agents will get this update, and it will protect the agent from being uninstalled. If this doesn’t answer your needs, I do know that there’s a big request on our features board for protecting it with a password. I’d be really interested to hear why and have a conversation about that, so feel free to reach out to us. I’d be very happy to chat. 

We do have some questions actually about both uninstall prevention and silent installation. One, someone is asking if they can get an alert if someone tries to uninstall. That isn’t supported yet, but it’s definitely something we’re looking into. That is a great feature request. Another question here is how will silent installation work on Azure AD or Entra joined devices. If you install it through Azure, or by its new name Entra, and you do it with domain admin privileges or system privileges, then it should be silent. Great, thank you very much for that overview of all of these new features and some sneak peeks. It looks like a lot of really exciting stuff. Now we are going to move over to Yaki. Are you ready to share, Yaki? 

Yaki: I’m ready, hopefully. Thank you, Yasmin. Hopefully, everything works. I’ll even try to turn on my camera. For some of the questions that we haven’t gotten to yet, we will get to them at the end in the live Q&A, so don’t worry. Can you guys see my screen? 

Dana: Yes, perfect. 

Yaki: All right, so we have a couple of exciting things to share today. The first thing I want to start with is the new ticket page interface. For those of you who are not using our ticketing, this is what a ticket would look like today. What I’m going to do now is switch to the new UI. This is available already for some of our users. We’re actually beta testing this with a couple of hundred users, and we hope to roll it out to everybody very soon. Some of you might see the blue banner I just clicked, and some of you will see it in the coming days. I want to go through some of the thoughts we had and some of the improvements we’ve implemented on this page—a lot of cool stuff. 

The first thing we did is we went ahead and turned everything into autosave. A lot of customers were complaining that it takes a while to do a lot of actions. Today, if you want to change the status, you can change the status with a click of a button. The same goes for changing the technician. If you want to change any of the ticket properties, let’s say I want to raise the priority, it takes one click less. With the amount of actions you guys need to do on tickets on a daily basis, we hope this will save a lot of unnecessary clicks. The entire page is responsive and autosaving, as I mentioned. 

Some other cool things we’ve added are in the text area where you draft the responses and the internal notes. Switching between public replies and internal notes is easier now; it’s one click instead of two, and then you can write anything you want. We’ve also introduced the ability to send notes or replies and change the status simultaneously. I can save this and change the status to open, which also will help you save time. 

We’ve actually changed the way a lot of the information on the page is organized. As you can see on the right side here, I have a detached scrolling element, and you have all the different modules. We noticed some of our users are not using everything. For example, if ticket properties are something you don’t leverage on a daily basis and you sort of stick with the basics, you can collapse this. The same goes for the calendar integration, and all these preferences are remembered. So, the next time you go into the page, we’re not going to show you the info that is less relevant for you. 

We also made some improvements around the conversation. This was something we heard from many of our users. For those of you using our ticketing, you know that the conversation was sorted from oldest to newest, meaning you would have to read through the entire conversation to see how things unfolded. Many of our customers mentioned that they want to have the opposite, so we went ahead and flipped it. Now the default is newest. Of course, you can change it if you prefer the old method, and we will remember your choice. We’ve also added filtering capabilities so you can look at only the public replies or only the internal notes. We connected the ticket activity, meaning all the changes that were done to the ticket, such as assignments, notes being added, ticket automation rules that were run.

Interface As I said, it’s open to selected customers already, and we’re opening it to more and more people basically every single week. If you have any feedback, we have this button here. As Yasmin mentioned, she’s getting all the feedback for the devices page. I’m receiving all the feedback for this page, and we’re very eager to hear from you guys and see how it can be improved even more. So that is it for the new ticket page, and I want to talk about the next feature that is still not released but is also very anticipated: ticket forms or ticket templates. We chose to call them ticket forms. This is still not released to our customers, and I will give you a sneak peek of what this is going to look like. Hopefully, we will release this in the coming weeks. 

Ticket forms basically give you the option to create different forms and templates for how to submit a ticket, a service request, etc. They allow you to control the different custom fields and their order based on the ticket type. I have two examples that I already created here. Let’s go to the first one. Actually, let’s do the second one: New Employee. The form I created here is called New Employee, and what I see in the center here are all the different fields that must be filled in to submit a new employee ticket. We have our default fields: the technician, ticket type, contract (for those of you using the MSP module), priority, and impact. Down here, I decided to add a bunch of custom fields that I found necessary whenever a new employee ticket is being created. In this case, I have the start date, which is a date type of field, the department, which is a dropdown between all the different departments that I have, and I also want to know if this is a remote employee—it’s simply a checkbox, a yes or no question. From here, you can also add different fields, simply drag and drop and reorder them if you want. If you want to create new fields, you can also do that from here. 

You will see this feature and be able to choose the form in different places in the platform. The first place would be when creating a new ticket. This is the new ticket screen. Let’s say I have a new employee. This would be my ticket title, and I will select the form New Employee. Then, you will only see the custom fields that are relevant for our new employees, as mentioned: the department, the start date, and the checkbox if they’re remote. If you choose a different template, like the equipment request, you will see I will now need to fill in the product type, the approving manager, and the SKU. Of course, if you decide any of the custom fields are mandatory or not mandatory, it will also be reflected here. In this case, in the equipment request, I chose the SKU to be mandatory, and I will have to fill this in whenever I create a new ticket. Obviously, these templates are also requested in the service portal in the customer portal. Let’s go ahead and navigate there and create a new ticket. This would be me as an end user creating a new ticket and saying, “I need a screen.” Then, I will have to choose a form template. In this case, it’s an equipment request, and then I will have the reason needed, the product type, the approving manager, and the SKU. You can make sure all these fields are mandatory. In this case, I chose not to, but if you choose that they’re mandatory, the end user will have to fill all of those in before they open the equipment request. That would be it for forms. As I said, this is coming soon. We’re very excited about this. We’re going to have a short beta testing phase and then open this to everybody. Exciting stuff—it looks really awesome down the line. Thank you. We also have some plans on introducing automation rules based on forms. Let’s say a new equipment request is being created in the system, then you can assign it to the relevant technician, escalate it, notify someone, and connect this to our ticket automation rules. Exciting stuff coming. 

Dana: Do we have more time to go over some AI features, or do we want to go to the Q&A? 

Yaki: I think we can briefly discuss maybe just one and then move ahead. Cool. I would actually have to open a new window and log into my other account. 

Dana: No problem. In the meantime, we can already start looking at some of the questions that we have. 

Yaki: So another small sneak peek, but this one is very exciting. Obviously, it has to do with AI. For those of you who are familiar, when you go to the tickets list or any one of the tickets, you have the AI assistant or the co-pilot that accompanies you guys, the technicians. We’ve added some cool improvements to it. Let’s go to this one: a slow PC issue. I’ll briefly go over the conversation as there’s a lot of info here. It looks like a slow computer, and this user actually spoke to our chatbot, the AI chatbot. Let’s say we are the technicians and we received this ticket and we want to click the AI assistant. What we’ve added now is a complete set of diagnostics and actions based on the ticket history. In this case, the AI assistant realized that there’s a PC that is running slow. The technician already checked CPU usage and disk speed, which were normal. We can actually see all these diagnostics here that happened automatically by the AI bot when this ticket was created. The bot checked the disk speeds, CPU usage, motherboard information, and processor information. This is just one example, and I really want to cover everything, so I’ll show you just a couple more use cases. We have another case here where someone complained about a slow internet connection. Once they complained, the AI assistant, the bot, ran an internet connection test, a speed test, and website connectivity. We checked the port connectivity and saw it succeeded. This is very cool. I want to show you one last use case. I know this is very quick and a lot to take in. This would be a case where a user goes to the service portal. I’m an end user now, and let’s say they want to connect to Zoom. Let’s say they need Zoom and don’t have it. Again, this is me as an end user, and everything you’re seeing now is in a closed beta that we’re working with a small group of customers just to see that everything is working and we’re setting expectations. As I said, I need Zoom, and then the computer is checking if I need Zoom and is asking me, “Can you confirm you already have Zoom installed on your system?” In this case, I don’t, so I’m going to say I don’t, I need it. Now, hopefully, the chatbot is going to offer the Zoom client for me. The reason this is being offered—I’m just going to go ahead and approve this—is because as admins, I’m going to go to the admin management screen of the portal. We have a list of software here that we decided to curate, and we’re actually actively curating. We have the Zoom plugin here and the Zoom application down here, I believe. 

Dana: I’d also add to that, Yaki, that if you have the private repository feature, then you’ll also be able to add custom software here as well. 

Yaki: Absolutely. The Zoom client is here as part of the software we’ve approved. As Yasmin mentioned, the private repository will also connect to this self-service module. Now, if we actually go to the device that belongs to this user, to this agent, and to the list of software inventory, hopefully, it was installed by now. I see that not yet, but any minute now, Zoom should be installed on this computer. That would be it for my demo. I think we can go to the live Q&A. 

Dana: Awesome. Thank you. Really exciting stuff, and hopefully, we’ll be showing that all to you guys very, very soon. You’ll be able to test it out once it’s out of the closed beta. A lot to look forward to on both ends, both RMM and PSA. Let’s move on to some questions. One of the questions that we got is for Yasmin about—hold on, let me find it because, of course, now I lost it. Ah, okay. For the private software repo, someone asked if there’s any way for regular files to be uploaded so that they can be deployed in bulk. 

Yasmin: Yes, as I showed, you can upload packages, and you can upload any package you like once you’ve connected to a repository. You can install it in bulk. We have a bulk software installation command, so that will apply for Windows devices. 

Dana: Awesome. I see here there’s also some wish list items that people wrote about. Like we mentioned before, definitely put your wish list items in the features request board. We really do look at it, and we take those ideas and run with them, so definitely put them in there. Let’s see if there are any other questions. Feel free to continue adding if there’s anything that hasn’t been talked about yet. You know what, I think actually—ah, here we go. How long does it take for the AI option to become available? I created an “Internet is slow” ticket, but the AI icon has not come up. 

Yaki: Who’s asking that? 

Dana: Cory is asking this. I want to just make sure that I understand it right. 

Yaki: I see. Cory, the truth is that the AI button should already be available. If you’re in the regular environment, you should already have the AI icon available next to your tickets. If you don’t, definitely send a support request because that’s something that you should be seeing. If you’re in the trial, it does only show up for the sample ticket. 

Dana: Correct. The reason is we wanted to make sure the AI experience is smooth and makes sense. It’s quite hard during your trial to have a ticket with the back and forth and the whole backstory. So that is the reason the AI assistant is limited during the trial. 

Yaki: Yes. 

Dana: Another question is, “Is Atera dark mode coming soon?” It’s a great question and one we get a lot. It’s something we are definitely considering, so we will let you know if that ends up being rolled out anytime soon. Any other questions before we move ahead to our survey? I don’t see anything. Like I said, definitely feature requests—lay them on us. We’re always open to hearing more, and also any feedback that you guys have on the things that you’ve seen today or in general. We have a lot of places within the app to provide feedback, so anywhere you see that, we really are looking at it. As Yasmin said, we have a Slack channel for feedback, so people are looking at what you’re saying. 

Let’s move on to the survey. If you have a quick minute before you head out, we’d love for you to let us know how we did, what we can improve upon, and anything that you can tell us for feedback. Thank you guys so much for joining today. Yaki, Yasmin, thanks for the demos—they were really, really insightful, and we’re really excited. 

Yaki: Thank you. Sorry about my camera. I’m not sure what happened, but I’m here. 

Dana: Technical difficulties, what can we say? Thank you, everybody. 

Yaki: Thanks, everyone, for joining. 

Dana: Thanks, everyone, for joining.