Zendesk Sell

Connect Zendesk Sell to collect ticketing evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Zendesk Sell:

   1. Sign in to Sell as a user who can see every account, and go to Integrations › OAuth.
   2. Open the Access Tokens tab and click + Add User Token.
   3. Fill in the Description field and click Save.
   4. Copy the token from the window before closing it; once the modal window is closed the token cannot be retrieved, and you would have to generate a new one.

   Zendesk Sell shows the secret only once, so copy it before you leave the page.

   Sell access tokens have an unlimited lifetime. Sell's scopes are read (read-only access to all data except account and user info), write, and profile (read-only access to account and users info). The first-call guide does not show a scope picker for user tokens, so whether a token can be limited to read at creation is not documented; the token carries the rights of the user who creates it.

   Source: developer.zendesk.com, developer.zendesk.com, checked 2026-10-07.

   The permissions Safeguard needs: read. The credential carries its user's rights: create it as a user who can see every account.

2. On Compliance › Connectors, open Zendesk Sell, click Connect, choose API token and fill in:

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Zendesk Sell and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Ticketing connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks