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

# Bitwarden

> How DSALTA integrates with Bitwarden — data collected, setup guide, and automated compliance checks.

## Overview

DSALTA connects to Bitwarden using read-only API access to collect compliance evidence automatically. Data syncs every 24 hours and feeds into your Data Library modules.

DSALTA authenticates with a Bitwarden **organization API key** against the Bitwarden Public API and syncs your organization **members** for access reviews.

<Info>
  **Read-only access.** DSALTA never modifies, creates, or deletes resources in your Bitwarden organization — it only reads your members for access reviews.
</Info>

## How to Connect

Bitwarden connects with your **organization API key** (a `client_id` and `client_secret`) — there's no app to install.

<Steps>
  <Step title="Understand what connecting means">
    Integrating Bitwarden with DSALTA means DSALTA will only be able to **read** your Bitwarden organization members for access reviews. It never modifies your vault or settings.
  </Step>

  <Step title="Get your organization API key">
    In Bitwarden, go to **Admin Console → Settings → Organization info → View API Key**. Copy the **client\_id** and **client\_secret**.
  </Step>

  <Step title="Connect">
    In the DSALTA sidebar, go to **Integrations**, find **Bitwarden**, and click **Connect**. Paste the **client\_id** and **client\_secret** into the secure window. If your organization is hosted in the EU, set the **region** to `eu` (otherwise leave it as `us`), then submit.
  </Step>

  <Step title="Finish">
    DSALTA exchanges your API key for a token and lists your organization members. After the initial sync completes, the compliance checks below activate.
  </Step>
</Steps>

## Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

| Check                                                                                                                    | Description                                                                          |
| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| [User access to Critical System should be valid](/integrations/bitwarden/user-access-to-critical-system-should-be-valid) | Checks that everyone with Bitwarden access is an active employee on the People page. |
| [Offboarded users should not have active access](/integrations/bitwarden/offboarded-users-should-not-have-active-access) | Checks that offboarded employees no longer have active Bitwarden access.             |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Integration shows Disconnected">
    Re-authenticate from **Integrations → Bitwarden → Reconnect**. This usually happens when the organization API key was rotated in Bitwarden. Generate a new **client\_id** and **client\_secret** under **Admin Console → Settings → Organization info → View API Key** and paste them again.
  </Accordion>

  <Accordion title="Data is not syncing">
    Confirm the **client\_id** and **client\_secret** are current and that the **region** matches where your organization is hosted (`us` or `eu`). Then trigger a manual sync from the integration settings.
  </Accordion>
</AccordionGroup>