Salesforce Integration: Use Any API Auth Permission Update

On December 1, 2026, Salesforce is enforcing a security change that affects how outside apps, including Alchemer, sign in to your Salesforce account. To keep the Alchemer Survey Salesforce integration running, your Salesforce admin needs to turn on a permission called Use Any API Auth for the Salesforce user Alchemer connects as. Without it, the integration pauses until the permission is on.

At a glance

What Turn on the Use Any API Auth permission for the Salesforce user (or users) Alchemer connects as.
When Before December 1, 2026.
Who Your organization's Salesforce admin.
How long About five minutes.

In Salesforce, this change appears under Setup > Release Updates as Assign Use Any API Auth Permission for SOAP login().

Enable the Use Any API Auth permission

Step 1: Find the Salesforce user Alchemer connects as

  1. In Alchemer, go to Integrations > Data Connectors in the left navigation.
  2. Click Edit on your Salesforce integration to see the username it uses.
  3. If you have more than one Salesforce integration, check each one and note every username.

Step 2: Create a permission set in Salesforce

  1. Click the gear icon and select Setup.
  2. In the Quick Find box, type Permission Sets and select it.
  3. Click New.
  4. Enter a label, such as Alchemer Integration API Auth. Leave License set to --None--.
  5. Click Save.

Step 3: Turn on Use Any API Auth

  1. In your new permission set, click System Permissions.
  2. Click Edit.
  3. Check Use Any API Auth.
  4. Click Save. If Salesforce asks to turn on related permissions, confirm.

Step 4: Assign the permission set

  1. Click Manage Assignments, then Add Assignment.
  2. Select each Salesforce user you noted in Step 1.
  3. Click Next, then Assign, then Done.

Tips

  • Check this even if the connected user is a System Administrator. Admin profiles don't always include this permission.
  • Prefer to manage permissions by profile? You can turn on Use Any API Auth under Setup > Profiles > [the user's profile] > System Permissions instead.
  • For Salesforce's own instructions, see "Granting the permission" in the SOAP API Developer Guide.

What happens if the permission is not enabled

Starting December 1, 2026, Salesforce blocks Alchemer from connecting to your account until the permission is on. While the connection is blocked:

  • Surveys that pull information from Salesforce, like a contact's name or account details, can't fill it in.
  • Surveys that send responses to Salesforce don't create or update records.

Your surveys keep running and collecting responses, but responses collected while the connection is blocked don't reach Salesforce. As soon as the permission is on, the connection picks back up.

Why this change is happening

Salesforce is tightening how outside apps sign in to its platform. This is the first of several changes Salesforce has planned over the next year, and Salesforce will eventually retire the sign-in method the integration uses today. For details, see Salesforce's notice.

Before summer 2027, Alchemer will move the Salesforce integration to OAuth, a newer and more secure way to connect. That means:

  • A more secure connection that meets Salesforce's latest standards.
  • No password and security token to manage for the integration.
  • A connection built to keep working as Salesforce continues to update its platform.

You don't need to do anything for the OAuth change yet. Alchemer will share details and timing well in advance so your team has time to plan.

Need help?

If you hit a snag or want someone to walk through the update with your Salesforce admin, reach out to your CSM or contact Alchemer Support.

Basic Standard Market Research HR Professional Full Access Reporting
Free Individual Team & Enterprise
Feature Included In