Connectors / Kandji
What Deixic does with Kandji.
Read and act
Review device details and help lock a departed employee’s device.
How Deixic helps with Kandji.
- Read information
- Review users and devices from Kandji as evidence and to check state.
- Choose the actions
- Deixic supports actions on devices. Grant only the tools and permissions the task needs.
- Keep your decisions
- Deixic checks your policy before a change; sensitive changes wait for a named approver. The action record keeps the decision and result.
1 of 1 changing operations require approval. See how approvals work.
Example workflow
Find and lock a departed employee’s device
Review the Kandji device inventory and match the departed employee’s device by identifier. Prepare a device-lock request for approval and check the device after the command.
- Confirm the departure in the HR system and match the device to the person using its assigned user and device identifier.
- Prepare the supported device-lock command for the named approver. Keep the device identifier and the approval reason with the job.
- After approval, send the lock command and read the device again. A queued command is not proof that an offline device has locked; keep verification open until the result is confirmed.
Check before you continue: Locking a device does not remove the person’s accounts in other systems. Review those accounts separately.
Provider reference: Kandji API documentation
Use your existing agent with Deixic. Calls you route through Deixic follow your access and approval policy.
Provider access
Supported Kandji reads and actions.
Choose the reads and actions your task needs. Your connection’s permissions and your agent’s access determine what it can use.
Read data
- Users Read
- Devices Read
Actions
- Devices Write
Permissions
Choose the access for Kandji.
Use a token issued for the account the agent should work in, check its owner, expiry, and resource access, and remember that replacing an expired token does not change the account’s permissions.
Find Kandji in the appManage connected accounts
- Connection
- Bearer token
- Supported operations
- Read and act
- Reads
- 2
- Actions
- 1
- Provider permissions
- Grant only the permissions needed for the task.
What you need to connect
- API base URL
- Bearer token
Deixic checks calls routed through its gateway and requests approval when your policy requires it.
Reference and troubleshooting
Connectors for related work
Tell us what you need from Kandji.
Bring one task. We’ll show you the access it needs and how Deixic helps.
Request early access