Skip to main content
Connect New Relic with a User API key to sync the users of your organization’s authentication domains and your accounts, 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 in every authentication domain of your New Relic organization, with their name, email and user type (Basic user, Core user or Full platform user) shown in the role column. New Relic exposes no account status, join date or MFA state through this query, so every user is shown as Active with MFA Unknown, and each row is stamped with the date of the sync.
A User key is required. License, Ingest and Browser keys authenticate data ingest only; New Relic’s NerdGraph API rejects them, and so does DSALTA at connect time.
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 New Relic user roster — names, emails and user types across all authentication domains — which appears on your Access page; and your New Relic accounts, which appear on your Inventory page by name and ID. Telemetry, entities and alerts are not read.It sends these NerdGraph queries to api.newrelic.com/graphql (or api.eu.newrelic.com/graphql for EU-region accounts):
  • actor { user { … } } — the key’s own user, used to validate
  • actor { organization { userManagement { authenticationDomains { users … } } } }
  • actor { accounts { … } }
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your New Relic environment.

​
Troubleshooting

The key is not a User key (it should start with NRAK-), it was deleted, or the Region is wrong — an EU-region key sent to the US endpoint fails. Create a User key, check the region, and connect again.
User keys inherit their owner’s permissions. Listing users requires the key’s owner to hold an organization-scoped role with authentication domain management permissions, such as Authentication domain manager or Organization manager. Create the key as such a user, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from New Relic.
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.