Skip to main content
Connect Neon with an 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 Neon organization — the organization DSALTA resolves from the key (see How to connect). Neon’s members endpoint returns no display name, so each row shows the member’s email address in place of a name, with their organization role and the date they joined. Neon reports no account status, so every member is shown as Active. Neon does report per-member MFA, so the MFA column shows Yes or No, and Unknown for a member whose record carries no MFA value.
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 Neon organization member roster — email addresses, roles, join dates and MFA status — which appears on your Access page; and the organization’s Neon projects, which appear on your Inventory page with their region, Postgres version, IP allowlist size, whether public or VPC connections are blocked, HIPAA status and maintenance window.It calls these Neon endpoints:
  • /api/v2/users/me/organizations
  • /api/v2/organizations/{id}/members
  • /api/v2/projects?org_id={id}
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Neon environment.

​
Troubleshooting

When the key can see more than one organization and no Organization ID was entered at connect time, DSALTA syncs the organization with the lowest ID. To pin a different one, disconnect, then connect again with the Organization ID field filled in (Neon shows it under Organization settings → General). Note that disconnecting permanently deletes the data already collected from Neon.
The key is invalid or revoked, or an Organization ID was entered that the key cannot see. A personal key only sees organizations the key’s owner belongs to.
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.