Managing email notification preferences

Managing email notification preferences

Understand what Notifications controls

Open Community Settings and go to Notifications to manage the community-wide email notification policy.


This section is important for a superhost, as it helps you decide how actively members should be notified by email and how much communication should happen through inboxes versus in-app or push notifications. These settings help you standardize notification behavior across the community, reduce unnecessary email noise, and create a notification experience that matches your community’s engagement style.

Use this section when you want to:
  1. Control whether email notifications are used at all
  2. Decide whether emails should be sent instantly or as a digest
  3. Reduce noise from high-volume activity such as Community Wall posts
  4. Define a default notification structure for all members

Set community-wide email notification behavior

Open Email Notification Preferences to configure how email notifications should work across the entire community.


The settings you choose here apply at the community level, which helps a superhost create a consistent default notification experience for everyone.

This is useful when you want to ensure that:
  1. Members are notified in a structured way
  2. Email usage matches your community’s communication style
  3. The notification experience does not become too noisy or too quiet by default

Turn off email notifications for the community

If you want to stop email alerts completely, click Turn Off Email Notifications.


This disables email notifications across the community, so members are notified only through:
  1. In-app notifications
  2. Push notifications

This is useful when your community relies more on real-time platform activity than email, or when you want to reduce inbox traffic and keep notifications contained within the product experience.

For a superhost, this is especially helpful in highly active communities where email notifications may otherwise become overwhelming.

Choose how emails should be delivered

If email notifications remain enabled, you can decide how they should be delivered.

You can choose one of these approaches:
  1. Default notifications – Members receive an email for every relevant activity
  2. Disable notifications - Keep email notifications disabled at the community level, while still allowing individual users to enable email notifications for themselves
  3. Digest notifications – Each user receives one email per day with a summary of the day’s relevant activity

Each option gives a different balance between visibility and noise.

Use Default notifications when members should receive immediate email updates for important activity.

Use Digest notifications when you want members to stay informed, but without sending emails throughout the day.

Use the member-controlled approach when you want the community to stay quieter by default, while still allowing individual users to opt in to email notifications based on their own preference.

This gives a superhost flexibility to set the right communication rhythm for the whole community.

Reduce email noise from Community Wall activity

You can also fine-tune the policy further by disabling email notifications specifically for Community Wall activities.

This is especially useful when the Community Wall is very active, and you want to avoid sending an email for every feed-based post or comment.


For a superhost, this helps reduce email fatigue while still keeping other types of notifications active where they matter more.

This setting is helpful when:
  1. Community Wall activity is frequent
  2. Email volume needs to be reduced
  3. Members should stay informed through in-app and push channels instead of frequent feed emails

Understand how member preferences still apply

Even after setting the community-wide email policy, individual members can still fine-tune their own notification preferences if needed.

This means the superhost defines the default email behavior for the community, while members may still have some control over how they personally receive updates.

This creates a balance between community-wide notification governance and personal notification flexibility.

In practice, this helps a superhost establish a sensible default structure without forcing every member into exactly the same email experience.

Notifications are an important part of member experience. When configured thoughtfully, they help members stay informed without overwhelming them, and help a superhost maintain the right level of communication across the community.