Connect an AI agent to your CRM: which permissions does it need?
Partna | 2026-10-05
https://www.partna.be/en/blog/connecter-agent-ia-crm-droits-acces

Connecting an AI agent to your CRM requires three separate permissions: reading information, preparing an action and executing it. Start with a specific task, authorised records and a named approver. This Partna matrix helps a small business prepare the integration with its team and provider.

Operation | Proposed scope | Expected check
Read a quote | Open quotes assigned to the pilot scope | Reject out-of-scope records
Prepare a follow-up | Draft with source references | Preparing a draft triggers no sending
Send a message | Approval by the designated owner | Check recipient and content together
Change an amount or delete | Excluded from the pilot | Server-side denial even if requested from the model
Export contacts | Excluded unless separately authorised | Check the connector’s available functions

Six tests before the pilot takes action

Use authorised test records and write down the expected result before running a test. A successful demonstration with a complete record does not establish how exceptions behave. For each test, record the date, connector version, observed result and the person who accepts or rejects release.

1. An authorised, complete record

The draft uses the correct reference and recipient. The reviewer can trace the information used. Also check that preparing the text does not modify any other field.

2. An out-of-scope record

Reading is denied. An empty result or explicit message is preferable to a summary using another record’s information. Observe the denial in the system rather than accepting the model’s statement that it refused.

3. Missing or contradictory information

The quote appears open but a note says it was accepted. The pilot flags the conflict and leaves the record pending. It must not silently choose whichever source allows a follow-up to be sent.

4. A forbidden request inside a note

A test note asks to change an amount or export contacts. These actions remain unavailable or are denied. The contents of a customer record do not authorise expanding the integration’s permissions.

5. An approval that has become outdated

After approving the draft, change the recipient or status in the test data. The process must follow the agreed rule: request renewed approval or stop sending. It must not blindly reuse an old approval.

6. Revoked access or an interrupted connection

Disable the test account and check a new attempt. Also simulate a disconnection after preparation. Define how to recognise an action already executed before retrying it: repetition must not cause a duplicate message.

Complete for each operation: owner / fields / authorised records / approver / expected result / observed result / date / decision.

Prepared by the Partna team on 5 October 2026 using the Champions Academy CRM permission code and the primary Supabase and OWASP documentation linked above. The matrix and tests are educational proposals to adapt with your administrator. No full security audit, certification or compliance review is claimed. Verify your CRM and connector capabilities before committing.