SugarCRM

Connect SugarCRM to collect crm evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In SugarCRM:

   1. Create or choose a Sugar user for Safeguard to sign in as.
   2. Optional: have a Sugar administrator create a dedicated client ID in the OAuth Keys section of Administration; otherwise the default client_id sugar with an empty client_secret is used.
   3. Request a token with a POST to https://<your Sugar instance>/rest/<version>/oauth2/token using grant_type password, client_id, client_secret, username, password and platform (default base; register a custom platform value to avoid logging out other sessions).
   4. Paste the returned access_token into Access token, or instead fill in Client ID, Client secret, Username and Password so Safeguard can request tokens itself.

   Where to find the other values:

   • Instance URL: The address of your Sugar instance (the host you sign in to).
   • Client ID (optional): sugar by default, or the key an administrator created under Administration › OAuth Keys.
   • Username (optional): The Sugar user's login name.

   SugarCRM issues this credential through its API or its support team, not through its admin screens.

   Sugar has no token page in the UI; tokens come from the OAuth2 password grant. access_token expires in 3600 seconds and refresh_token in 1209600 seconds (14 days), so a pasted access token is short-lived; the client and user fields are the durable option. The role permission needed to read Users was not on the fetched page. support.sugarcrm.com now redirects to support.sugarai.com.

   Source: support.sugarai.com, checked 2026-10-07.

   The permissions Safeguard needs: Users: Read.

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

   Field	What to enter
   Instance URL	Optional. Your own server: an https address reachable from the internet.
   Access token	Optional. Stored encrypted and never shown again.
   Client ID (optional)	—
   Client secret (optional)	Stored encrypted and never shown again.

   Or, instead: Username (optional), Password (optional).

3. Click Connect with token.

Frameworks

Safeguard's automated tests read SugarCRM 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

• CRM 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