Skip to main content
Connect Copper with an API key to sync account users and run access reviews. Read-only; the key is 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 your Copper account users — name and email address, which is what Copper’s admin API returns for a user — and those appear on your Access page. Copper is a CRM, so the Companies, People, Opportunities and Leads it holds are your own customer and prospect data rather than infrastructure, and nothing is synced to Inventory, Incidents or Changes. People is your own DSALTA directory, which the access reviews below match Copper users against by email.It calls these Copper endpoints:
  • /v1/account
  • /v1/users/search
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Copper environment.

​
Troubleshooting

Copper’s user object carries no status field, so every user Copper returns is recorded as Active. Remove the person in Copper itself, then run Sync from integrations — the row leaves the Access page once Copper stops returning them.
The API key is invalid or revoked, or the email address entered does not belong to the Copper user the key was generated for. Copper authenticates the key and the address together.
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.