This article covers the most common errors you may encounter when logging in to DataGroomr with your Salesforce account, and how to resolve them.

Error: "The DataGroomr app is blocked in your Salesforce organization"

This error occurs when a Salesforce administrator has blocked the DataGroomr Connected App at the organization level. While the app is blocked, no users in the organization can log in to DataGroomr.

How to fix

  1. Log in to Salesforce as an administrator.
  2. Go to Setup → search for "Connected Apps OAuth Usage" in the Quick Find box.
  3. Find DataGroomr in the list.
  4. Click Unblock from the dropdown action menu.
  5. If DataGroomr does not appear in the OAuth Usage list, navigate to Setup → Manage Connected Apps, find DataGroomr, and ensure it is not blocked.
  6. After unblocking, the user should try logging in again.

Note: Only users with the System Administrator profile or the "Manage Connected Apps" permission can unblock a Connected App.

Error: "Your Salesforce profile does not have access to the DataGroomr app"

This error occurs when the DataGroomr Connected App is configured to restrict access to specific profiles or permission sets, and the user attempting to log in is not included.

How to fix

  1. Log in to Salesforce as an administrator.
  2. Go to Setup → search for "App Manager" in the Quick Find box.
  3. Find DataGroomr in the list and click Manage.
  4. Scroll down to the Profiles or Permission Sets section.
  5. Click Manage Profiles (or Manage Permission Sets) and add the affected user's profile or permission set.
  6. Click Save.
  7. The user should try logging in again.

Alternative approach: If you want all users to have access, change the Connected App's Permitted Users setting from "Admin approved users are pre-authorized" to "All users may self-authorize" under the OAuth Policies section.

Error: "Unable to log in — your Salesforce organization has restricted access to this app"

This is a generic error that Salesforce returns when the login is blocked by an org-level policy. The most common cause is that the user's profile has Login IP Ranges configured, and the user is connecting from an IP address outside those ranges.

How to fix

  1. Log in to Salesforce as an administrator.
  2. Go to Setup → search for "Profiles" in the Quick Find box.
  3. Open the affected user's profile.
  4. Scroll down to Login IP Ranges and verify the user's current IP address falls within an allowed range.
  5. If needed, add or expand the IP range to include the user's IP address, or remove the restriction.
  6. The user should try logging in again.

Other possible causes:

  • The Connected App requires admin approval and the user has not been pre-authorized. See the access denied section above.
  • The user's profile has Login Hours restrictions and they are attempting to log in outside the allowed window.

Error: "Your Salesforce session has expired or the authorization code is invalid"

This error typically occurs when the login process was interrupted or took too long, causing the temporary authorization code to expire before it could be exchanged for a session.

How to fix

  1. Try logging in again. In most cases, simply clicking "Log in with Salesforce" again will resolve the issue.
  2. If the error persists, clear your browser cookies for datagroomr.com and salesforce.com, then try again.
  3. If you are still unable to log in, check whether your Salesforce account has been locked or deactivated by contacting your Salesforce administrator.

Other possible causes

  • Refresh token revoked: If an administrator revoked all OAuth tokens for the organization (e.g., via "Revoke All Tokens" in Connected App settings), users will need to re-authorize by logging in again.
  • Browser extensions: Privacy-focused browser extensions that block third-party cookies or redirects can interfere with the OAuth flow. Try disabling them or using an incognito/private window.

Still need help?

If none of the steps above resolve your issue, please contact us at support@datagroomr.com with the following details:

  • The exact error message you see
  • Your Salesforce username
  • Your Salesforce Organization ID (found in Setup → Company Information)
  • A screenshot of the error