You are here:
Salesforce Spiff Release Notes for November 11, 2024
Secure your Salesforce Spiff environment with additional authentication requirements, and automate Spiff plan assignments with more confidence.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Secure your Salesforce Spiff environment with additional authentication requirements, and automate Spiff plan assignments with more confidence.
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
| Available for an additional cost in: Professional Edition with Web Services API Enabled |
Build your culture of trust, for your company and customers, by adding another layer of protection for users who log in to Spiff. Multi-factor authentication (MFA) reduces the risk of unauthorized access to systems by requiring users to provide two or more verification factors, such as a password and mobile device with an authenticator app.
How: Turn on MFA from your Spiff settings.
The only supported secondary authentication factor is an authenticator app. Spiff doesn't support MFA with the mobile app.
MFA isn't available if your company uses single sign-on (SSO) authentication.
See Set Up Multi-Factor Authentication for Salesforce Spiff.
Scale plans to more reps with a more sophisticated solution for automated plan assignment. Developers can reference a new planID field, a read-only unique ID that doesn't change on the Plan Assignment object. Previously, developers referenced a Plan_Name field, which an admin could change in Designer and break automation that depended on it.
How: To find the plan ID, go to Designer and click a plan. In the right panel, under the Settings tab, copy the Plan ID.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.