Resolving OAuth Errors When Authenticating New Users in Recruiterbolt

Created by Salesbolt Support, Modified on Thu, 18 Sep at 5:45 PM by Salesbolt Support

Why You’re Seeing This Error


Starting August 28, 2025 (for sandboxes & new orgs) and September 1, 2025 (for existing orgs), Salesforce introduced new security requirements for all Connected Apps that use OAuth.

Recruiterbolt uses a Connected App named Salesbolt. If these new settings are not applied by your Salesforce Admin, new users may encounter OAuth errors when trying to log in or authenticate.

How to Fix the Issue (For Salesforce Admins)


1. Log into Salesforce as a System Administrator.
2. Navigate to Setup → App Manager.
3. Locate the Connected App called Salesbolt and click Manage.
4. On the 'Policies' page, update the following:

- Permitted Users → Admin approved users are pre-authorized
- Session Policies → Configure timeout/session security per your org standards
- MFA / High Assurance → Enable if required by your org’s policy


5. Save changes.
6. Create or update a Permission Set (recommended name: 'Salesbolt Users').
7. In the Permission Set, go to 'Assigned Connected Apps' and add Salesbolt.
8. Assign this Permission Set to all users who need Recruiterbolt access.
9. Ask the user to retry authentication in Recruiterbolt.


Quick Checklist for Admins

✅ Salesbolt appears in App Manager

✅ Permitted Users set to 'Admin approved users are pre-authorized'

✅ Salesbolt added to a Permission Set

✅ Users assigned via Permission Set

✅ Session policies configured

✅ MFA/High Assurance set if required

✅ Authentication tested successfully


Still Seeing Issues?

- Confirm that the user is assigned the Permission Set that grants Salesbolt access.
- Verify that the org has applied Salesforce’s latest Connected App policy changes.
- Reference Salesforce’s official guidance: https://help.salesforce.com/s/articleView?id=005132365&type=1

If the problem continues, please contact Recruiterbolt Support with:


- The affected user’s Salesforce username
- A screenshot of the OAuth error
- Confirmation that the above steps were completed


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article