AutoElevate

We are seeing a higher volume of elevation requests and see the tickets hit their SLA time in connectwise. we would love to have a feature where if the request wasn't Approved or denied within a set time it would be set as a one-time denial. this would prevent from also having to search through an older request for elevation if the Real time timer timed out and the user tries to run the request again

Elevation rules that target specific users — not just machines — so a single endpoint can have different elevation behavior per user.

Can we add the ticket number details to the elevation event? This would be really helpful for us to help track down the ticket when starting from the AutoElevate portal looking at events. Also, for auditing purposes it would be ideal.

Scoping Blocker rules per user on the same machine — so technicians can run tools like PowerShell or WScript while standard users on the same device stay blocked.

I'd love to see a mode between Policy and Live, wherein the UAC prompt is not automatically dismissed, the overlay is loaded with its beneficial analysis, and the user/admin has the option to submit a request, enter admin credentials, or if already an admin, simply click Yes/No.

if a Request was denied, a user could optionally "appeal" with an explanation as to why they think an exception should be made. (This was extracted from the "End User Elevation Request Explanation" item)

We are experiencing a high volume of elevation requests related to shpafact.dll (identified as “Virtual Factory for Windows Defender Firewall CPL”), which appear to be triggered indirectly by various parent processes across different applications. 1 Currently, each of these requests must be reviewed and approved manually, resulting in a significant operational burden and increased technician workload. 1 Requested Enhancement We would like to request more granular rule criteria options to reduce unnecessary elevation prompts while maintaining security integrity. Specifically: Ability to create elevation rules based on parent process Support for rule conditions such as: Command-line arguments Event title File description Context-aware elevation rules that allow controlled approvals without broadly approving a DLL globally Business Impact Without these capabilities: Technicians must repeatedly investigate similar elevation events Productivity is reduced due to manual approvals There is increased risk of either over-approving or delaying legitimate operations Desired Outcome Providing more flexible and context-aware elevation rule options would: Reduce repetitive approval workflows Maintain strong security controls Improve operational efficiency for managed environments

Tracking the remaining gaps between the Mac and Windows agents so the macOS agent can do everything the Windows one does.

It would be great if we could set a timer for offline devices to be automatically removed from the autoelevate portal. For example, if a machine has been offline for 90 days, remove it.

The ability to create "OR" logic in rules would allow for better rule management of complex systems and processes. Especially for certificate-based rules, to structure rules with and/or functionality would allow for rule consolidation. For Example, the following rule would cover all installation components that may otherwise take 2-3 separate rules: Cert = XYZ Company AND Product Name = XYZ Installation Services OR File Name = setup.exe OR File Name = drivers.dll