--- title: Notices slug: guide/notices description: Create and manage notices in Unaric Guide to communicate time-sensitive information to specific users or groups in Salesforce. image: https://archbee-image-uploads.s3.amazonaws.com/10Nod6Ww95R3dPr0k0TCJ/_tngRVPAfkpnDtsU_neBG_unaric-guide.png docTags: createdAt: 2025-07-15T17:07:15.076Z --- Notices are targeted messages created by publishers within a NoticeBoard. Use notices to deliver messages to selected recipients **with predifined Required Actions**. Once published, Notices generate personal Notifications for each recipient, which appear as a Banner. ## Use cases Notices are flexible and can be used for various communication types, such as: - Policy updates that require user acknowledgement - Internal announcements - Change management notices - Just-in-time training - Compliance alerts ## How it works Every Notice has a parent NoticeBoard from which it inherits Notice management policy and default attributes, such as Signatory and any pre-publication approval requirement. Notices consist of: - **Selected Recipients**: the target audience for the critical alerts or call to action. - **Message**: Describing the issue or activity. - **Required Action**: Recipients can be asked to to follow a link, open & read the Notice or read and acknowledge it, with a variety of feedback options. ### Notice lifecycle The typical lifecycle of a Notice includes: ::::WorkflowBlock :::WorkflowBlockItem **Drafting** Define content, select recipients, and configure settings. As defined by the Notice owner, each Notice can include: - A **title**, **summary**, and **detailed message, **which can include rich text, images and links. - The audience of Recipients that will receive the Notice. - **Required action** for recipients (e.g., read and acknowledge) - A **deadline** for response - Optional **signatory** information and **branding** - Optional **approval workflow** and **scheduled publication** ::: :::WorkflowBlockItem **Approval** (optional) Submit for approval if required by the NoticeBoard. ::: :::WorkflowBlockItem **Publication** Publish manually or schedule automatic publication. ::: :::WorkflowBlockItem **Engagement Tracking** Monitor who received, opened, and acknowledged the Notice. Targeted users read and click on Banner items to start the required action set by the Notice publisher. The Recipient's on-click experience will vary according to the "Required Action" set by the Notice's author: - **Click to dismiss**: opens a simple dialogue with any Notice detail needed for a quick 'heads-up'. - **Visit URL**: open a specific web address in a new tab. - **Open and read** or** Read and Acknowledge**: opens their personal Notification page for the Notice. ::: :::WorkflowBlockItem **Suspension or Closure** Retire the Notice when it’s no longer needed. ::: :::: ## Create notices New Notices can be created by a user with Notice Owner permissions from the parent NoticeBoard record, a Notice List view or a New Notice Action. ### 1. Notice creation 1. **Navigate to the relevant NoticeBoard** where the Notice will be published. 2. Click **New Notice**. 3. Enter a title. This will be the Notice headline that Recipients see in their **Notification Banner**, so keep it short, clear and user-friendly (it can be edited later before publication). 4. Click **Continue**. ### 2. Define Notice details & behaviour A Notice's **Notice Definition** tab is where message content and options are managed. Complete the following fields in the **Notice Definition** tab: - **Announcement** - **NoticeBoard (Required)**: The selected NoticeBoard for the Notice. - **Title (Required)**: As it will appear in the Notification Banner. - **Summary**: Optional short description. - **Signatory**: Identify who the Notice is from. The default Signatory for new Notices is the NoticeBoard Owner, but can be overwritten by any name, role, function, etc. - **Custom Style**: Allows you to select a custom style for the notice's theme image preview. - **Personalisation** - **Salutation**: How the notice should greet recipients. You can use different predefined options from the dropdown menu or choose *Other *and enter one of your preference. - **Action** - **Required Action**: Choose how recipients must respond to deem the Notice as successful and clear the associated notification from their Notification Banner. By default, Recipients need to *Read and Acknowledge* the Notice. For simple awareness-raising *FYI* announcements, the Required Action should be set to *Open and Read*. - **Required Action Deadline**: Set a due date for responses. - **Required Action After**: Must be an integer. - **Banner Action Message**: Customize the action text in the banner. - **Response** - **Notification Response Option**: Options include *Acknowledge Only*, *Acknowledge / Acknowledge & Flag*, and *Vote*. - **Acknowledgement Statement**: Optional statement users must agree to if the Notice Required Action is to *Acknowledge the Notice*. New Notices default to use their parent NoticeBoard's default acknowledgement statement. - **Allow comment**: Mark the checkbox for allowing comments. - **Approval** - **Approval Required**: If this Notice must be approved before publication. - **Notice Approver**: Define who must approve the Notice. - **Ignore any Recipients that may cause publication failures**: Mark the checkbox to use this configuration. - **Scheduling** - **Publication Mode (Required)**: How the Notice is published (manually or scheduled). - Suspension Mode: How the notice is suspended (manually or scheduled). - **Content** - **Detail**: Full rich-text message content. After filling all information, click **Save** to finish. :::hint{type="success"} Notices can also be created using the NoticeBoard API via Salesforce process automation or local custom code. ::: ### 3. Select recipients Recipients are the target audience for a notice, selected as individuals or lists, from Salesforce Profiles, Roles, Public Groups or Recipient Groups. To select recipients after defining the notice: 1. Go to the **Select Recipients** sub-tab and click the **Select Recipients **button. 2. Select the Selection Mode: - **Individual Recipients**: Manually add users. This is particularly useful for relatively small, fixed lists of users. - **Recipient Lists**: Use Roles, Public Groups, or Profiles. In this mode, the individuals in each collection are identiied only at the point of publishing the Notice. This mode is useful for larger numbers of users. 3. Use the selection panel to search and add users or groups. 1. Choose Recipient List 1. This section contains a drop down pick list followed by a listing. 2. Select a source list of potential Recipients from the picklist. 3. As you make selections in the picklist, the listing populates with matching items. 2. Select Recipients 1. The listing populates with potential Recipients that match the selections made 2. In Individual mode, these will be names of matching users. 3. In Recipient List mode, these will be matching collections. For example, if in Step 1 one selects Roles and Subordinates then selects a Role, the Step 2 listing will display its subordinate Role names. 3. Selected Recipients - Use Add and Remove buttons to move entries between potential and selected Recipient listings. - This menu also includes a Scope drop down to filter Recipients to include internal users, external users or both. - In Individual mode, the count of currently selected Users is shown below the list field. If any External Users are selected, the count of these is shown highlighted. This helps to manage the risk of Notices for internal audiences being 'leaked' to partner Users. 4. Click **Save**. :::hint{type="warning"} Recipients won’t receive a Notification until the Notice is published. ::: :::hint{type="warning"} See NoticeBoard global settings for definitions of the Salesforce license types that are deemed to represent 'external' users. ::: ## Submit for approval (optional) If **Approval Required** is enabled, you must: 1. Click **Submit for Approval** on the Notice page. 2. The designated **Notice Approver** reviews and either approves or rejects the request. Once approved, the Notice becomes eligible for publishing. :::hint{type="info"} For more information, see [Notice Approvals](docId\:APvG2f1qlF_Gm-5OtasRU). ::: ## Publish notice Publishing generates **Notifications** for each recipient, shown in their Banner. These Notifications are tracked individually to monitor user engagement. You can publish a Notice m**anually **or **automatically** by setting a future **Auto-Publish Date** under scheduling options. ### Prerequisites - ***Drafted *****status**: The notice must be fully defined, with all required fields completed and recipients selected. - **Approval (if applicable)**: If pre-publication approval is configured, the notice must be approved by the designated approver. ### Manual publication 1. Ensure the **Publication Option** is set to "Manual" in the Notice Definition tab. 2. On the **Notice Definition** or **Selected Recipients** tab, click the **Publish Now** button. A confirmation dialog will appear to verify the action. 3. Upon confirmation, the notice is published, and personal notifications are issued to all selected recipients, appearing in their Notification Banners. :::hint{type="info"} If the notice is set to *Scheduled* publication, manual publishing is not possible unless the option is changed to *Manual*. ::: ### Scheduled publication 1. In the **Notice Definition** tab, set the **Publication Option** to "Scheduled." 2. Specify a future date and time for publication. The notice will auto-publish within 15 minutes of the set time, similar to a Salesforce Workflow action. 3. If approval is required, ensure it is granted before the scheduled time. Notices with pending approvals will not auto-publish if configured to prevent this. 4. Use reports and dashboards to track notices pending approval or scheduled for publication to manage potential risks. ## Monitor notices After publication, use the **Notice Status** tab to track engagement across all recipients. Status include *Opened*, *Displayed*, and *Acknowledged*. - View individual recipient actions under the **Selected Recipients** tab. - You may **Suspend** a Notice to stop further notifications. - After suspension, you can optionally **Close** it to mark it for archiving. - **Acknowledgements **can be set as a required action to gather feedback from each Recipient for specific Notices. ### Notice Status Tab - **Left Column: Lifecycle Dates** - Displays key dates such as publication, suspension, and closure dates. - **Right Column: Recipient and Notification Summary** - **Total Selected Recipients**: The number of recipients targeted by the notice. - **Total Notifications Issued**: The count of notifications sent to recipients. - **Notification Lifecycle Breakdown**: - **Displayed Notifications**: Count of notifications that have appeared in recipients’ banners but have not yet been opened. - **Opened Notifications**: Count of notifications opened by recipients but not yet acknowledged. - **Acknowledged Notifications**: Count of notifications where recipients have clicked the "Acknowledge" button, confirming the notice’s acknowledgement statement. - **Acknowledged and Flagged Notifications**: Count of notifications where recipients have clicked the "Acknowledge and Flag" button, indicating a need for follow-up due to conditional acceptance of the acknowledgement statement. ## Suspend notices Notices can be suspended manually or on a scheduled basis to stop them from appearing in recipients’ banners. Once suspended, notices can be closed to finalize their lifecycle. This is useful when a notice has served its purpose, such as for time-sensitive announcements like special offers or system outages. ### Prerequisites - **Notice status**: The notice must be in the "Published" state. Notices that are still in "Draft" or have not been published cannot be suspended. - **Suspension option**: The notice’s Suspension Option must be set to either "Manual" or "Scheduled," as configured in the **Notice Definition** tab. ### Manual suspension To immediately remove a notice from recipients’ banners: 1. Ensure the notice is in *Published* status. Check the **Notice Status** tab to confirm. 2. Confirm that the Suspension Option is set to *Manual* in the **Notice Definition** tab. If set to *Scheduled*, change it to *Manual* and save the notice. 3. Navigate to the **Notice Definition** tab. 4. Click the **Suspend Publication** button. The notice and its associated notifications will be immediately removed from recipients’ banners (either instantly or upon banner refresh, depending on settings). A confirmation dialog may appear (browser-dependent) to verify the action. ### Scheduled suspension 1. In the **Notice Definition** tab, change the Suspension Option to *Scheduled*. 2. Specify an **Auto-Suspend Date** and time, ensuring it is set in the future. 3. Save the notice to lock the settings. The notice will auto-suspend within 15 minutes of the specified date and time, similar to a Salesforce Workflow action and notifications will be removed from recipients’ banners upon suspension.