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

# Cursor

> How DSALTA integrates with Cursor — data collected, setup guide, and automated compliance checks.

## Overview

DSALTA connects to Cursor using read-only API access to collect compliance evidence automatically. Data syncs every 24 hours and feeds into your Data Library modules.

<Info>
  **Read-only access.** DSALTA never modifies, creates, or deletes resources in your Cursor account.
</Info>

<Note>
  **What you'll see.** With a **Team Admin API key**, DSALTA's Access page lists your Cursor team members (by name and email). With a standard **User API key**, Cursor only returns the connected account, so the Access page shows a single row — the key's owner — rather than your full roster. In that case the access checks below, which match Cursor users to your People page by email, may not resolve for the rest of your team. To review your whole team, connect with a Team Admin key.
</Note>

## How to Connect

Cursor connects with an **API key** — there's no app to install.

<Steps>
  <Step title="Create a Cursor API key">
    For the full team roster, create an **Admin API Key** at [cursor.com/dashboard](https://cursor.com/dashboard), then **Settings → Advanced → Admin API Keys** (this requires a Business plan and team admin). Otherwise, a standard **User API Key** (**Dashboard → API Keys**) still connects and shows the connected account.
  </Step>

  <Step title="Copy the key">
    Copy the key so you can paste it in the next step.
  </Step>

  <Step title="Connect">
    In the DSALTA sidebar, go to **Integrations**, find **Cursor**, and click **Connect**. Paste your API key in the secure window and submit.
  </Step>

  <Step title="Finish">
    DSALTA runs an initial sync — usually a few minutes — after which the compliance checks below activate.
  </Step>
</Steps>

## Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

| Check                                                                                                                 | Description                                                                       |
| --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| [User access to Critical System should be valid](/integrations/cursor/user-access-to-critical-system-should-be-valid) | Checks that everyone with Cursor access is an active employee on the People page. |
| [Offboarded users should not have active access](/integrations/cursor/offboarded-users-should-not-have-active-access) | Checks that offboarded employees no longer have active Cursor access.             |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Integration shows Disconnected">
    Re-authenticate from **Integrations → Cursor → Reconnect**. This can happen if the API key was revoked or rotated in the Cursor Dashboard.
  </Accordion>

  <Accordion title="Data is not syncing">
    Confirm the API key is still valid in the Cursor Dashboard, then trigger a manual sync from the integration settings. If only the connected account appears instead of your full team, reconnect with a **Team Admin API Key**.
  </Accordion>
</AccordionGroup>