Notification Groups

The Notification Groups page allows customer administrators to organize and manage groups of peers who receive automated system notifications. This feature helps streamline communication by grouping recipients according to purpose or responsibility — for example, technical alerts, billing updates, or security warnings.

Notification Groups ensure that relevant peers receive messages triggered by specific system events, such as service suspensions, quota limits, or ticket updates.

Interface Overview

The main Notification Groups list displays all created groups within the current customer account. The table contains the following columns:

• Name — The name of the notification group.
• Recipients — Displays all peers currently included in the group.
• Actions — Provides quick options for editing or deleting a group.

If no groups have been created, the page will display the message No records….

Creating a Notification Group

To create a new group, click + Add Notification Group. The following fields will appear:

• Name — Enter a clear and descriptive name that reflects the group’s purpose (e.g., “IT Alerts” or “Billing Team”).
• Description — Optionally provide additional details about the group’s function or scope of notifications.
• Recipients — Select one or more existing peers to include in the group. Each peer will receive notifications associated with this group.

After configuring all required fields, click one of the available options:

• Save Changes — Saves the group but keeps the current window open for further editing.
• Save Changes and Exit — Saves the group and returns to the main Notification Groups list.
• Cancel — Discards unsaved changes and closes the form.

Editing and Managing Groups

Existing groups can be modified at any time to update their name, description, or list of recipients. When editing a group, changes take effect immediately after saving and apply to all future notifications sent through the system.

To delete a group, use the Actions column in the main table. Deletion permanently removes the group and its associations, but does not affect peers themselves or other groups they belong to.

Use Cases

• Service Notifications — Send operational alerts to IT staff or system engineers.
• Billing Reminders — Notify accounting or finance peers about invoice events.
• Security Alerts — Distribute access or login-related warnings to administrators.

Best Practices

• Use descriptive names to distinguish between operational and administrative groups.
• Regularly review group memberships to ensure only active peers receive notifications.
• Avoid duplicating recipients across multiple overlapping groups unless necessary.
• Combine notification groups with Peer Roles for more precise communication control.