Salesforce's December 1 login change: is your small business ready?

By Intelligent Solutions LLC · · 2 min read

Salesforce's December 1 login change: is your small business ready?

On December 1, 2026, some of the tools connected to your Salesforce could stop signing in. If an old integration fails, the first thing you'll notice is data that quietly stops syncing.

What Salesforce is changing

Salesforce's developer blog says that beginning December 1, 2026, every user who authenticates with SOAP API login() needs the Use Any API Auth user permission. It adds that this applies to all orgs and that users without the permission get an error.

In plain English: some older apps connect to Salesforce by sending a username and password through a method called SOAP login(). (SOAP is an older way for software to talk to other software.) Salesforce is tightening access to that method now, as a step toward removing it.

The bigger deadline is Summer '27

This is a step toward a larger change. Salesforce's API documentation says the SOAP login() call is scheduled for retirement in Summer '27, and the developer blog notes that it retires for API versions 31.0 through 64.0. After that, an integration that still uses it will not work at all, whatever permissions it has.

Which small business tools could be affected

Most small teams never touch this directly. The risk sits in the connections other people built for you: older middleware, backup tools, e-signature apps, reporting add-ons and custom scripts from a past contractor.

Sage gives a real example in its help center for Sage People customers. It tells them to update DocuSign to use OAuth instead of the legacy SOAP login and to ask the provider of any custom integration whether it uses the SOAP username and password method. OAuth is the modern, token-based way of letting one app connect to another without sharing a password.

A 15-minute check you can do this week

  • Look at your Login History. In Salesforce Setup, review Login History for SOAP API logins, as Sage suggests. Note which user names and which apps show up.
  • Make a list of your integrations. Match each login to a tool and an owner. A user name like "integration" or "sync" with no clear owner is the one to chase first.
  • Ask each vendor one question. "Does your connection to our Salesforce use SOAP login(), and when will you move to OAuth?"
  • Test before December 1. Salesforce says admins can test the change in advance with the release update in Setup. Assign the Use Any API Auth permission to the integration users that need it, and only to them.
  • Plan the real fix. The developer blog advises moving integrations to OAuth with external client apps. Treat the permission as a short-term bridge, not the destination.

The takeaway

A permission change on December 1 is easy to handle if you find the affected integrations first. Waiting for the error is the expensive way to learn about it, because a broken sync can go unnoticed for days.

Not sure which of your tools log in this way? Book a free audit and we will map your integrations and flag the ones that need attention.

Sources