Integrations/JumpCloud
J

Control what your AI agents do in JumpCloud.

Let your team build AI agents for JumpCloud. Bollard AI controls what each one can do, area by area.

Request early accessSee how it works →
JJumpCloud
Directory Agent
Users Account areaOffReadFull use
Groups Account areaOffReadFull use
Devices Account areaOffReadFull use
Delete users and reset passwords
What agents can do

Set what each agent can do across your account.

Each area of JumpCloud, like users, groups, or devices, gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see that part of your account.
Read
Read-only
The agent can read users and groups in that area. It can't change anything.
Full use
Read and update
The agent can read and update user details in that area, like a job title.

Some actions stay off until explicitly turned on

Each one changes who can sign in or removes accounts for good, so it could override the limits set elsewhere.

Deleting usersResetting passwordsChanging group membership
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's JumpCloud a single time. Bollard AI lays out the areas of your account, and anything you don't allow stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead and update user details in a single area
Example

A directory admin agent.

A directory agent updates user details and can read your groups, but it can't delete a user or reset a password.

Users Account areaOffReadFull use
Groups Account areaOffReadFull use
Devices Account areaOffReadFull use

Manage access

ALLOWEDDirectory Agent updated a record in Users
ALLOWEDDirectory Agent read a Group
BLOCKEDDirectory Agent tried to open Devices, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and JumpCloud, so they never hold your JumpCloud keys and never reach JumpCloud directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to JumpCloud. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every area starts off-limits, and changing who can sign in is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your JumpCloud keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which user or group, and the decision. The record is readable and can't be edited after the fact.

Questions

JumpCloud, answered.

Does connecting JumpCloud hand Bollard AI your whole account?+
Only the areas you allow. An admin connects your JumpCloud, and you decide which areas, like users or groups, each agent can reach. Bollard AI doesn't browse or copy your account. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent delete users or reset passwords?+
Not unless you turn it on. Deleting users, resetting passwords, and changing group membership are held off by default, so an agent can update user details and read groups without ever changing who can sign in, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our JumpCloud keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches JumpCloud, and the blocked attempt lands in the activity record with the reason.
How do we connect JumpCloud?+
An admin connects the company's JumpCloud once. Bollard AI seals the connection and lays out the areas of your account to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in JumpCloud, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →