As you might have heard, on Friday Marc Benioff officially renamed AIForce to SIForce. This follows the U.S. administration’s executive order that tells federal agencies to replace “Artificial Intelligence” with “Super Intelligence”.

(And by “officially” I mean a post on X)

In case you missed it, AIForce was announced at Dreamforce 2026. It’s mostly a marketing layer that combines capabilities such as Headless 360, hosted MCP servers, APIs, skills and plugins. Everything we’ve known about for quite some time just got an extra layer on top and was packaged together as AIForce.

Now AIForce becomes SIForce, and we should expect other products to be renamed around the Super Intelligence name as well.

Winter ‘27 Is Live

As for the more exciting news, the last release weekend was October 10, so Winter ‘27 has now officially landed in all production environments.

If you missed what’s included, check out this post: Salesforce Winter ‘27 Is Here: All Developers Need to Know

Users have already found two issues in the new release that you need to be aware of.

CustomObject metadata retrieval fails when Profile Filtering is enabled under a high assurance session

Profile Filtering has been an optional setting since Winter ‘21, but Winter ‘27 now turns it on through a release update. If Profile Filtering is enabled under User Management Settings in your org, and Manage Profiles and Permission Sets is set to Raise session to high assurance under Identity Verification settings, your Metadata API calls that retrieve CustomObject might fail with a Salesforce error.

For example, a simple retrieve like this one is enough to run into it:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Account</members>
        <members>Invoice__c</members>
        <name>CustomObject</name>
    </types>
    <version>68.0</version>
</Package>
sf project retrieve start --manifest manifest/package.xml --target-org production

The same applies to any deployment tool or CI pipeline that uses the Metadata API retrieve() call behind the scenes.

For now, the workaround is to turn off Profile Filtering in your production org and wait for a fix.

“Insufficient Privileges” error on the MFA registration page

When new users log in to Salesforce for the first time and are asked to set up MFA, the setup fails with an “Insufficient Privileges” error.

The workaround is to ask the user to log out, log back in and try the MFA setup again (if it’s shown). That should fix it.

Make sure to talk to your users and check your production org before the busy week starts eating you alive. Stay safe, Super Intelligence is here!

Winter '27