The notification builder in the Hub Services console guides you through the steps to create a notification, select the target audience, and create an actionable response. When you click Publish in the wizard, the notification is sent to the target audience. For step-by-step instructions, see Create Notifications in Workspace ONE Hub Services.
The type of notifications that can be sent are Actionable and Informational. See Types of Notifications That Can Be Sent from Workspace ONE Hub Services.
You can also create and save commonly used notifications as notification templates. See Creating Notification Templates in Workspace ONE Hub Services.
Important: If a notification creation request includes a user in the target audience with more than 10,000 devices, Hub Services skips the entire request and no user, regardless of the number of devices registered to them, receives the notification.
Who can send Notifications in Hub Services
Users who are delegated super admin permissions can send notifications to any audience.
In addition, super admins can assign user groups to predefined administrator roles to manage the Notifications services.
- Notification Admin. The notification admin role can create and send notifications, manage the notification list on the Notifications List tab, and edit the Notifications Global Settings page.
- Notification Creator. The notification creator role can create and send notifications from the Notifications List tab. The notifications creator has read-only access to view the Global Settings page.
- Notification Auditor. The notification auditor role has read-only permissions to view the Notifications List tab and Notifications Global Settings page.
When super admins assign user groups to a notification role, they can specify the exact target audience the admin can send notification to. When admins that are assigned a role with a custom target audience create notifications in the notification builder, the target audience field is pre-configured with the custom target audience name.
See Manage Admin Roles in Workspace ONE Hub Services.
Selecting the Target Audience
By default, notification admins can send notifications to the target audience types in your organization as listed in the table that follows.
You can select multiple groups within a single audience type. For example, you can select several Organization Groups or several Smart Groups in a single notification.
You can also combine Organization Group, Smart Group, and Platform audience types together in the same notification. For example, you can target specific Organization Groups, Smart Groups, and a Platform all in one notification. The notification is sent to all selected groups and platforms in one action, and all selected audience types and groups are listed together in the Target Audience Types column for that notification in the Notifications list.
All Employees and Users Group are user-level audience types and cannot be combined with the device-level audience types All Devices, Organization Group, Smart Group, or Platform in the same notification.
The following are the available audience types that can be selected.
| Audience Types | Description |
|---|---|
| All Employees | Notifications can be sent to all employees listed as users in the Omnissa Access service. |
| All Devices | Notifications can be sent to all devices configured in your Workspace ONE UEM environment, regardless of organization groups. |
| Organization Group | Organization groups (OG) in the Workspace ONE UEM console are created to group individual organizations in your corporate structure, geographical location, business unit, or department. You can select one or more organization groups in Workspace ONE UEM in which to send the notification. |
| Smart Group | Smart groups are customizable groups within Workspace ONE UEM that determine which platforms, devices, and users receive an assigned application, book, compliance policy, device profile, or provision. You can select one or more smart groups in Workspace ONE UEM in which to send the notification. |
| Platform | You can select one or more platform types to send a notification. The platforms are iOS, Android, macOS, and Windows. |
| Users Group | Groups in the Omnissa Access service are imported from your Active Directory or are created as local groups in the Omnissa Access console. You can select one or more Omnissa Access User groups to which to send a notification. |
| Email Recipients | Designate email addresses of specific users to receive the notification. Copy and paste or manually enter email addresses into the text box that appears below the drop-down.
When the Email Recipients audience type is selected, an Email Notification toggle appears in the Notification Builder and is enabled by default. If SMTP is configured in Hub Services, notifications are delivered to both the user's device (push) and the user's email inbox. If the user's email address exists in Workspace ONE UEM or Omnissa Access, the notification is sent to both the device and the corresponding inbox. If the email address is not found in UEM or Access, neither the device notification nor the email is delivered. If SMTP is not configured, the notification is delivered to the user's device only. To send email notifications to users' inboxes, you must configure SMTP. See Configure SMTP Settings for Hub Services. |
If your organization implements the pre-hire onboarding process, you might not want to send certain types of notifications to the pre-hire audience and groups. To exclude users in the pre-hire groups from receiving a notification, when you configure the target audience on the Definition page, select the Exclude Pre-hires check box.
Customized Target Audience Permissions
When the notification admin role specifics a specific target audience, an admin can have either Full Access to all users in the target audience or can have Custom Access and be given permissions to send notifications to selected group of users. The target audience types that can be select are shown in the following figure.
- When an admin has Full Access permissions. they can send notifications to all groups or platforms in the target audience type. If Omnissa Access user group is selected as the target audience, full access includes All Employees as a group. If Smart Group is the target audience, full access includes All Devices as a group.
- When an admin has Custom Access permissions in a target audience, specific groups or platforms are assigned as the target audience type. All Employees or All Devices can be selected as a custom access option.
When an admin role includes custom target audiences, the notification builder shows only the target audience types and groups that the admin has permissions to access.
Actions That Can Be Added to Notification Messages
At the most, three actions can be presented on the notification card. When you create an action, a button appears with the text you configured. The ideal user experience is to have one or two actions. Any more than three can degrade the user experience as the buttons are in a horizontal line on the card, and the card can be too narrow to display the action buttons correctly.
Three action types can be selected.
-
Open In. When you select the Open In action, you then enter the URL that opens when the button is clicked.
-
API. When you select API, you then select the method to use to interact with the data being addressed in the notification.
API Task Description GET Use GET to retrieve data from a specified resource. The data is not modified. Enter the URL of the resource that supplies the data. POST Use POST to send data to a specified URL to insert data in a resource. Enter the URL where the data is sent. PUT Use PUT to send data to a specified URL to update a resource. Use PUT when user can only send the data one time. PATCH Use PATCH to allow users to modify their data on the resource. DELETE Use Delete to let the user delete data from the specified URL. -
API with Parameters. When you select API with Parameters, in addition to selecting the method and API endpoint, you can add specific parameters and a value for the parameters.
For more information about parameters, go to the Workspace ONE Notification service API page. The Notifications Service reference guide is available from the Documentation tab.
Adding Attachments
You can add up to 10 attachments to notification that you create. The individual file size cannot exceed 5 MB.
Adding an Image, Video, and Links to Notifications
You can select to add an image or a video that displays as a banner in your notification and links that display in the View more section of the notification.
-
To allow images and videos to display correctly in the notification banner, configure the web portal to permit cross-origin access to image or video files. You configure the following Cross-origin Resource Sharing (CORS) request headers on your website.
Access-Control-Allow-Origin: <YOUR-HUB-APP-URL> Access-Control-Allow-Method: GET -
To display an image in the notification banner, enter the full URL address that includes
HTTPS. Example of a full image URL address:https://www.mozilla.org/media/img/firefox/new/desktop/hero-mr1.c078ff206641.png. The image must be either a JPG or PNG file and the aspect ratio of the image must be 4:3. -
To display a video in the notification banner, enter the full URL address including
HTTPSthat is displayed in the embedded code as thesrcvalue. For example,<source src="https://www.mozilla.org/media/videos/abcvideo.mp4">. -
To add links to the notification, you add the link title that displays in the notification and then the complete link URL. You can add up to 10 links.
Notification Delivery Time
When you use the wizard to create a notification, when you click Publish, the notification is created and sent.
The time it takes for the target audience to receive a notification depends on various factors. These factors include the Workspace UEM Mobile Device Management API response time and the total number of users and devices targeted for the notification. On average, you can expect 10,000 recipients to receive the notification within 45 minutes.
Guidelines for Creating User-Friendly Notifications
Notifications cards include a header and message. The notification can also include buttons that make the message actionable. When you compose a message, consider the following good practices.
- Write short titles to catch the users' attention.
- Make the description message clear and concise.
- Use the Additional Details section to list details with a Label/Description that you would like to call out. Examples of types of additional details to add.
- Author:Name
- Phone number:XXX-XXX-XXXX
- Source:Technical Marketing
- No more than three actions can be presented on the notification card. One or two actions are the ideal user experience.
- When you create a label for your action button, keep it short to avoid truncation.
- If the user can repeat the action, enable the Repeatable radio button in the Content page. When the radio button is deactivated, users can perform the action once.
- The action buttons appear as either primary or secondary. The primary action button appears before a secondary action button.
- Toggle on Use Rich Text Formatting to emphasize parts of the notification Description using character formatting, such as bold, underline, italics, colors, bulleted lists, and numbered lists.
In the default view of a notification message, a logo image appears in the left corner of the notification. You can change this image when you create a custom notification. You can upload an image or add a URL address to an image you want to appear on the card.
Was this page helpful?