Skip to main content
DSALTA connects to Cursor using read-only API access to collect compliance evidence automatically. Data 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.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Cursor user roster — names, emails and roles, which appears on your Access page.It calls these Cursor endpoints:
  • /teams/members
  • /v0/me
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Cursor environment.

​
Troubleshooting

There is no Reconnect button. Open Integrations → Connected, click Manage on the Cursor card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Cursor. 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 click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once. If only the connected account appears instead of your full team, reconnect with a Team Admin API Key.