Bitwarden

Bitwarden

Corma governs Bitwarden membership: owners, admins and collection access, revocation on departure and the credential updates that may need to follow.

The Corma and Bitwarden integration brings your Bitwarden organization under Corma's identity governance, so IT and security teams know who can open which shared logins, who administers the vault, and what has to happen when someone leaves. Bitwarden is an open source password manager that businesses use to store, share and autofill logins across the organization.

Key takeaways

  • Bitwarden Teams and Enterprise plans are priced per user per month, and a revoked Bitwarden member no longer occupies a subscription seat.
  • Bitwarden grants access to shared logins per collection, with permissions ranging from View items to Manage collection, for members or groups.
  • Bitwarden recommends updating the credentials a removed member could access when misuse of cached data is a concern, since some clients keep a read-only copy for a short time.

Why does offboarding go further in a password manager?

Bitwarden has three default member roles, owner, admin and user, plus custom roles on Enterprise. Shared items live in collections, and each member or group receives a permission per collection, from View items to Manage collection. Bitwarden also distinguishes revoking a member, which is reversible and frees the seat, from removing them, after which they must re-join to regain access.

Removing the account is only part of the job. Offline devices cache a read-only copy of organization items, and some clients may keep it for a short time after removal, which is why Bitwarden advises to update the credentials the member had access to when cached data could be misused. In practice, the collections a person could open are also the list of passwords to review.

How Corma governs Bitwarden

  • Members, roles and groups in one view: every Bitwarden member with their role, next to the rest of your stack.
  • Revocation on departure: a departure in your HR system revokes the member in Bitwarden within the offboarding workflow, so the seat is freed and no orphaned account keeps a door open.
  • A human step for credentials: the IT workflow builder can keep an approval step in the flow, for example the collection owner confirming that shared passwords were updated.
  • Reviews of owners and admins: owners, admins and members with Manage collection rights go into access review campaigns.

Detail by topic: Bitwarden access management, Bitwarden licence management and Bitwarden cost management.

Frequently asked questions

How does Corma connect to Bitwarden?

Through a native API integration where Bitwarden allows it, or through Corma's browser-based agents, which work in the Bitwarden admin console the way an administrator would.

Does Corma replace Bitwarden Directory Connector or SCIM?

No. On Teams and Enterprise, Directory Connector and SCIM sync members and groups from your directory or identity provider. Corma works on top: it reviews who should keep access, handles roles and collections outside the directory, and documents every decision.

Where is Corma data hosted?

In France, on AWS infrastructure, with encryption in transit and at rest. Corma is ISO/IEC 27001:2022 certified and only requests the permissions it needs to manage access.

Want to know who can open your shared vaults today? Book a Corma demo.

Related Integrations

Check out other integrations that could help you on managing your software licences and accesses!