> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accessowl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bitwarden

AccessOwl integrates with Bitwarden to provision and deprovision user access in your Bitwarden organization.

## Capabilities

<CardGroup cols={2}>
  <Card title="Provisioning" icon="user-plus">
    AccessOwl creates user accounts with the specified roles/permissions during access requests.
  </Card>

  <Card title="Deprovisioning" icon="user-minus">
    AccessOwl removes members from the Bitwarden organization during access revocations.
  </Card>
</CardGroup>

## Prerequisites

* **Admin** access to your Bitwarden organization, so you can invite the integration account.

## Setup

<Steps>
  <Step title="Add Bitwarden in AccessOwl">
    Either add a new application or open Applications and click the +-symbol, then continue.
  </Step>

  <Step title="Invite the integration account as Admin">
    AccessOwl shows you the integration account's email address. In Bitwarden:

    * Open the **Admin Console** and select **Members** from the sidebar.
    * Click **Invite member**.
    * Enter the integration account's email address.
    * Set the role to **Admin**.
    * Send the invite.

    <Note>
      The integration account needs Admin because only Admins (and Owners) can invite and confirm new members, and revoke or remove existing members from the organization. Without Admin, the integration account cannot provision or deprovision users.
    </Note>
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="The user was provisioned but I can't see them as an active member in Bitwarden">
    Bitwarden uses a three-step onboarding process: Invite, Accept, and Confirm. When AccessOwl provisions a user, it sends them an invitation email. The user only becomes a full member after they accept the invite and an Admin selects them in the Members list and clicks Confirm. Until both steps are complete, the user appears as Invited or Accepted but does not have access to shared organization items. Note that invitations expire after five days; if a user has not accepted by then, the integration account will need to re-invite them.
  </Accordion>
</AccordionGroup>