Receive campaign publish-request notifications

For the request-to-publish path, enable Campaign Submission Notifications on the fundraising administrator record and verify that the administrator can launch the specific campaign. The service checks both the subscription and campaign-scoped launch permission, then resolves a confirmed non-guest, non-tracking-link user by email.

A broad role or subscription alone is insufficient if the other checks fail. Confirm the correct school, campaign scope and registered email before investigating delivery. This does not confirm that every legacy submission or idea notification uses identical rules.

Select recipients for new idea submissions without changing roles

The new idea-submission notice checks both Campaign Submission Notifications on the fundraising administrator and permission to manage idea submissions. To route these notices to two eligible users, enable that subscription for them and disable it for other users who should not receive the notices. The permission still must be present; subscribing an otherwise ineligible user does not grant it. This preference is also used for campaign publish requests, so review that shared impact rather than treating it as an idea-only toggle.