Action required by November 30: Keep your Salesforce sync running

  • Updated

What's changing

Starting November 30, 2026, Salesforce will block Act-On from connecting to your org unless the Salesforce user Act-On connects with has a permission called Use Any API Auth. Adding it takes a Salesforce admin about five minutes.  Learn More

This is part of a broader Salesforce security change that retires password-based connections in Summer 2027. Salesforce is tightening access in stages, and November 30 is the first stage that affects Act-On.  We’ll provide information about additional changes prior to the Summer 2027 deadline.

If the permission is missing, your Salesforce sync will stop. Lead, contact, and account updates will no longer flow between Act-On and Salesforce, and Salesforce won't show any error on its side.

Who needs to act

A Salesforce administrator at your company needs to complete the steps below before November 30. You'll need the username of the Salesforce user Act-On connects with, which you'll find in Act-On under Connectors > SalesForce.

If that user has the standard System Administrator profile, it may already have this permission. Check anyway, because many companies use a custom or API-only profile for integrations, and those usually don't include it.

How to fix it

You'll create a small permission set that contains only this one permission, then assign it to your Act-On user.

  1. In Salesforce, go to Setup. In the Quick Find box, type Permission Sets and select it.
  2. Click New.
  3. Fill in the details:
  • Label: Act-On Integration – API Auth
  • Description: Lets the Act-On integration user connect to Salesforce. Required from Nov 30, 2026. 
  • License: depends on your Act-On user's license. To check, go to Setup → Users, open your Act-On user, and look at the User License field. If it says Salesforce, leave the permission set License as --None--. If it says Salesforce Integration (an API-only user), choose Salesforce Integration.
  1. Click Save.
  2. On the permission set page, click System Permissions, then Edit.
  3. Check Use Any API Auth, then click Save. If Salesforce asks you to confirm changes, confirm them.
  4. Click Manage Assignments, then Add Assignment.
  5. Select the Salesforce user Act-On connects with, then click Next and Assign.

Be careful with the name. Salesforce also has a permission called Use Any API Client. It is a different permission and will not keep your sync running. Make sure you enable Use Any API Auth.

Can't find or save the permission? It can only be assigned to users whose Salesforce license supports it. If it isn't listed, or Salesforce won't let you assign the permission set to your Act-On user, contact Act-On Support before November 30 and we'll help you set up a user that works.

How to confirm it worked

  1. In Salesforce Setup, open Users, select your Act-On user, and check that Act-On Integration – API Auth appears under Permission Set Assignments.
  2. In Act-On, open [Act-On path to CRM sync status] and confirm the next scheduled sync completes without errors.

No other changes are needed. Your existing Act-On connection, field mappings, and sync settings stay the same.

Frequently asked questions

Salesforce told us something changes in February. Is that this? No. February 20, 2027 is when Salesforce retires a different sign-in method, the OAuth username-password flow. This is not used by Act-On. December 1 is the date that matters for your Act-On connection.

Is this a permanent fix? No. It keeps your sync running until Salesforce fully retires password-based connections in Summer 2027. Before then, Act-On will release a new, more secure way to connect, and we'll send step-by-step instructions for switching.

Should we switch to Salesforce's API-only integration user now? You don't need to for November 30. If you do switch, add the Use Any API Auth permission to the new user, and make sure it can see every object and field Act-On syncs. Otherwise records may stop syncing.

Do we need to reconnect Act-On to Salesforce? No, as long as you add the permission to the user Act-On already connects with.

Who can help? Contact support and mention the November 30 Salesforce permission change.

Was this article helpful?

Have more questions? Submit a request