Skip to main content
Connect Xata with a User API key to sync organization members and projects, 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 the members of one Xata organization — the first organization the key can see — with their name, email and organization role. Xata’s members endpoint does not always return a role; a member without one is shown as Member. Pending invitations are not included. Xata reports no account status, join date or MFA state, so every member is shown as Active with MFA Unknown, and each row is stamped with the date of the sync.
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 Xata organization member roster — names, emails and roles — which appears on your Access page; and the organization’s projects, which appear on your Inventory page with the project’s boolean settings and last-updated date.It calls these Xata endpoints on api.xata.tech:
  • /organizations
  • /organizations/{id}/members
  • /organizations/{id}/projects
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Xata environment.

​
Troubleshooting

The key must be a User API key (it starts with xau_) created under Account Settings → User API keys. A key created with Access control switched on but without the Organization scope cannot list members. Create a new key and connect again.
When the key can see several organizations, DSALTA syncs the first by ID and there is no field to pin another. Create the key as a user who belongs only to the organization you want reviewed, or scope the key to that organization with Access control, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Xata.
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.