Skip to main content
Checks that everyone with Cursor access is an active employee on the People page.

​
About

When you connect Cursor to DSALTA, the platform syncs the users on your Cursor Access page using read-only API access. On every sync DSALTA compares those users against your People directory, matched by email within your organization. The check passes when every Cursor user is an active employee on the People page.
With a standard User API key, Cursor returns only the connected account, so this match may cover just that one user. Connect with a Team Admin API key to review your full team roster.

​
Why This Matters

Access to the organization’s AI coding tooling must be limited to current, authorized employees. Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure the Cursor integration is connected so DSALTA has the current list of users.
Review Cursor access
  1. In the Cursor Dashboard, go to Settings → Members and remove anyone who is not a current employee.
  2. In DSALTA, open People and confirm each Cursor user exists and is active.
  3. In DSALTA, go to Data Library → Access and filter for Cursor to review each user against their current job function.
Once every Cursor user is an active, authorized employee, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Cursor integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once every Cursor user maps to an active employee, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Cursor.