10.9. Configure Email and In-App Notifications for Invoices, Projects, and Tickets

Notifications help your MSP keep the right people informed without relying on manual reminders. A well-tuned setup can alert staff about invoices, projects, tickets, and other operational events while avoiding unnecessary noise.

Navigate to Settings > General in the sidebar to open Admin Settings, then select Notifications (under Communication). This section allows you to configure system notifications, with separate views for Email Notifications and Internal Notifications.

Figure 1: Notification Settings. The Global Settings toggle controls all notifications for the tenant, and the Settings, Email Templates, and Categories tabs refine what gets sent.

1. Open Settings > General, then click Notifications in the Admin Settings sidebar.
2. Review Global Settings on the Settings tab. Use the Enable Notifications toggle to turn notifications on or off for the entire tenant, then click Save Changes.
3. Review the Categories tab. Enable or disable notifications for specific categories like Invoices, Projects, and Tickets.
4. Review the Email Templates tab. View and customize the content of email templates for various events.
5. Switch between Email Notifications and Internal Notifications to configure each delivery channel.
6. Test a small workflow after changing notification behavior. For example, if you adjust ticket notifications, confirm the expected staff receive the appropriate in-app or email notification when a ticket event occurs.

After configuration, AlgaPSA should send notifications according to the tenant-wide settings, category choices, and template content. If global notifications are off, category-level choices will not have the same practical effect because the tenant-level switch controls overall delivery.

Brand and edit email templates

In Email Notifications, use Email Branding to preview and apply your MSP's colors across templates and languages. Email Templates provides a side-by-side editor for the subject, HTML, and plain-text content beside a live preview. See 10.22. Brand System Emails and Edit Notification Templates for both workflows and the Enterprise logo and footer options.

Set tenant notification priorities

Open Settings > General > Notifications > Internal Notifications > Categories & Types. Each notification subtype row has a Priority selector with High, Normal, and Low. Use Reset to default when a tenant-level selection should return to the subtype's default priority.

Individual users can override the inherited priority at Settings > Profile > Notifications > Internal with the same High, Normal, and Low selector. The personal control also includes Reset. Treat tenant priorities as operational defaults, then allow role-specific exceptions for staff whose responsibilities differ.

For personal email delivery choices, open Settings > Profile > Notifications > Email on your MSP profile. Category and individual notification toggles save as you change them and retain those choices when you return to the profile.

The numeric bell badge counts only unread High priority notifications. If unread items exist but none are high priority, the bell shows a neutral dot instead of a number.

Understand the background-job attention indicator

The background-job attention indicßator counts failures from the last 24 hours. A failure that was resolved more than a day ago no longer keeps the attention dot lit, allowing the indicator to represent recent work that may still need investigation.

Be deliberate with invoice and ticket notifications. Billing admins may need invoice messages promptly, while technicians and dispatchers may care more about ticket-related updates. Too many broad notifications can cause staff to ignore important alerts.

Operational tip: review notification categories after enabling new workflows. For example, RMM alert rules can notify chosen team members when an alert creates a ticket, and the RMM alert category is managed in Notifications (under Communication). Align those notifications with your dispatch process before going live.