# Cursor

> Connect a Cursor Enterprise team key to LevelFour.

Source: https://docs.levelfour.ai/connectors/cursor


## Prerequisites

* Cursor Enterprise. Team and Pro plans cannot use the Admin API that this connector reads.
* A team admin, to create the API key.

## Connect

### Create a team API key in Cursor

In the Cursor dashboard, go to **API Keys > Team**, and create a new key. Cursor publishes no read-only admin scope, so the key is created with full admin access.

Copy the key (it starts with `crsr_`).

> **Warning**
>
> This key can also change spend limits, remove members, and edit model access. Create it on a dedicated identity, since Cursor offers no narrower scope.

### Add it to LevelFour

Open **Connect Providers**, select **Cursor**, and paste the key under **Team API key**. Click **Add Team API key**.

## Confirming it worked

The connection moves to **Connected**. Your first data appears within a day.

## Rotating or removing access

### Rotating the credential

Create a new team key in Cursor, paste it into **Connect Providers**, then revoke the old key from Cursor's **API Keys** page.

### Removing access

Disconnect Cursor under **Connect Providers**, then revoke the key from Cursor's **API Keys** page.

## Troubleshooting

| Symptom                                  | What to do                                                                                                                                                        |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The connection is refused outright       | Cursor's Admin API is Enterprise only. A Team or Pro plan key will not work, even if Cursor's dashboard lets you create one                                       |
| Spend looks low compared to your invoice | Seat subscription fees are not in this data. Only usage-based model spend is covered                                                                              |
| The key stops working unexpectedly       | Team keys belong to the organization, but a dashboard-level change to the creator's account can still affect them. Create a fresh key and check with a team admin |

## Next

* [Connect Providers](/connectors) lists every provider you can connect