Product & Service Notifications provide essential transactional updates to Salesforce admins via email. These notifications deliver critical information about changes that may affect the functionality or usage of their Salesforce organizations.
The Salesforce Technology Communications & Readiness team delivers Product & Service Notifications to Salesforce admins. These communications provide timely alerts about changes to features, functionality, or services that could impact their Salesforce usage. Notifications may also outline necessary actions admins should take to prepare for these updates.
Product & Service Notifications include:
Our target audience is a system administrator who manages changes to Salesforce features, functionality, or services on behalf of their organization. We define an admin as any user with a profile, permission set, or permission set group that has the following permissions enabled below:
Additionally, the user must be in an active status.
For Marketing Cloud, the permissions are:
Check your profile or ask the system administrator of your Salesforce org to see if you have these permissions enabled.
NOTE: If a change impacts a sandbox org, the admin(s) of the production org associated with the impacted sandbox org receive the Product & Service Notification.
Receiving these notifications is critical to prepare for changes that may impact your organization. Product & Service Notifications are not marketing emails; they are communications based on your organization’s Salesforce implementation.
Each type of communication has its notification cadence and guidelines. For planned activities, changes, and updates, our goal is to give customers as much notice as possible to prepare for the change, especially if there is an action customers need to take. Additionally, email reminders may be sent to ensure customers are aware and thoroughly prepared.
The following matrix provides an overview of the major communications and associated notification periods:
|
Product & Service Notifications |
1st Notification |
Reminders or Updates |
|
Major Release Reminders |
3 times per year |
N/A |
|
Off-Cycle Release Notifications (Outside of the 24-hour standard release window) |
1 month |
1 week |
|
Product Behavior Changes |
Varies as needed |
Varies as needed |
|
Service Maintenance Notifications* |
Varies as needed |
Varies as needed |
|
Product & Feature Retirement Notifications |
Refer to link |
Sent via newsletter on the 3rd Tuesday of the month |
*Notification of Salesforce taking an extended or off-cycle maintenance
Review the below list of other articles for more detailed information on specific communications:
Marketing Cloud:
|
Product & Service Notifications |
1st Notification |
Reminders or Updates |
|---|---|---|
|
Major Release Reminders- **Marketing Cloud **Social Studio Salesforce Marketing Cloud Release Schedule |
5 times per year 5 times per year |
January, March, June, August & October |
|
Off-Cycle Release Notifications (Outside of the 24-hour standard release window) |
1 month |
1 week |
|
Product Behavior Changes |
Varies as needed |
Varies as needed |
|
Service Maintenance Notifications* (Infrastructure Upgrade) |
Varies as needed |
Varies as needed |
|
Product & Feature Retirement Notifications |
Refer to link |
Once a month via the monthly digest |
*Notification of Salesforce taking an extended or off-cycle maintenance
These communications are sent from: noreply@salesforce.com, alerts@mail.salesforce.com, and techcomms@mail.salesforce.com with the header "Product & Service Notification.”
6. If the admin(s) for my organization works across multiple orgs, will that admin(s) receive multiple notifications for any given Product & Service Notification?
Communications & Readiness team sends Product & Service Notifications to targeted customer lists based on the relevance of specific changes to each organization. Admins receive a notification for each impacted organization they manage.
For example, if you're an admin for three different orgs (each with a unique orgID), you'll receive Product & Service Notifications for each of those orgs whenever the org, or your users, are impacted by a change that may require you to take action.
Add the permissions outlined in Question 2 and confirm the email address is correct and free of typos.
Additionally, there are a small subset of users who have encrypted their email addresses using Shield Platform Encryption. Users with Shield Platform Encryption will not receive these notifications and must provide an alternate email address, in order to be contacted.
Sign up for Trust notifications for your Salesforce instance via Salesforce Trust site. If you'd like more details about what Trust notifications are and how to subscribe, you can review the Trust Notification User Guide.
000387296

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.