Skip to main content
Connect Unleash with your instance URL and an Admin service-account token to sync console users and projects, and run access reviews. Read-only. Works for Unleash cloud and self-hosted OSS alike.
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 of your Unleash instance with their name, email or username, root role (Admin, Editor or Viewer, or Member when Unleash reports none) and the date they were created. Service accounts are left out — Unleash keeps them on a separate endpoint. Unleash reports no account status or MFA state, so every user is shown as Active with MFA Unknown.
An Admin service-account token is required. Unleash’s user directory is only readable with the Admin root role; a service account with the Viewer or Editor role receives a 403, and SDK tokens from API access cannot call any admin endpoint.
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 Unleash user roster — names, emails, root roles and creation dates — which appears on your Access page; and your Unleash projects, which appear on your Inventory page with their health score, feature count and member count. Feature flags and their configurations are not read.It calls these Unleash admin endpoints on your instance URL:
  • /api/admin/user-admin
  • /api/admin/projects
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Unleash environment.

​
Troubleshooting

Three causes, in order of likelihood: the token is an SDK token from Access control → API access (it looks like *:development.…) rather than a service-account token; the service account has the Viewer or Editor role instead of Admin; or the Instance URL is missing the tenant path — for Unleash cloud it is https://<region>.app.getunleash.io/<tenant>, copied from the address bar.
Service-account tokens carry an expiry chosen at creation. Generate a new token for the service account, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Unleash.
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.