How do I customize the notification settings?

Hana Park Hana Park 3 weeks ago Resolved

I'm getting email notifications for every reply in spaces I've joined. Is there a way to set a daily digest instead? I looked in profile settings but couldn't find it.

Running the latest version on WordPress 6.9 with the BuddyX theme.

3

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

For what it is worth, the same approach works with the PMPro adapter — the membership side is identical from here.

Trust levels are earned automatically through participation, so there is nothing to configure per user. If you want to grant an ability sooner, assign a space role instead — that takes effect immediately and is independent of trust level.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

This deserves more votes. It is a small change with an outsized impact on day-to-day use.

Strong agree. Good defaults beat a wall of toggles every single time.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

Strong agree. Good defaults beat a wall of toggles every single time.

This matches my experience exactly. The hard part is staying consistent once the initial novelty wears off.