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

# Ashby

AccessOwl integrates with Ashby to provision and deprovision user access in your Ashby 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 deactivates users in Ashby during access revocations.
  </Card>
</CardGroup>

## Prerequisites

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

## Setup

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

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

    * Go to **Admin** > **Organization Setup** > **Employees**.
    * Click **New**, enter the integration account's name and email address, then click **Create**.
    * On the newly created profile, click **Actions** and select **Activate**.
    * Open the **Permissions** tab and set the global access role to **Organization Admin**.

    <Note>
      The integration account needs Organization Admin access because only Organization Admins can activate accounts, deactivate users, and manage access roles in Ashby.
    </Note>
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="What is the difference between deactivating and terminating a user in Ashby?">
    Ashby offers two ways to remove access. Deactivating a user is intended for employees who are still at the company but should no longer have Ashby access. Terminating a user removes all access roles and is intended for employees who have left the organization. AccessOwl uses deactivation during access revocations. Note that deactivating a user does not remove them from already-scheduled interviews, so manual rescheduling may be required.
  </Accordion>
</AccordionGroup>