• ConnectWise Automate
• Kaseya VSA 
• N-central
• SyncroMSP: Look in your Syncro portal under scripts for the “AutoElevate (Official)” deployment script
• Datto RMM (with Autotask PSA)
• For a PowerShell script

In Edge you would click on the “lock” in the top left of the browser. The lock next to the Left of the URL address then click “Site permissions” to open the screen containing the various permission settings.

Scroll down in the list to “Notifications” and change the down-down menu choice to “Allow”

.

In Firefox after logging into the Admin portal you should see an icon in the top left of the browser to the left of the URL address which looks like a chat icon and be given the ability to select “Allow Notifications”.

If this has already been set to ‘Never Allow’ you can change the setting in Firefox by clicking the ‘Hamburger’ menu on the right-hand side of the screen and then from the menu selecting “Options”

Click on “Privacy & Security” and then scroll down in the list to “Permissions” and click the “Settings” button next to ‘Notifications’

Find the Admin Portal address in the list and set the status drop-down to “Allow” and then “Save Changed”  

To have the browser notifications show up in the Windows notification area you would first need to allow it in your browser and then would need to enable it in Windows by doing the following:

• In Windows go to Settings->System->Notifications & Actions

• Toggle the “Get notifications from apps and other senders” to “ON”

• Scroll down through the list and make sure the browser that you have authenticated in AutoElevate and enabled notifications for (in this case Chrome) is toggled to “ON”

• Click on the browser in the list and set the “Show notification banners” and “Show notifications in action center” to on by checking the boxes. You may also set the other notification settings based on your preferences here.

Easily turn events into rules. From the “Events” screen in the Admin Portal (https://msp.autoelevate.com/) select a check box next to an UAC event record and then from the “Actions” menu select “Convert to Rule”, select whether to Approve/Deny and then whether you want the rule to apply Globally, a Company, Location, or a single Computer.

From the “Rules” screen you can see that rules that have been made and the elevation type (Admin/User) that they are set to by looking what is listed in the “Elevation Type” column. To change an elevation rule from using Admin elevation to User elevation or vice-versa you would select the check box next to the rule and then from the “Actions” menu select either “Set to Admin” or “Set to User” under ‘Elevation Type’.

You can set the default elevation type from the Settings menu from the ‘Default Elevation Type’ drop-down under “Requests & Rules” [picture]

From the “Rules” screen you can Delete, Move or Copy rules. To delete simply click on the trash can next to the rule and confirm at the prompt. You can Move or Copy rules from the “Actions” menu.

• To Move rules from one Computer/Location/Company/Globally to another: https://support.autoelevate.com/hc/en-us/articles/360002665652-Moving-Rules
• To Copy rules from one Computer/Location/Company/Globally to another: https://support.autoelevate.com/hc/en-us/articles/360004331772-Copying-Rules

To prevent a technician from being able to make rules you can set their User Role to “Technician (Level 1)” and/or adjust their Company access. Please see: https://support.autoelevate.com/hc/en-us/articles/360018899091-User-Management-from-the-Admin-Portal

Hopefully this information has been helpful. There is more information on this and other technical topics available on our support site at https://support.autoelevate.com or you can specifically email questions to support@autoelevate.com and we’ll be happy to assist.

Admin elevation is ideal for the elevation of system functions, installation of most MSI and executables, examination of machines that have potentially been breached, or other Technician activities where security is a concern. With Admin elevation the credential being used for the Admin account is rotated and changed before and after every single use so that each elevation happens with a credential that is only good for that 1 moment in time, that 1 thing, is not stored anywhere, transmitted anywhere, and at rest is just a standard user account. Additionally, because Admin elevation is happening with just a local account the things elevated with Admin elevation won’t have access to mapped drives, network resources, or servers on your network(s) which can help you exercise the principle of least privilege and operate in a very secure way.

User elevation is ideal for installation, updates, or Line of Business applications that need to be done ‘as the user’. User elevation elevates to Administrator privileges but is done as the currently logged in user and therefore has the ‘context’ of that user. Things that are elevated with User elevation will have access to anything that the user has permissions to access on the computer like the user’s profile, HKEY Current User registry keys, App Data folder in their profile and also what they have access to on the network such as network printers, mapped drives, server shares, etc.

Here is an article that describes the elevation types that are used by AutoElevate: https://support.autoelevate.com/hc/en-us/articles/360030799571-Elevation-Types 

User elevation displays an additional dialog in the user process the 1st time it is used (and whenever the user’s password is changed) identifying the user that is logged in and asking the user to enter their Windows password and confirm it. Once submitted it is encrypted and stored locally in the Window Credential Manager (is not stored or transmitted off the machine) for use in any User elevation rule or action for the named user.

YES. The dialog that is displayed during the User elevation process can be customized to suit your preferences and is typically sufficient communication for most MSPs implementing User elevation rules. Some AutoElevate partners prefer to assist their users by pre-populating this credential prior to the application of any User elevation rules or going Live thus eliminating the user being prompted for credential confirmation on the 1st user elevation event.

You can prepopulate the credential manually by communicating and coordinating with your users and then running the Credential Input dialog manually (c:\Program Files (x86)\AutoElevate\AECredentialInput.exe) thus allowing them to enter the Credential prior to an elevation event.

This could also be accomplished by going into Technician mode when the desired user is logged into Windows, running something that requires Admin privileges (anything producing a UAC), and then clicking the “User Elevation” button which will then cause the Credential input box to appear for the user. Once their credential has been successfully populated, user elevation can be used for that logged in user on that machine for approved elevations in Real Time or by a Rule without any further input by the user.

There is more information regarding this and other technical topics on our support site at https://support.autoelevate.com or you can specifically email questions to support@autoelevate.com and we’ll be happy to assist.