Skip to main content
Connect Twingate with your network name and an Admin Console API token to sync users and protected resources, and run access reviews. Read-only.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists every user of your Twingate network with their name, email, Admin Console role and the date they were created, and respects Twingate’s own user state — a user Twingate reports as anything other than active (for example Pending or Disabled) is shown as Inactive. Twingate reports no MFA state through this query, so the MFA column shows Unknown. Devices are not synced.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Twingate user roster — names, emails, roles, state and creation dates — which appears on your Access page; and your Twingate Resources, which appear on your Inventory page with their address and whether they are active.It sends these GraphQL queries to https://<network>.twingate.com/api/graphql/:
  • users { … }
  • resources { … }
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Twingate environment.

​
Troubleshooting

The Network name must be the subdomain of your Admin Console URL — for acme.twingate.com enter acme — and the token must come from Settings → API in that network’s Admin Console. A token from another network, or a deleted token, is rejected the same way.
When Twingate is connected to an identity provider, users are synchronised from it and cannot be edited in the Admin Console. Remediation for those users happens in the identity provider; the Access page still shows them with the state Twingate reports.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.