Skip to main content

​
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.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Cursor account.
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.

​
How to Connect

Cursor connects with an API key — there’s no app to install.
1

Create a Cursor API key

For the full team roster, create an Admin API Key at 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.
2

Copy the key

Copy the key so you can paste it in the next step.
3

Connect

In the DSALTA sidebar, go to Integrations, find Cursor, and click Connect. Paste your API key in the secure window and submit.
4

Finish

DSALTA runs an initial sync — usually a few minutes — after which the compliance checks below activate.

​
Automated Compliance Checks

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

​
Troubleshooting

Re-authenticate from Integrations → Cursor → Reconnect. This can happen if the API key was revoked or rotated in the Cursor Dashboard.
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.