Notification Trigger Suppression is a set of controls on every Notification Trigger that limits how often the trigger may fire, both per target record and across the school as a whole. Suppression keeps automated communication useful by preventing the same family, student, or staff member from receiving the same message more often than the school intends, and by capping the total number of fires for high-risk triggers within a defined period.

Suppression applies to every trigger Category, including Student and Household. When a quota cap is reached, the trigger is suppressed quietly. The underlying condition query is not modified, and no error is raised.

Roles required

The Notification Triggers page is restricted to users with the Security Full role. The same role governs all trigger Categories and all suppression fields.

Suppression fields

Every Notification Trigger exposes the following fields.

• SendOncePer defines the minimum interval that must pass between two fires of the same trigger for the same target record. The interval is anchored to the school's calendar period.
• MaxFiresPerScope caps the total number of fires for the trigger within the defined period, counted across all target records at the school.
• PeriodScopeSchoolId identifies the school whose calendar period anchors both the SendOncePer interval and the MaxFiresPerScope window. The period boundary follows the school's fiscal or academic calendar as configured.

Note: SendOncePer is evaluated per target record. MaxFiresPerScope is evaluated across the school. The two fields are independent and may be used together.

How suppression is evaluated

When a Notification Trigger is scheduled to fire, the system performs the following checks in order.

• The trigger condition query is evaluated against the target Category, producing a candidate set of records.
• For each candidate record, the SendOncePer interval is checked against the trigger's fire history. Candidates that fired within the interval are dropped.
• The MaxFiresPerScope cap is checked against the trigger's fire history for the current period. If the cap has been reached, the remaining candidates are dropped.
• The trigger fires for the surviving candidates, and the fire history is updated.

Example: A trigger with SendOncePer set to one fire per billing cycle and MaxFiresPerScope set to five hundred fires per cycle will fire at most once per target record and at most five hundred times in total across the school within a single billing cycle.

Configuring suppression

• Open the Notification Triggers page in Campus.
• Open the trigger to edit.
• Set SendOncePer to the desired per-record interval.
• Set MaxFiresPerScope to the desired total cap, or leave blank for no cap.
• Set PeriodScopeSchoolId to the school whose calendar anchors the period.
• Save the trigger.

Note: Leaving SendOncePer blank allows the trigger to fire on every evaluation cycle that matches the condition. Leaving MaxFiresPerScope blank removes the total cap. Both behaviors may be appropriate for low-volume triggers, but should be reviewed before saving.

Use cases

• A tuition past-due reminder configured with SendOncePer set to one fire per billing cycle, so the same household receives the reminder at most once per cycle.
• A capital campaign pledge reminder configured with SendOncePer set to one fire per quarter, so donors are not approached more than once per quarter.
• A severe weather closure notice configured with MaxFiresPerScope set to a sensible cap per academic term, so a string of incidents does not generate excessive messages across the school.
• A re-enrollment reminder configured with SendOncePer set to one fire per enrollment season, so each family receives a single reminder per season.

Note: Suppression applies to the trigger itself. If two separate triggers are configured to send similar messages, each trigger maintains its own suppression history.