How to configure Skool notifications without missing what matters
Not every alert comes from the same setting. Review community preferences, followed people and individual threads separately.

Reducing Skool notifications does not have to mean disconnecting from your community. Start by separating general group alerts, notifications generated by following a person and updates about a particular conversation. The official documentation describes these controls separately. Identify where an unwanted alert comes from before switching off unrelated settings and potentially losing updates that still matter to you.
General preferences and email
Open your profile picture, choose Settings and select Notifications. From there, you can change notifications for individual groups, with available options depending on your role. Skool distinguishes the weekly digest of popular posts from the daily email summarising unread activity. It also documents administrator announcements and event reminder emails sent 24 hours before an event begins. These serve different purposes rather than being interchangeable alerts.
People and threads have their own controls
Following a member can generate notifications when they publish. To unfollow someone, open Profile and review Following. For an individual conversation, use the bell on the post: enabling it follows new comment activity, and clicking it again stops following that thread. Our recommendation is to reserve thread bells for unresolved questions or discussions where you genuinely need to see the next reply.
Worked example: a learning community
Luis belongs to two groups and receives more email than he wants. He still needs his weekly coaching reminder and the answer to a technical question. One recommended configuration is to review each group's email preferences, retain the relevant event reminder and enable the bell only on his question. He then checks whether remaining alerts come from followed people. He does not assume changing one group changes the other.
Checklist for reducing noise
- Identify which community and activity type generated the alert.
- Review the available weekly digest, daily activity and reminder preferences separately.
- Check followed people before changing every email preference.
- Turn off the bell for conversations that have already been resolved.
- If you administer the group, retain a dependable way to review membership requests and reported content.
We recommend reviewing changes after several days of normal use. Adjust one source at a time so you can identify what improved without accidentally losing a necessary communication.
Explore PowerUpSkool features to support your community operations.
ContinueSources and documentation
Frequently asked questions
How do I stop notifications from one particular post?
Click that post's bell again to stop following its comments. If alerts continue, also check whether you follow the author.
Turn this guide into work done in your community
PowerUpSkool reads your Skool community and shows you daily who is going quiet, which threads need replies and what message to send. Free to start; Pro with a 15-day trial.
Keep reading
The Skool app: what you can do from mobile and what you can't
The Skool app is built for consuming the community, not managing it. Knowing exactly where that line sits saves you half an hour a day.
How to reduce churn in your Skool community
Nobody cancels out of nowhere. There are three quiet weeks before it, and they can be seen and reversed.
Skool categories: organise your feed around member intent
A category should explain where to post and what to find, not mirror your entire business structure.
Skool sign-in problems: how to recover access
Signing into your account and entering a community are different problems. Identify yours before creating another account.