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

# Qdrant Cloud

> Managed vector database — members & access

<Tabs>
  <Tab title="Overview">
    Connect Qdrant Cloud with a Cloud Management Key to sync account members and clusters, 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 the members of one Qdrant Cloud **account** — the one with the lowest account ID among those the key can see. Qdrant's member record carries no display name, so each row shows the member's **email address** in place of a name, together with the date they were added and Qdrant's own active or inactive state. The account **Owner** is labelled as such; other members show the names of the roles assigned to them in User & Role Management, or **Member** when none is assigned. Pending invitations are not included. Qdrant reports no MFA state, so the **MFA** column shows **Unknown**.
    </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 Qdrant Cloud account member roster — email addresses, roles, join dates and account state — which appears on your **Access** page; and the account's **clusters**, which appear on your **Inventory** page with their cloud provider, region and state. Role names are looked up member by member, for the first 50 members of the account; any member beyond that is shown as **Member**, except the account owner, who is always shown as **Owner**.

    It calls these Qdrant Cloud endpoints:

    * `/api/account/v1/accounts`
    * `/api/account/v1/accounts/{id}/members`
    * `/api/iam/v1/accounts/{id}/users/{userId}/roles`
    * `/api/cluster/v1/accounts/{id}/clusters`

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

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        The key must be the full Cloud Management Key string, including the `|` separator between the key ID and the secret. A key that was deleted under **Cloud Management Keys**, or one whose account no longer exists, is rejected the same way. Create a new key and connect again.
      </Accordion>

      <Accordion title="A member shows Member instead of their real role">
        Role names come from a per-member lookup that covers the first 50 members. In a larger account the remaining members show **Member**. The role lookup also falls back to **Member** silently when Qdrant refuses it, so check the role in **User & Role Management** before acting on it.
      </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 Qdrant Cloud Management Key (the full `<key-id>|<secret>` string). The account is detected automatically. Read-only.

    **Before you begin**

    * A Qdrant Cloud account. Cloud Management Keys are created from **Access Management**, which account owners and admins can open.

    You will need:

    | Field                    | Where to find it                              | Example              |
    | ------------------------ | --------------------------------------------- | -------------------- |
    | **Cloud Management Key** | **Access Management → Cloud Management Keys** | `<key-id>\|<secret>` |

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

      <Step title="Create a Cloud Management Key">
        Sign in to [cloud.qdrant.io](https://cloud.qdrant.io), open **Access Management → Cloud Management Keys**, and create a key. Copy the **full** key string — it has the form `<key-id>|<secret>`, and both halves are needed.

        <Warning>
          A Cloud Management Key reaches every operation available to your account, not only reads, and Qdrant asks that it is never exposed in repositories or logs. Paste it only into the DSALTA connect panel.
        </Warning>

        <Info>
          These are not the database API keys you use to query a cluster. Cluster API keys cannot list members or clusters, and DSALTA does not accept them.
        </Info>
      </Step>

      <Step title="Connect Qdrant Cloud">
        Return to the connect panel, paste the full key string including the `|` separator, and click **Connect**. The account is detected automatically.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the key when you click **Connect**, by listing the accounts it can see. 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 key, a partial key without the `|` separator, or a key whose account is no longer visible.

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

  <Tab title="Useful links">
    | Topic       | Link                                                                                          |
    | ----------- | --------------------------------------------------------------------------------------------- |
    | Setup       | [Qdrant Cloud API and management keys](https://qdrant.tech/documentation/cloud-api/)          |
    | Remediation | [Qdrant Cloud user management](https://qdrant.tech/documentation/cloud-rbac/user-management/) |
    | General     | [Qdrant Cloud console](https://cloud.qdrant.io)                                               |
    | DSALTA      | [Connection error messages](/troubleshooting/connection-error-messages)                       |
  </Tab>
</Tabs>