Troubleshooting communities
Causes and fixes for the community problems creators report most: missing new-post emails, members who are blocked or not recognized, hidden channels, the feed order and member removal.
This page collects the problems creators report most often while running a community, each with its cause and the steps that fix it.
My members do not get an email when I publish a post
This is the default, not a fault. A new post reaches every member as an in-app notification under the bell icon; the email about new posts is off until a member turns it on. The Notifications tab in the community editor's Settings controls only the weekly digest, not new-post emails.
You have two ways to get a post into inboxes:
- Announce the post. Before publishing, turn on Notify all members under the composer toolbar and click Publish. For a post that is already live, open its ⋮ menu and choose Notify all members…. Confirm with Schedule notification; sending starts after 5 minutes and can be stopped with Cancel on the post's banner. An announcement also reaches members who keep new-post emails off.
- Ask members to turn the emails on. In the community a member clicks their avatar, chooses Profile, opens the Notifications tab and ticks Email in the New posts section, either on the Apply to all channels row or for single channels, and clicks Save.
The full list of notifications and their defaults: Notifications and announcements.
I used Notify all members, but some members got nothing
An announcement is sent once per post and respects each member's own settings, so a few members can be left out on purpose.
| Cause | How to check | What to do |
|---|---|---|
| The member unticked Admin announcements | The member opens Profile → Notifications in the community. | They tick Email (and In-app) in the Admin announcements row and click Save. Their other notifications were never affected. |
| The member already got the regular new-post email for the post | They follow new posts by email, so the announcement did not send a second one. | Nothing. It is one email per person per post. |
| The email was sent but did not arrive | Open Customers, click the History pill (/customers/history/emails), type the address into Filter by email address… and press Enter. | Read the Status of the row. What each status means: Email and login history. |
| The announcement was cancelled or never scheduled | The post's ⋮ menu still offers Notify all members…. | Schedule it again. If the menu item is gone, the announcement was already scheduled or sent, and it cannot be sent a second time. |
Notify all members is disabled while you schedule a post for later. Announce that post after it publishes.
A client paid, but sees "Your access to this community is blocked"
The member's status in the community is Disabled. That happens in two ways: someone switched them off by hand (the Status switch in Edit member, Disable member on their profile, or Remove from community for a person whose access comes from another product), or their access to the product ended and the membership was switched off with it.
When access comes back through a renewal, a new purchase or a manual grant, the membership switches back on by itself. A member who was disabled by hand stays disabled, also after they pay again. To let them in:
- In the community editor open Members list (
/communities/<productId>/editor/members) and click Disabled above the table. - Find the member with Search members....
- Open the ⋮ menu in their row and choose Activate. You see Member activated.
- Ask the member to reload the community.
If the member's access has ended, activate nothing: open their profile in Customers → All customers (/customers), check the Access tab, and have them renew or grant the access again (Grant access manually). More about statuses: Manage members.
A client bought access, but sees "You are not a member of this community"
The client is signed in with a different email address than the one that holds the access. Each address is a separate client, so a purchase made with a typo, or with Apple Pay or Google Pay (which pass the email stored in the wallet), can sit on an address the client does not use to log in.
- Ask the client which address they log in with and which one they gave at checkout.
- In Customers → All customers (
/customers) search for both. Open the record that has the purchase; its Access tab lists the community as a row of type Community membership. - If only that record exists, move it to the right address: Actions → Change email (Change a client's email address). The login moves with it.
- If both addresses exist as separate clients, combine them: the three-dot menu at the top of the profile, Merge customers, keeping the address the client logs in with. Community memberships move to the surviving client (Merge or delete a client).
- Ask the client to log out and log in again on your platform's address.
A member does not see a channel that other members see
A channel a member cannot access is hidden from their channel list, their feed and the post search; they are not told it exists. Open Channels in the community editor (/communities/<productId>/editor/channels) and check the channel against this list:
- The channel is inactive. A channel with Active switched off carries a Hidden badge and only administrators see it. Open the channel and turn Active on.
- The channel is limited to roles. A Restricted badge means Access is set to Only selected roles. The member needs at least one of the ticked roles. With several extra roles, one role that has access is enough.
- The member does not have the role. Open Members list, click the member and read their roles in Member details. Add a role with Edit member, or, when the role should come with a purchase, set Grants role on the right plan in the product's Add-ons & Plans tab (Roles and VIP channels).
- The group limits access. A group has its own access table that applies to every channel inside it, unless the channel overrides it.
- The channel has a level gate. In Settings → Gamification, Level-gated channels can require Level 2+ or higher. Members below the level do not see the channel (Gamification).
After a role change the member sees the channel once they reload the page.
New posts do not show at the top of the feed
Pinned posts always come first. The feed puts pinned posts from every channel above all other posts, so a community with a pinned welcome post in each channel opens with a block of old posts, and the new ones start below it.
- Open the community and scroll the feed past the posts marked with a pin icon; the recent posts follow.
- On each pinned post you do not need at the top, open the ⋮ menu and choose Un-pin from top. This also removes the pin inside the post's own channel.
- Check the sort selector above the posts. Recent activity, the default, moves a post up when someone other than its author comments on it; Latest orders posts by the time they were written.
How the feed is ordered: The community feed and search.
I removed members, but they still count as active customers
Remove from community takes away product access only when the access comes from the community product itself. The confirmation window sorts the selected members into groups, and two of them keep their access:
| Group in the window | What happens |
|---|---|
| Members to be removed | Their access to the community product is revoked. |
| Only community access | They got in through another product that includes the community. They are disabled in the community; their access to that other product, their orders and subscriptions do not change. |
| Skipped members with an active subscription | Nothing changes. Cancel the subscription from the product page first. |
A client counts as an active customer as long as they have access to at least one product. To free the place:
- Open the client in Customers → All customers (
/customers) and go to the Access tab. - Find the product that gave them the community and choose Revoke access in the row's three-dot menu. For many people at once, tick them in the list and use Edit selected → Revoke product access (Bulk actions on clients).
- Check the Active customers meter in Settings → Usage (
/settings/usage).
For a member who pays by subscription, end the subscription first: Cancel or revoke a subscription.
I want to turn off private messages between members
Member-to-member messages are a community setting and are on by default.
- In the community editor open Settings → Access & features (
/communities/<productId>/editor/settings/access). - Turn off Private messages between members and click Save.
The Message buttons and the message composer disappear for members, and existing conversations stay readable with the notice "Private messages are turned off in this community." Your own conversation with each client is a separate channel with its own switches in the inbox settings: The inbox: direct messages.
If your problem is not on this list, write to the Zanfia team: Get help and contact support.
Was this article helpful?

