Practical guide

Help members choose notifications without promising delivery

Last materially reviewed 2026-09-28

Quick answerExplain notification choices and a dependable way to find essential information; do not equate sending with reading.
What to know

Separate the channels

A community can present information in the product, through email or through device notifications. Member preferences and device settings can affect the experience. Explain which location is authoritative for essential dates and instructions. A notification is a route to that information, not a guarantee that every member has received, noticed or understood it.

What to know

Let the member choose

Provide a short route to the actual personal settings and explain the practical trade-off between more alerts and less interruption. Do not change someone’s preferences without applicable authority. Avoid telling every member to enable every channel as a condition of being considered engaged. The best setting depends on the person’s needs and how the community communicates.

What to know

Design for a missed alert

Maintain an easy-to-find event or update index. Put material changes there even when an announcement is also sent. For an important access problem, use the agreed support process rather than assuming another broadcast will fix it. Record whether the member found the information, not merely whether an administrator generated another message.

What to know

A fictional missed meeting

A participant does not see a push notification and misses a changed meeting time. The group checks the authoritative event page and improves the route from its welcome area. It may explain notification settings, but it does not blame the member or claim guaranteed future delivery. The repair reduces dependence on one alert channel while preserving the person’s own notification preferences.

What to know

Before you close this task

For essential updates, tell members where they can look without waiting for an alert. Check that the route is visible from the ordinary entry page and does not require a special administrative role. This makes the communication plan more resilient without demanding a particular device, app or notification preference from everyone.

Continue when useful

Next: First visit

Welcome an existing member back to their community before introducing every feature of the new platform.

Open First visit →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Host notifications — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28
  2. Personal settings — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28