Skip to main content

​
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.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Bitwarden organization — it only reads your members for access reviews.

​
How to Connect

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

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

Get your organization API key

In Bitwarden, go to Admin Console → Settings → Organization info → View API Key. Copy the client_id and client_secret.
3

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

Finish

DSALTA exchanges your API key for a token and lists your organization members. After the initial sync completes, the compliance checks below activate.

​
Automated Compliance Checks

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

​
Troubleshooting

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