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

# Cursor

AccessOwl integrates with Cursor to provision and deprovision user access in your Cursor 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 members from the Cursor team during access revocations.
  </Card>
</CardGroup>

## Prerequisites

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

## Setup

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

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

    * Open your Cursor team's **Members** page.
    * Click **Invite Members**.
    * Enter the integration account's email address.
    * Set the role to **Unpaid Admin**.
    * Send the invite.

    <Note>
      The integration account is invited as Unpaid Admin so it doesn't consume a paid Cursor seat. Unpaid Admins can add and remove members and modify roles, without holding any Cursor Pro features. Your team needs at least one paid user for the Unpaid Admin role to be available.
    </Note>
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="The user was provisioned but I can't see them in Cursor">
    Cursor does not show pending invites in the team Members page. When AccessOwl provisions a user, the integration account sends them an invite email, but the user only appears in your Cursor Members list after they accept that invite. If a provisioning request shows as completed in AccessOwl but the user is not yet visible in Cursor, they haven't accepted the invite yet.
  </Accordion>
</AccordionGroup>