Skip to main content
You connect ThreatLocker once at the MSP level, then turn it on per agent. Setup takes a few minutes.
ThreatLocker uses a single API URL and key per MSP. Save them once and every agent that has ThreatLocker permissions can use them.

1. Find your API URL and key in ThreatLocker

1

Find your Portal API URL

In the ThreatLocker Portal, open the Help menu and look for ThreatLocker Access. Copy the API URL shown there exactly — it’s specific to your ThreatLocker instance, so don’t guess or reuse another MSP’s URL.
2

Create an API Auth Key

Go to the Administrators page and create an API User, then generate its Auth Key.
Copy the key somewhere safe once it’s generated — you won’t be able to view it again in ThreatLocker.

2. Add the credentials in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the ThreatLocker card, under Endpoint Security.
2

Save the API URL and key

Paste both values and click Save. Neo checks the key against your portal before storing it — a refused key fails the save with the reason, so a wrong instance letter or a geolocation restriction never saves as “Connected”. The Organization Mapping tab fills separately: check it a few minutes after the save, and again after the next nightly PSA sync.

3. Turn ThreatLocker on per agent

Each agent decides whether it uses ThreatLocker and which areas it can touch. Open the agent, go to its Tools & Settings tab, click Endpoint Security, and expand the ThreatLocker block.

Pick a preset

Read Only

Every area set to read only, and Agent Deployment off. The agent can look up computers, applications, policies, approval requests and the audit log, but never makes changes.

Helpdesk

Approval Requests and File Testing set to read and write, with technician approval on every write. Everything else read only, and Agent Deployment off. Fits a helpdesk agent resolving the “app is blocked” workflow.

IT Admin

Every area read and write. Approving or rejecting software, editing policies and file testing go through on their own; Computers, Applications and Organizations writes wait on a technician.

Full Automation

Maintenance mode, disabling protection and override codes still wait on a technician. Every other write goes through on its own, approving software and editing policies included.

Or set each area by hand

Safety controls

  • Technician approval is per area. Turn on Require Technician Approval for an area and every write there waits on a technician, approving software and editing policies included.
  • Maintenance mode, disabling protection and override codes always wait on a technician. Each stops a computer’s protection, so this holds whatever the agent’s settings.
  • The install key stays out of logs. An agent with Agent Deployment reads it for an install, but it never reaches the run log or a sandbox script.
  • Path safety. Suspicious URL paths (anything containing .., for example) are rejected before they reach ThreatLocker.

If ThreatLocker refuses Neo’s requests

ThreatLocker answers a refused request with an error message, and each one has a different fix. Match the most specific row first. Until it is fixed, agents that use ThreatLocker report the failure on the ticket they were working. Neo’s ThreatLocker organization mapping also stops refreshing if the refusal reaches the Organizations read it depends on — every Unauthorized does, and a Forbidden does only when that area is the one being refused. The rest of Neo keeps running.

If Neo sees no computers in your clients’ organizations

A computer read can succeed and still return only the computers in your own top-level organization. ThreatLocker includes child organizations only when the API user holds View Computers, Edit Computers or Install Computers. View Computers - Managed Organization Only limits the computer list to your own organization, even when the request asks for child organizations. Replace it with View Computers, the read-only one of the three; no change is needed in Neo.

Disconnecting ThreatLocker

1

Open the integration

In the Neo Dashboard, open Integrations and select the ThreatLocker card.
2

Disconnect

Click Disconnect and confirm. Neo removes the credentials from Key Vault.
Your Organization Mapping is kept, including any mapping you set by hand, so reconnecting later picks up where you left off. Agents that use ThreatLocker stop working until you connect it again.

Security

  • The API key lives in Azure Key Vault. It is never stored in plaintext.
  • All traffic to ThreatLocker goes over HTTPS, to the Portal API URL you saved for your instance.
  • Write access to ThreatLocker is opt in per area, per agent.
Once your credentials are saved and an agent has permissions, the ThreatLocker tool is added to that agent automatically.