Skip to main content
Connect Attio via OAuth to sync workspace members and run access reviews. Read-only; tokens are held by Nango.
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.
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 Attio workspace member list — first and last name, email address, access level and creation date — which appears on your Access page, where the access level is used as the role and every row is recorded as a Human account. Attio is a CRM, so its records are your own customer and deal data rather than infrastructure, and nothing is synced to Inventory, Incidents or Changes. People is your own DSALTA directory, which the checks below read to match members by email.It calls this Attio endpoint:
  • /v2/workspace_members
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Attio environment.

​
Troubleshooting

Attio’s workspace member object carries no status field. Removing someone from the workspace takes them off the member list, and their Access row clears at the next sync.
DSALTA validates by listing workspace members. Authorize again with an Attio account that has permission to view the workspace’s members.
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.