> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vantage

> Cloud cost management — members & access

<Tabs>
  <Tab title="Overview">
    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.

    <Info>
      **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.
    </Info>

    <Info>
      **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).
    </Info>

    <Note>
      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.
    </Note>

    ## 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

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        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.
      </Accordion>

      <Accordion title="The connection stopped working">
        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.
      </Accordion>

      <Accordion title="Inventory shows no cloud accounts, or Changes is empty">
        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.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        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.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        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](/guides/compliance/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        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.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **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](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        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.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    A Vantage service token with the Read scope. Workspaces are detected automatically. Read-only.

    **Before you begin**

    * A Vantage account.
    * The **Organization Owner** or **Team Owner** role, which is needed to create service tokens.

    You will need:

    | Field | Where to find it | Example |
    | - | - | - |
    | **Service token** | **Settings** (top navigation) → **API Access Tokens** → **Service Tokens** tab → **Create** | Revealed with **Show** |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Vantage**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Open API Access Tokens">
        Sign in at [console.vantage.sh](https://console.vantage.sh) — you do not need to connect a cloud provider first. Open **Settings** in the top navigation, then **API Access Tokens** in the left navigation.
      </Step>

      <Step title="Create a read-only service token">
        Stay on the **Service Tokens** tab, not **Personal Access Tokens**: a personal token stops working when its owner leaves. Enter a name (for example `dsalta-access-sync`), tick only the **Read** scope, and click **Create**. On non-Enterprise plans the token automatically covers the whole organization; Enterprise accounts also choose a team.

        <Warning>
          **Tick Read only.** With the Write scope the same API can delete cost reports, teams and workspaces. DSALTA never needs it.
        </Warning>
      </Step>

      <Step title="Connect Vantage">
        Click **Show**, copy the token, return to the connect panel, paste it, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the token when you click **Connect**, by reading the token's own record to confirm it carries the **Read** scope and then listing your account members with it. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** An invalid or deleted token, or a token created without the Read scope.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check | Severity | What it verifies |
    | - | - | - |
    | [User access to Critical System should be valid](/integrations/vantage/user-access-to-critical-system-should-be-valid) | Info | Checks that everyone with Vantage access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/vantage/offboarded-users-should-not-have-active-access) | High | Checks that offboarded employees no longer have active Vantage access. |
  </Tab>

  <Tab title="Useful links">
    | Topic | Link |
    | - | - |
    | Setup | [Vantage API authentication](https://docs.vantage.sh/api/authentication) |
    | Remediation | [Vantage account settings](https://docs.vantage.sh/vantage_account) · [Audit logs](https://docs.vantage.sh/audit_logs) |
    | General | [Vantage console](https://console.vantage.sh) |
    | DSALTA | [Connection error messages](/troubleshooting/connection-error-messages) |
  </Tab>
</Tabs>