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

# Float

AccessOwl integrates with Float to provision and deprovision user access in your Float team.

## 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 account access for people in your Float team during access revocations.
  </Card>
</CardGroup>

## Prerequisites

* **Admin** access to your Float team, so you can invite the integration account.

## Setup

<Steps>
  <Step title="Add Float 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 Float:

    * Click the **+** in the top-right corner and select **Add person**.
    * Enter the integration account's details.
    * Open the **Access** tab on the new person's profile.
    * Enter the integration account's email address.
    * Set the access rights to **Admin**.
    * Click **Update & invite person**.

    <Note>
      The integration account needs Admin access because it has to invite people and remove their account access on your behalf.
    </Note>
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="What does deprovisioning do to a person in Float?">
    Float separates a *person* (who appears on the schedule) from their *account access* (the ability to log in). When AccessOwl deprovisions a user, it removes their account access so they can no longer log in. The person stays on your schedule unless you archive them separately in Float.
  </Accordion>
</AccordionGroup>