Skip to main content

​
What this check does

DSALTA compares the accounts on the Twilio Access page against your People directory, matched by email within your organization. It passes when every Twilio account maps to 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: Every Twilio account maps to an active employee on the People page.

​
Why this matters

Access to the organization’s Twilio account must be limited to current, authorized employees.

​
How to fix

Review Twilio Console access
  1. Sign in to the Twilio Console with a user that holds the Administrator role.
  2. Open the Admin menu and choose Users to list everyone who can sign in to your organization and its managed accounts.
  3. In DSALTA, open Data Library → Access (or this test’s Source Data tab) to see which Twilio users have no matching active employee.
  4. For anyone who is not a current employee, click their name and choose Remove user at the bottom of their profile.
  5. For users who still belong but hold more access than they need, open Account → Manage users, click the user, and select Developer, Support, or Billing Manager instead of Administrator, then click Save — to downgrade an existing Administrator you must disable that role and confirm first.
  6. In DSALTA → People, confirm each remaining Twilio user exists and is Active.
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.