AutoElevate

From the "elevation events" page, there should be an indication that a rule has already been created from that specific event. Otherwise, you have multiple people that could be wasting time creating the same rule from the same event. This should be as easy as indicating with a field/column of "Rule created" (yes/no) or a visual indication like a green/red dot or a hover-over fly-out that says "rule created".

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 adding a Last Sign-In column to the Users grid in the admin portal, so you can see at a glance when each portal user last signed in. That makes it easy to spot technician accounts that haven't been used in a while and should be reviewed or disabled.

Today, enabling Technician Mode or approving a Just-in-Time Log In from the mobile app means scanning a QR code shown on the endpoint. That's a problem when the technician is already using their phone to reach the machine, for example through a mobile remote-access tool. We're adding a way to approve these requests directly in the AutoElevate mobile app with no QR scan, similar to how Technician Mode can already be turned on from the admin portal.

The new local group authorization function adds 3 unnecessary prompt steps during JIT Admin QR code logins, when only one local group is authorized. Please add an option to bypass group selection and log in directly upon scanning, as was previously the case.

Currently, the new UI always defaults to only showing today. Todat is a good default to have set to a new account, but if I select "7 days ago" in "Elevation Events" Page, and go to "Elevation Requests" page, it automatically goes back to "Today", even if I move to a page without that time filter, like "Dashboard" and then go back to the first page, it also goes back to "Today". Maybe make it a user configurable option if oppinions are devided, but currently, this gives a strange feeling of, didn't I had this set. Certainly if you are reviewing things of last weekend, what elevation events where there, what requests, what blocker events,...

The scope only seems to be working on dashboard and computer submenu's. So even if I'm in the scope of company1, I do see under elevation events/elevation requests/blocker events/blocker requests all events and request of all users, not just company1

If you have a company selected as scope in the new UI. You only see the Event and Blocker rules created specifically on this company, not ALL rules that apply to that company. Because therefor you should also see the rules applied to All Companies If I have rules for all, rules for company1 and rules for company2. If I'm on the scope of All companies, I see all rules (that is how I would like it, so that is good) if I'm on the scope of company1, I currently see only the rules created in company1. I would love to see the rules in company1 and in all companies. That way, I have an overview of all rules that are applied to that company (they should be grouped or indicated on what level it's created)

We're revamping the AutoElevate agent dialog UI to better match modern Windows (especially Windows 11) — a cleaner, more current look for the prompts your end users see during elevation requests. This is actively in development and is the first step in a larger effort to modernize the agent experience. Taking shape A refreshed dialog design aligned with modern Windows styling A clearer, more polished experience for end users

We're planning to surface each machine's detected antivirus/security software directly on the Elevation Requests and Computers grids. When a request comes in, you'll see at a glance what AV is present on that endpoint — one less thing to look up in another tool while you triage.