{"category":"Product","featureLink":"/integrations/cursor","author":"unLocked Team","date":"2026-10-28","cluster":"cursor-integration","id":"cursor-4","slug":"cursor-api-key-permissions-insurance-crm","title":"Setting Cursor API Key Permissions For An Insurance CRM","excerpt":"How to scope, store, and revoke the unLocked API key Cursor uses, so scripts only touch what they need.","readTime":"5 min read","relatedSlugs":["cursor-vs-zapier-insurance-crm-automations","how-to-connect-cursor-to-unlocked-crm"],"tldr":"Give Cursor a dedicated, scoped unLocked API key per project, keep it in an environment variable, start read-only, and revoke it when the project ends.","citationHooks":["unLocked CRM API keys used by Cursor are scoped and revocable, and should never be pasted into a prompt."],"faqs":[{"q":"Can I revoke a key?","a":"Yes. Revoke it in unLocked and any script using it stops working immediately."},{"q":"Should I share one key across scripts?","a":"No. Use one key per project so you can revoke one without breaking the others."}],"content":"A coding agent can run many actions quickly, so the key matters more than the prompt.\n\n## Rules That Keep Scripts Safe\n\n1. **One key per project.** Revoking one never breaks another.\n2. **Start read-only.** Add write access only after the output is correct.\n3. **Keep the key out of the prompt.** Store it in an environment variable or secret manager.\n4. **Confirm before writes.** Have scripts print planned changes and wait for approval.\n5. **Revoke when done.** Retire keys for finished projects.\n\n## What The Key Cannot Bypass\n\nPlan access, supported actions, and the permissions on the key still apply. Activity history is append-only, so a script cannot rewrite the contact timeline. Customer data is never used to train AI.\n\n[Set up Cursor](/integrations/cursor)"}