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

# Qase

> Test management — users & access

<Tabs>
  <Tab title="Overview">
    Connect Qase with an API token to sync workspace users and projects, and run access reviews. Read-only.

    <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 every **user** of your Qase workspace with their name, email and the job title Qase stores for them, which appears in the role column. Qase's own status is respected — a user Qase reports as inactive is shown as **Inactive**. Qase reports no join date or MFA state, so the **MFA** column shows **Unknown** and each row is stamped with the date of the sync.
    </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 Qase workspace user roster — names, emails, titles and status — which appears on your **Access** page; and your Qase **projects**, which appear on your **Inventory** page with their counts of test cases, suites, runs and defects. Test cases and results themselves are not read.

    It calls these Qase endpoints:

    * `/v1/user`
    * `/v1/project`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Qase environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        The token is invalid or was revoked, or it belongs to a user whose role cannot list workspace users — DSALTA refuses to connect when Qase returns no users at all. Create a token as a workspace owner or admin and connect again.
      </Accordion>

      <Accordion title="The role column shows job titles">
        Qase's users endpoint returns each person's title, not their workspace role, so DSALTA shows the title. Check the actual role under the workspace's **Users** settings when you review.
      </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 Qase API token. Syncs workspace users and projects. Read-only.

    **Before you begin**

    * A Qase workspace, and a user in it who can see all workspace users — the token acts as that user, so a workspace owner or admin is the safe choice.

    You will need:

    | Field         | Where to find it        | Example          |
    | ------------- | ----------------------- | ---------------- |
    | **API Token** | Avatar → **API Tokens** | Created per user |

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

      <Step title="Create an API token">
        Sign in to [app.qase.io](https://app.qase.io), click your avatar, choose **API Tokens**, and create a token. Copy it.

        <Info>
          The token carries your own workspace permissions. If you create it as a member with limited visibility, the Access page will be limited the same way.
        </Info>
      </Step>

      <Step title="Connect Qase">
        Return to the connect panel, paste the token, and click **Connect**.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the token when you click **Connect**, by listing the workspace's users — a token that authenticates but sees no users is rejected. 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.** Invalid or revoked token, or a token whose user cannot see any workspace users.

      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/qase/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Qase access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/qase/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Qase access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                      |
    | ------- | ------------------------------------------------------------------------- |
    | Setup   | [Qase API authentication](https://developers.qase.io/docs/authentication) |
    | General | [Qase](https://app.qase.io)                                               |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)   |
  </Tab>
</Tabs>