AutoElevate

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

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

The ability to approve/deny a request for times when the computer is offline and not able to reach AE servers.

The Windows agent supports Advanced Elevation Rules that auto-approve or auto-deny future UAC requests based on file path, file name, product name, MD5 hash, and/or publisher certificate — and those rules can be scoped to a single machine, a group, or the entire org. Once a rule exists, other users never even have to submit a request for that installer. The macOS agent (now GA) currently only supports session-based elevation with manual technician approve/deny — there's no equivalent rule engine to auto-allow known-good installers/apps org-wide. Request: bring file- and/or code-signing-identity-based auto-approve/deny rules to the macOS agent, matching the spirit of the Windows Advanced Elevation Rules (e.g., match on bundle ID, code signature/Team ID, notarization status, and/or path), scoped per-machine/group/org the same way. This would close the biggest functional gap between the Windows and Mac agents and let MSPs actually reach "zero standing admin" on mixed fleets without turning Mac elevation into a 100%-manual-approval workflow. Here's a draft ready to post on roadmap.cyberfox.com/autoelevate :

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

We're upgrading the AutoElevate admin portal under the hood: modern build tooling, TypeScript, a refreshed service layer, and cleanup of legacy dependencies. The goal is faster load times, better stability, and a stronger foundation for the UI improvements coming next.

We're planning to let the logo you've already uploaded in Settings display directly on agent dialogs and message customizations — no more needing to host your logo at an external URL just to show it in elevation prompts or denial messages. We're also looking at supporting separate logos for different contexts (for example, one for the agent dialogs and one for the admin console) to give MSPs more branding flexibility.

It would be nice to have temporal controls on rule creation. E.g., An user is cleaning up their installed programs - allow access to appwiz.cpl for 3 hours. Upon expiration the rule is deactivated or deleted entirely

PLEASE NOTE: The following only seems to apply where organizations have implemented SSO into the CyberFox applications with an IdP such as Microsoft Entra. We have customers using Microsoft Intune Mobile Application Management (MAM) for BYOD devices without MDM enrollment. Currently, AutoElevate and other CyberFOX mobile applications cannot be protected with Microsoft Intune App Protection Policies because they do not appear to support the Microsoft Intune App SDK. We would like CyberFOX to evaluate integrating the Microsoft Intune App SDK for iOS and Android into all CyberFOX mobile applications. This would allow organizations to enforce app-level protections such as application PINs, selective wipe of corporate data, prevention of data transfer to unmanaged applications, encryption of organizational data, Conditional Access integration, and other Intune App Protection Policy controls on unmanaged BYOD devices. Microsoft provides the Intune App SDK specifically for software vendors to enable these capabilities in their mobile applications. Once integrated, CyberFOX applications could be managed and protected alongside Microsoft 365 applications in organizations using Intune MAM. Support for the Intune App SDK would significantly improve the usability of CyberFOX products in regulated environments, including organizations pursuing CMMC, NIST 800-171, CJIS, HIPAA, and similar compliance frameworks, where customers increasingly rely on Intune App Protection Policies to secure corporate data on personally owned mobile devices.

We support many customers that have many different regulatory requirements. Not all of our staff can support all of those environments. We use the "Company Access" area on each user to restrict environments, but each time a new org comes on board that requires exemption, each user account has to be modified. With hundreds of users, this is a very tedious task. It would be fantastic if Tags or Groups could be introduced so we could not only easily identify those customers, but also scale company access more easily.