Skip to main content

​
What this check does

DSALTA compares the account on the Pipedream Access page against your People directory, matched by email within your organization. It passes when the Pipedream account is an active employee on the People page.
This check also runs on 85 other integrations — see User access to Critical System should be valid for the full list.
Passes when: The connected Pipedream account is an active employee on the People page.

​
Why this matters

Access to the organization’s Pipedream account must belong to a current, authorized employee.

​
How to fix

Review Pipedream access
  1. In DSALTA, open Data Library → Access and filter to Pipedream — the single row shows the username and email of the account whose API key authorized the connection.
  2. Open People and confirm that email belongs to a current, active employee.
  3. If it does not, have a current employee copy their key from Settings → Account at pipedream.com/settings/account.
  4. In DSALTA, open Integrations → Connected, click Manage on the Pipedream card, and click Disconnect — this permanently deletes the data and tests already collected from Pipedream.
  5. On the Integrations page, click Connect on the Pipedream card and paste that key, so the Access row matches a person on your People page.
  6. In Pipedream, open Settings → Members and remove anyone who is no longer a current 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 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.