AutoElevate

In the Admin Portal we can use Convert to Rule on an elevation request after it's been approved, denied or allowed once, and on elevation events. The Partner API can only create a rule at decision time, through approve or deny with createRule on a pending request, and the Partner API KB says creating a rule from scratch isn't available yet. We're building technician tooling on the Partner API and often decide a rule is needed after a one-time approval. Please add an endpoint like POST /api/v1/elevation-requests/{id}/convert-to-rule (and the same for elevation events), taking ruleLevel, approved, elevationType and the same options the portal offers. Being able to set or change a rule's scope through PATCH would help too.

We're adding self-service setup for the Zendesk integration. Today, connecting Zendesk to AutoElevate goes through our support team. With this change, you'll be able to connect Zendesk and manage its integration settings yourself in the admin portal, without contacting support.

We're adding self-service setup for the ConnectWise Manage integration. Today, connecting ConnectWise Manage to AutoElevate goes through a support ticket. With this change, you'll be able to connect ConnectWise Manage and manage its integration settings yourself in the admin portal, without contacting support.

We're fixing an issue where AutoElevate can't complete an elevation when the UAC prompt opens with a username already filled in, for example because of a Group Policy setting or the application itself. AutoElevate works when the prompt is blank, but a pre-filled username can cause the elevation to fail. The fix changes how AutoElevate answers the UAC prompt so a pre-filled username no longer matters. Vote and follow this post to be notified when it's available.

Currently, Blocker rule precedence follows that the 'lowest level' in the hierarchy (Computer) takes precedence OVER higher levels. This also means that 'All Companies' rules are superseded by more specific 'Whole Company' rules. It would be very helpful to REVERSE this rule precedence; as the way 'recommended blocks' work and how organizations scale, it quickly becomes unfeasible to maintain a list of identical exceptions (e.g., for your security stack or RMM tools) across many different companies, per-company, while having the recommended blocks at the 'All Companies' level. (The recommended blocks are more general and almost never change; the rule exceptions change frequently. One level lower in the precedence means we have to multiply the total number by the number of tenants, at the minimum)

We're adding self-service settings for the Email Connector. Today, Email Connector settings are set up and changed by our support team. With this change, you'll be able to view and edit your Email Connector settings yourself in the admin portal, without contacting support.

It would be helpful if there was a link from Elevation Rule > Elevation Request (if applicable). There is additional context/data in that view (e.g., Ticket Number, User Explanation, "Additional App Info") that can be helpful in reassessing why the rule was created in the first place and how to potentially improve efficacy. Adding the data into "Original Event Info" or adding another section like "Elevation Request Details" and keeping everything on the same page would be a nice touch.

We're working on making Technician Mode available on computers where more than one user is signed in at the same time, such as terminal servers and Azure Virtual Desktop multi-session hosts. Today Technician Mode can't start when multiple sessions are active.

We're adding Technician Mode ticketing for HaloPSA. When a technician starts a Technician Mode session, AutoElevate will be able to create or update a HaloPSA ticket and track time for the session, the same way Technician Mode ticketing works with our other PSA integrations today.

In the portal, when selecting multiple devices at a time, it would be nice if you could do a "shift-->click" to select all devices between those two clicks instead of having to select each one individually. You know, click the top device, hold down shift, click a device that is 20 down the list and all devices in between would also be selected.