Admin rights requests, decided from the ticket.
Neo pulls the AutoElevate elevation request onto the ticket and reads the file, publisher and user behind it. A technician signs off on every approve or deny.
What Neo does with CyberFOX AutoElevate.
The request behind the ticket
Neo finds the pending elevation request for the ticket's client and reads its state. It approves or denies only after a technician signs off.
What the user wants to run
Neo reads the matching elevation event: file name and path, hashes, signature state, publisher, signing certificate and the user who ran it.
Computers, sessions and rules
Neo reads managed computers, elevated admin sessions, and the auto-approval and auto-denial rules with their scope. These areas are read only.
Concrete work Neo handles in CyberFOX AutoElevate.
"I need admin rights to install this"
Neo finds the request, checks the file and publisher, and prepares the decision. The technician approves or denies from the ticket, without the AutoElevate portal.
Pending requests, watched
An agent watches for pending requests and hands a technician a ready decision, with the evidence already checked.
Existing rules, checked first
Neo reads the auto-approval and auto-denial rules that may already cover the software, and the scope each rule applies at.
Who had admin on this machine
Neo reads elevated sessions: who held one, when it started and how long it was scheduled for.
Live in under an hour.
Connect, configure, go. No code, no long implementation.
Connect AutoElevate
Add an API key to a service user in AutoElevate with the API Token (AE-BEARER) scheme. Grant companyView, the view scopes your agents need, and requestEdit to decide requests. Neo checks the key before it saves.
Check the company mapping
Neo matches your AutoElevate companies to your PSA companies by name. Confirm AI suggestions or set a mapping by hand on the Organization Mapping tab.
Set access per agent
Pick Read Only, or Helpdesk to let the agent decide requests with a technician's sign-off. Neo adds the AutoElevate tool to every agent you enable.
Questions about the CyberFOX AutoElevate integration.
What can Neo change in AutoElevate?+
Only one thing: it can approve or deny a pending elevation request. Rules, computers, companies and locations are read only, because the AutoElevate API has no write for them.
Does every decision need a technician?+
Yes. Approving and denying always wait on a technician, and there is no Full Automation profile. Neo also leaves auto-approval and auto-denial rules off unless a technician asks for one.
What credentials does Neo need?+
An AutoElevate API key with the API Token (AE-BEARER) scheme. Its value starts with aeb_. Keys with the HMAC scheme do not work with Neo.
How are AutoElevate companies mapped to PSA companies?+
By company name: an exact match first, then a match without a legal suffix such as Inc or LLC, then an AI match. An AI match waits on the Organization Mapping tab until someone confirms it.
Ready to wire up CyberFOX AutoElevate?
14-day free trial. No credit card. Live in under an hour, right inside your stack.