Skip to main content
Connect Vantage with a read-only service token to sync account members, workspaces, teams, connected cloud accounts, and the audit log, and run access reviews. Read-only. Data feeds into your Access accounts, Inventory and Changes pages.
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 your Vantage account — a service token is account-wide, so there is no workspace or account ID to choose. Each row shows the member’s name (or their email address when Vantage reports no name), their email, and their Vantage role as Vantage reports it (for example Owner, or Member when Vantage reports none). An invitation that was never accepted — a row with neither a name nor a last-seen date — is left out. Vantage reports no account status, so every member is shown as Active and stamped with the date of the sync. Vantage reports no per-user MFA state, so the MFA column is blank (shown as a dash).
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 Vantage account member roster — names, emails and roles — which appears on your Access page; your Vantage workspaces (currency and creation date), teams (member count, workspace count and description) and connected cloud accounts (provider, account identifier, status and last update), which appear on your Inventory page; and the account’s audit log, which appears on your Changes page. Each audit-log entry arrives as a change that has already happened — status Deployed, priority always Medium because Vantage attaches no severity to an audit-log entry, the event and the object it touched in the title, the actor, source, workspace and the names of the changed fields (never their values) in the description, and the workspace as the environment (or Vantage when the entry names none). The whole audit log is read, with no date window. The Changes page populates when Vantage has logged actions on the account. Connected cloud accounts appear once a cloud provider is connected in Vantage. Members’ last-seen dates are not synced.It calls these Vantage endpoints on api.vantage.sh/v2:
  • /me
  • /users
  • /workspaces
  • /teams
  • /integrations
  • /audit_logs
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Vantage environment.

​
Troubleshooting

The token was created without the Read scope — DSALTA checks the token’s scopes before reading any data — or it has been deleted in Vantage. Create a Service Token on Settings → API Access Tokens with the Read scope ticked and connect again. A Personal Access Token follows the user who created it and stops working when that user leaves, so prefer a service token.
The token was deleted, or it was a Personal Access Token whose owner left the account. Create a new service token, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Vantage.
Workspaces, teams, connected cloud accounts and the audit log are read best-effort after the member roster: a failure on one of those calls leaves that part of the page empty without failing the sync. Cloud account rows appear once a cloud provider is connected in Vantage, and the Changes page has rows once Vantage has logged actions on the account. Click Sync from integrations on the Integrations page to retry.
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.