Skip to main content

​
What this check does

DSALTA matches each user with active Hugging Face access to your People directory by username, because Hugging Face keeps member email addresses private. If a matched person is offboarded (terminated or in offboarding) but still has active access, the check flags it as a serious issue.
This check also runs on 112 other integrations — see Offboarded users should not have active access for the full list.
Matching is by username: a member is only recognised as offboarded when their Hugging Face username matches the username on their People record or the start of their email address.
Passes when: No offboarded employee retains active Hugging Face access.

​
Why this matters

Offboarded employees must not retain access to the organization’s machine-learning hub.

​
How to fix

Remove offboarded members from Hugging Face
  1. Sign in to huggingface.co as an organization admin.
  2. Open the organization’s page, go to Organization settings → Members, and find each offboarded employee by username.
  3. Revoke their membership. If your organization uses Managed SSO with SCIM, remove the person in the identity provider instead.
  4. The person’s own access tokens lose the organization’s resources with the membership; on Enterprise plans you can additionally revoke tokens scoped to the organization from the token management settings.
  5. In DSALTA, go to People and confirm each of those employees is marked terminated with an end date.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.