Cursor
Connect Cursor as an access review source using a Read-only team Admin API key so the platform can list your team's members and their roles.
the platform reads your Cursor team’s members through the Cursor Admin API so you can review who has access.
Prerequisites
Section titled “Prerequisites”- the platform organization administrator access
- The team administrator role in Cursor (only team administrators can create and manage Admin API keys)
- A Cursor team on a paid Business plan (the Admin API is not available on individual accounts)
Collected Fields
Section titled “Collected Fields”| the platform field | Cursor field | Notes |
|---|---|---|
| Name | name | Member display name |
email | Member email address | |
| Role | role | owner and free-owner map to Owner, member to Member, removed to Removed; any other value passes through unchanged |
| Admin | role | Flagged as an administrator when role is owner or free-owner |
| Status | isRemoved, role | Shown inactive when isRemoved is true or role is removed, otherwise active |
| MFA | Not supported | |
| Last login | Not supported | |
| External ID | id | Stable identifier used to track the account across reviews |
| Created at | Not supported |
Step 1: Create an API Key
Section titled “Step 1: Create an API Key”- In Cursor (signed in as a team administrator), open
cursor.com/dashboard, go to Settings, and select API Keys in the sidebar. - Open the Team tab and click New API Key.
- Enter a name (e.g.
Probo Access Review), choose an expiration date, and set Scope to Read-only. - Create and copy the key (
crsr_…), then store it securely. It’s shown only once.
Step 2: Connect in the platform
Section titled “Step 2: Connect in the platform”- In the platform, go to Access Reviews > Sources > Add Source.
- Find Cursor, click API Key, paste the key, and click Connect.
The Admin API exposes no team or organization name endpoint, so the platform lists the source under the fixed name Cursor and pulls its members into your campaigns.
Troubleshooting
Section titled “Troubleshooting”- Key rejected. Confirm it’s a team API key (
crsr_…) with the Read-only scope, created by a team administrator. A personal User API Key won’t work, and because the Admin API accepts only Basic auth, Bearer tokens are rejected. - No members appear. The key must be created by a team administrator and belong to the team you’re reviewing on a paid Business plan.