Granular Unsubscribe Controls for Community Emails

TL;DR

Community email unsubscribes are now granular. A member can opt out of a specific notification type for one community without affecting other communities or platform emails. No action is required from agency owners.

Who this affects

This change affects any HighLevel agency owner or SaaS entrepreneur whose clients use the Communities feature and receive emails from it. If your clients do not use HighLevel Communities, this update is not relevant to your operations. HighLevel has not confirmed who is affected by plan level or sub-account setup.

What changed

HighLevel has implemented granular unsubscribe controls for emails originating from the Communities feature. Previously, if a member clicked 'Unsubscribe' in a Communities email, it could opt them out of all platform email communication. This behavior has been updated.

Now:

• Unsubscribing from a specific notification type in one community no longer affects emails from other communities or the rest of the HighLevel platform.
• The unsubscribe preference applies only to the community that generated the email and the specific notification type.
• When a member clicks 'Unsubscribe', a confirmation page appears, showing the community name and the specific notification type being turned off.
• The member must confirm this scoped unsubscribe preference.
• Future emails matching that community and notification type are stopped.
• All other community and platform emails continue as normal.
• If an unsubscribe link has already been used or has expired, a clear message confirms no settings were changed.
• Disabled notifications can be re-enabled from the member's notification settings.

HighLevel has not confirmed any limits, plan gating, or rollout status for this feature.

Where to find it

HighLevel has not published the specific location where agencies can manage or configure this new granular unsubscribe control. This control is primarily a user-facing improvement to the unsubscribe process within Community emails themselves, rather than a new setting for agency owners to configure. The change is to the behavior of unsubscribe links embedded in Community emails and the subsequent confirmation page a member sees. Members will find controls to re-enable notifications within their personal notification settings.

How agencies will use this

Consider an agency running a HighLevel Community for a client, 'Fitness Hub Pro'. This community sends out weekly 'Workout Challenge' emails and daily 'Forum Digest' emails. A member, Jane, is very active in the forums but finds the daily digest too frequent. She also receives emails from another community, 'Nutrition Experts', run by the same agency.

Under the previous system, if Jane clicked 'Unsubscribe' on a 'Forum Digest' email, there was a risk she would be opted out of all emails from 'Fitness Hub Pro', and potentially even 'Nutrition Experts' or other platform communications. Now, Jane can click 'Unsubscribe' on a 'Forum Digest' email. A confirmation page will appear, clearly stating she is unsubscribing specifically from 'Forum Digest' emails within the 'Fitness Hub Pro' community. She confirms this, and those specific emails stop. She continues to receive 'Workout Challenge' emails from 'Fitness Hub Pro' and all emails from 'Nutrition Experts'. If she later changes her mind, she can re-enable 'Forum Digest' emails via her notification settings within the 'Fitness Hub Pro' community. This reduces member frustration and ensures essential communications are not inadvertently blocked.

Our take

This is a minor but welcome quality-of-life update. The previous unsubscribe behavior for Community emails presented a risk of unintended and broad opt-outs, potentially impacting member engagement across multiple communities or even the entire platform. This update brings the unsubscribe functionality more in line with user expectations and standard email practices. It's a small improvement that reduces friction for community members and mitigates a potential headache for agency owners related to accidental mass unsubscribes. While not a groundbreaking feature, it demonstrates HighLevel is refining existing components. It likely won't impact your daily operations significantly this week unless you've been fielding support requests about overly broad unsubscribes from Communities.