You are here:
Create an App Alert
App alerts are contextual notifications that appear in the Notifications experience and in specific areas of the application. When you create an alert, select a context type to control where the alert appears: Global, Object, and Tab. You can also include an additional message to provide links, actions, or tags that guide users toward their next steps.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
| User Permissions Needed | |
|---|---|
| To configure App Alerts: | Life Sciences Commercial Admin |
- From the App Launcher, find and select App Alerts.
- Click New.
- Enter a subject.
-
Select the type of alert.
- Notification: Provides short, contextual updates about relevant actions or statuses.
- Recommendation: Guides users toward the next best action or suggestion.
- Guided Action: Directs users through specific tasks by using predefined instructions.
- Announcement: Shares broad internal communication, such as home office announcements. For more information, see Create Home Office Announcements.
If you set the alert type to None, the app alert is considered as a notification. -
Select the display context type.
- Object: Shows the alert on all the record pages of a specific
object. After you select Object, specify the object name in the Display
Context Name field. For example, enter Account so the app alert is
visible on all Account pages.
Note: Object type is supported only on mobile.
- Tab: Shows the alert on a specific tab in the app. After you
select Tab, specify the tab details in the Display Context Name field.
There are three distinct naming conventions for tabs and you can refer to this table for
examples.
Tab Pattern Example of Display Context Name Standard Tab Prefix with “standard-" - standard-home
- standard-Visit
Managed Package Tab Prefix with the namespace - For Account, use lsc4ce__AccountFilter
- For Calendar, use lsc4ce__Planner
- For Intelligent Content, use lsc4ce__IntelligentContent
- For Sales Data, use lsc4ce__SalesData
Custom Tab No prefix Defined by admins Note: Tab type is supported only on mobile.
- Global: Shows the alert across all pages.
If you leave the Display Context Type field blank, Global is applied by default and the alert shows on the home page.
Note: Global type is supported only on mobile.
- Object: Shows the alert on all the record pages of a specific
object. After you select Object, specify the object name in the Display
Context Name field. For example, enter Account so the app alert is
visible on all Account pages.
-
Select the effective start date and time.
Indicates the date and time from when the alert becomes visible to users.
-
If needed, in Valid Until Date, select the effective end date and time.
- On mobile, notifications and recommendations are visible by default for up to 7 days from the effective start date, unless removed earlier by users.
- If you don't set a value in the Valid Until Date field for web, alerts are visible indefinitely until the user marks them as Read.
-
If needed, in Additional Message, enter a JSON-formatted value that follows the supported
scheme. The Additional Message field appears only on mobile.
This field supports a JSON structure that enables deep links, external website links, action buttons, and tags on mobile. If the alert is actionable, define the action and mark it as Dismissed or Resolved using the actionName attribute in the JSON. For more information, see Additional Message for App Alerts on Mobile.
-
If needed, enter a message. The Message field appears on both the web and mobile
applications.
Note: If you provide valid values in both the Message and Additional Message fields, only the content in the Additional Message field appears on mobile. To avoid inconsistencies between web and mobile displays, we recommend keeping the content in the Message and Additional Message fields consistent.
- Save your changes.
Did this article solve your issue?
Let us know so we can improve!

