Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks that offboarded users no longer have active JumpCloud access.

​
Why This Matters

Former employees retaining active access represents one of the most common and dangerous security gaps. Departed staff may still have credentials to sensitive systems, creating risk of unauthorized data access, intellectual property theft, or accidental modifications. Compliance frameworks including SOC 2, ISO 27001, and GDPR require timely access revocation upon termination.

​
What DSALTA Checks

DSALTA connects to your JumpCloud environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → JumpCloud.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Identify all offboarded employees by cross-referencing your HRMS (or DSALTA People module) with active JumpCloud accounts.
  2. For each offboarded user, disable or delete their account in JumpCloud.
  3. Revoke any API keys, access tokens, or service credentials associated with the departed user.
  4. Remove the user from all groups, roles, and shared resources.
  5. Document the offboarding action with the date and person who performed it.
  6. Set up automated offboarding workflows by connecting your HRMS to DSALTA — when an employee status changes to “Offboarded,” DSALTA flags any remaining active access.
  7. Once resolved, DSALTA will detect the change on the next sync cycle and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the JumpCloud integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in JumpCloud.