LogoLogo
LogoLogo
  • Welcome
    • Navigation
  • RealmJoin Deployment
    • Onboarding
    • Required Permissions
    • Infrastructure Considerations
      • Multi User Devices
    • Migration to RealmJoin vNext
  • User, Group and Device Management
    • Overview
    • User Profile
    • Organization Details
    • User, Group and Device Lists
      • Advanced Search
      • User Details
      • Group Details
      • Device Details
    • User and Group Settings
      • Available RealmJoin Policies
  • App Management
    • Packages
      • Package Store
        • Application Store Details
      • Package Management
      • Package Details
      • Package Assignments
        • Package Migration
      • Package Settings
      • Packaging Requests
        • Organic Packages
    • AVD Templates
  • Automation
    • Connecting Azure Automation
      • Required Permissions
      • Runbook Parameters
    • Runbooks
      • Runbook Customization
      • Runbook Permissions
      • Naming Conventions
      • Runbook Scheduling
      • Runbook Logs
        • Runbook Job Details
      • Runbooks Changelog
    • Requirements
    • Remediation Scripts
  • RealmJoin Agent
    • Features
      • Local Admin Password Solution (LAPS)
        • KeyVault
        • Application Insights
      • Notifications
      • AnyDesk Integration
        • AnyDesk configuration
      • App Deployment using the Agent
        • RealmJoin ESP
    • Deploying the Agent
    • User Interface
  • Logs
    • Connecting Azure Log Analytics Workspace
    • Audit Log
  • RealmJoin Settings
    • Overview
    • General
    • Roles and Permissions
      • Pre-defined Roles
      • Custom Roles
        • Available Permissions
    • Group Namespaces
    • Workplace Cloud Storage
    • Self Service Forms
  • Developer Reference
    • RealmJoin API
      • Authentication
    • Interacting with Runbooks
    • Simulating a Runbook Environment
    • Local Admin Password Management
  • Other
    • FAQ
      • Security
    • Troubleshooting
      • Package Installation Issues
        • Collecting Logfiles
        • Logfiles Structure
        • Analysing chocolatey.log
        • Troubleshooting failed chocolatey packages
        • Troubleshooting failed craft packages
        • Fixes for common issues
        • Intunewin Debugging
      • LAPS Issues
        • LAPS account passwords cannot be retrieved
        • Requested LAPS Accounts are not being created
    • Changelog
  • Legal
    • Licensing
    • Support
  • RealmJoin Website
Powered by GitBook
On this page
  • User Experience
  • Creating a Notification
  • Basic Settings
  • Advanced Settings
  • Saving and Publishing Notifications
  • Cancelling a Notification

Was this helpful?

Edit on GitHub
  1. RealmJoin Agent
  2. Features

Notifications

Last updated 10 months ago

Was this helpful?

Our notification system allows you to send notifications directly to user’s computers. This can be useful for displaying general information or important issues.

User Experience

Once you have created your notification, the target groups will receive a notification at the scheduled time. This notification appears on the desktop of a client.

The user receives different colored notifications based off the notification category chosen. Once a notification has been closed and acknowledged by the user, it will not re-appear.

Creating a Notification

Basic Settings

  1. Category: Choose the category of your notification. The options are:

    • None

    • Info

    • Alert

  2. Notification Schedule: Set a Start and End date for the notification. The notification will only be active during this period. Use the prompts to quickly fill

  3. Notification Content: This includes:

    • Language (Optional): The language of your notification. This field accepts IETF language tags.

    • Title: The headline of your notification.

    • Body: The main content of your notification.

Advanced Settings

  1. Disable Click Through: If enabled, users will not be able to click on the notification to navigate to a different page.

  2. Disable Transparency: If enabled, the notification window will not be transparent.

Please note that these advanced options might affect the user experience, so use them wisely.

Effective notifications are concise, relevant, and timely. Always respect the user’s time and attention when sending notifications.

Saving and Publishing Notifications

In order to publish a notification, the configured notification must first be saved as a draft.

Drafts will appear in the notification list with a yellow "Draft" tag.

Once a draft has been saved, the administrator will be prompted to either Publish or Delete.

Cancelling a Notification

Once a notification has been published, administrators will have the option to cancel the notification.

Cancelling a notification will cause the notification to disappear from a user's device without their intervention. Cancelled notifications cannot be recovered, will be deleted after 30 days and appear in the notification list with a red "Cancelled" tag.

The notifications are transparent and are able to be clicked through to minimize disruption. This can be changed in the .

Target Groups: Specify which should receive the alert. You can also exclude certain groups if needed.

Publish: Selecting Publish will prompt for an additional Confirm Publish button. Once notifications are sent out, they are not easily retrieved. Please make sure the notification is configured as intended prior to publishing.

Delete: Selecting Delete will prompt for an additional Confirm Delete button. Once messages are deleted, they cannot be recovered. They will be deleted after 30 days.

groups
Advanced Settings
Category: None
Category: Info
Category: Alert