Skip to main content

​
What this check does

DSALTA compares every Supervisely team member on the Access page against your People directory, matching each one by email address. Pending invitations that never signed in are not compared. A member whose Supervisely account carries no email is listed by login; DSALTA then tries that login against People usernames and the part of each email before the @, and records a member it still cannot place as having no matching person. A user with no matching person, or whose person is terminated or offboarding, is recorded with the reason.
This check also runs on 144 other integrations — see User access to Critical System should be valid for the full list.
A member whose Supervisely account carries no email address is listed by login. DSALTA then tries that login against the usernames and email local parts on the People page; when nothing matches, the member is recorded as having no matching person.
Passes when: Every user on the Supervisely Access page matches a person on the People page whose status is current and who is not in offboarding. An Access page with no synced Supervisely users passes.

​
Why this matters

Access to the organization’s Supervisely team, which holds its labeling projects and the images and annotations that train its models, must be limited to current, authorized employees. An account on the Supervisely Access page that belongs to nobody on the People page, or to someone who has already left, is access that no one is accountable for.

​
How to fix

Review Supervisely team access
  1. Sign in at app.supervisely.com (or your Enterprise instance) as an admin of the team.
  2. Open the team, then Team → Members. Each row is one team member.
  3. Compare every member against your current employee roster, paying attention to any address on an external domain. Annotator accounts may be external contractors; review them too.
  4. Remove anyone who is not a current employee.
  5. In DSALTA, go to People and confirm every remaining Supervisely member maps to an active employee.
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 Compliance → 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 Compliance → 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.