Assign enrollment and evidence follow-ups
Connect
SPIRITT
JumpCloudJumpCloud
Onboard with control
SPIRITT turns JumpCloud enrollment guidance into working IT handoffs and validates the credentials behind them. For role retirement, it permanently deletes explicitly authorized custom roles by exact ID and records the results.
What you can do with JumpCloud.
Accountable enrollment
Give technicians clear enrollment instructions, assigned devices, and a place to record completion evidence against your onboarding checklist.
Controlled retirement
Tie each permanent custom role deletion to an exact ID, explicit authorization, and a recorded result so retirement decisions stay traceable.
Better IT decisions
Combine supplied rosters, technician confirmations, and work records to plan enrollment capacity and identify recurring process failures.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for device enrollment coordination, credential readiness, or controlled custom role retirement.
02
Connect JumpCloud
Connect JumpCloud with an API key authorized for your mission. Add the roster, IT procedures, or exact custom role IDs the work requires.
03
Delegate an outcome
Ask SPIRITT to build an enrollment desk or retire an explicitly authorized list of custom roles. It runs the workflow and records the outcomes.
Hand over a mission.
Choose a mission. Make it yours.
Put JumpCloud to work.
Make IT handoffs accountable
Questions
JumpCloud, with SPIRITT.
01Which JumpCloud actions can SPIRITT perform?+
This connection validates credentials, provides system enrollment guidance, and permanently deletes a specified custom role by ID. SPIRITT can build software and operate connected workflows around those actions. The available operations do not include reading directory inventory, provisioning users, or administering devices.
02Does enrollment guidance mean SPIRITT enrolls devices directly?+
No. The system operation provides guidance and credential validation, not direct system creation or enrollment. SPIRITT can organize technician tasks and collect their completion evidence. A technician-confirmed status in an enrollment desk is distinct from a device status read directly from JumpCloud.
03What access and source records does a mission need?+
Connect an API key authorized for the intended operation. Enrollment coordination needs your roster, owners, and local procedures. Role retirement needs exact custom role IDs, dependency review evidence, and explicit deletion authorization because this connection cannot list roles or inspect their assignments.
04Can SPIRITT retire built-in roles or undo a deletion?+
Custom role deletion is permanent, not an archive operation, and does not apply to built-in roles. SPIRITT can execute an explicitly authorized list of exact custom role IDs and retain each result. Role retirement should follow your dependency review; deleting a role is not proof that a broader offboarding process is complete.
05How can this work with our existing IT tools?+
SPIRITT can use a Google Sheets roster to plan enrollment handoffs, assign work in Asana or Jira, and coordinate technicians through Slack. Scheduled credential checks can feed incident workflows, while Google Drive can hold retirement authorizations and recorded deletion outcomes.
06What does a custom enrollment desk add beyond JumpCloud administration?+
It adds intake forms, assigned handoffs, evidence collection, and readiness views around your procedures and supplied records. SPIRITT can also build manifest validation tools and technician training. These systems coordinate the surrounding work rather than replacing JumpCloud's directory or device administration.