Integrations/CyberFOX AutoElevate
SECURITY INTEGRATION

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. Then it approves or denies, with a technician's sign-off or on its own, as you choose.

01Capabilities

What Neo does with CyberFOX AutoElevate.

01
REQUESTS

The request behind the ticket

Neo finds the pending elevation request for the ticket's client and reads its state. It approves or denies, and you choose per agent whether a technician signs off first.

02
EVIDENCE

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.

03
CONTEXT

Computers, sessions and rules

Neo reads managed computers, elevated admin sessions, and the auto-approval and auto-denial rules with their scope. Neo creates a rule only with a decision, and only where you allow it.

02Workflows

Concrete work Neo handles in CyberFOX AutoElevate.

ADMIN RIGHTS

"I need admin rights to install this"

Neo finds the request, checks the file and publisher, and approves or denies it from the ticket, or hands the decision to a technician. Nobody opens the AutoElevate portal.

QUEUE

Pending requests, watched

An agent watches for pending requests and decides them with the evidence already checked, after hours included, or hands a technician a ready decision.

RULE CHECK

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.

AUDIT

Who had admin on this machine

Neo reads elevated sessions: who held one, when it started and how long it was scheduled for.

03Setup

Live in under an hour.

Connect, configure, go. No code, no long implementation.

01

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.

02

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.

03

Set access per agent

Pick Read Only, Helpdesk to decide requests with a technician's sign-off, IT Admin to decide them alone, or Full Automation. Neo adds the AutoElevate tool to every agent you enable.

FAQ

Questions about the CyberFOX AutoElevate integration.

What can Neo change in AutoElevate?+

It can approve or deny a pending elevation request, and create an auto-approval or auto-denial rule with that decision when you allow it. Computers, companies and locations are read only, because the AutoElevate API has no write for them.

Does every decision need a technician?+

Only if you want it to. Each agent's approval settings decide it: Helpdesk asks on every decision, IT Admin decides alone but asks before it creates a rule, and Full Automation asks on nothing.

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.