GoHighLevel community comments are controlled at the individual post level. When you create or edit a community post, the Allow comments setting determines whether members can add replies to that post.
That gives community managers a simple way to separate announcements from discussions. You can disable comments when a post should remain clear and authoritative, then leave comments enabled when you want questions, feedback or peer interaction in the same thread.
The important operational choice is not simply whether comments are on or off. It is deciding what job each post serves, who owns the resulting conversation and where members should go when they need help. A consistent rule makes a community easier to navigate and reduces duplicated or misplaced questions.
What the GoHighLevel comment setting controls
The comment setting belongs to the community post rather than acting as a single global switch for every post in the community. This means the person publishing or editing a post can choose the appropriate conversation mode for that item.
- Comments enabled: Members can use the available reply or comment control to participate in the post discussion.
- Comments disabled: New replies are not available on that post.
This distinction matters because a community usually contains several different types of content. A policy update, a weekly question, a course announcement and a troubleshooting discussion should not necessarily have the same interaction model.
A community post should have one clear purpose: inform members, collect responses, or support an ongoing discussion. The comment setting should match that purpose.
How to disable comments on a GoHighLevel community post
Use the following sequence when a post should not receive new replies:
- Open the relevant community: Go to the GoHighLevel community that contains the post.
- Open the post editor: Create a new post or select an existing post for editing.
- Find the comment control: Locate the setting labelled Allow comments in the post editor.
- Turn the setting off: Switch off the control so members cannot add new comments to that post.
- Save or publish the post: Apply the change by saving the update or publishing the new post.
After the change is saved, members should no longer have the normal option to add a new reply to that post. If the post already has discussion attached to it, review the member-facing result in the current GoHighLevel interface so you understand how existing comments are displayed.
Turning comments off closes a conversation channel. It does not automatically create a better place for members to ask questions, so the post should explain where follow-up questions belong when that information is needed.
How to enable comments on a GoHighLevel community post
To open a post for member discussion, use the same post-level setting:
- Open the community: Navigate to the community where the post is located.
- Open or create the post: Edit an existing post or begin a new one.
- Locate Allow comments: Find the comment control in the post editor.
- Turn the setting on: Enable the option so members can reply.
- Save or publish: Update the post or publish it to apply the setting.
Enabling comments creates an open discussion space, but it also creates a small operating responsibility. Someone should know which questions need an answer, which replies are off-topic and when a discussion should be closed or redirected.
Choose the right comment mode for each post
A practical way to manage comments is to classify the post before publishing it. The following three-mode model keeps the decision simple.
Inform members
Use disabled comments for official announcements, rules, deadlines, policies and instructions where replies would make the information harder to find.
Invite participation
Use enabled comments for questions, feedback, peer support, challenges and discussions where member input is part of the intended outcome.
Some posts will change mode over time. For example, a launch announcement may begin with comments enabled while questions are being collected, then be edited with comments disabled once the information is final and a separate support thread is available.
When disabling comments is useful
Disabling comments is usually appropriate when the post represents a stable business message rather than an open conversation. Common examples include:
- Important announcements that members need to read without scrolling through replies.
- Community rules, policies or terms that should remain easy to locate.
- Time-sensitive instructions where questions belong in a dedicated support thread.
- Completed campaigns, events or challenges where the discussion period has ended.
- Repeated announcements that attract the same questions across multiple posts.
Disabling comments can reduce clutter, but it should not be used to hide unresolved issues. If members are likely to need clarification, include a clear instruction such as where to ask the question, which post to use or who owns the response.
When keeping comments enabled is useful
Comments are valuable when the post is designed to produce interaction. Leave them enabled for:
- Questions of the week and member prompts.
- Product or program feedback.
- Course discussions and lesson follow-up.
- Peer support and experience sharing.
- Event participation, challenges and progress updates.
For an enabled discussion to remain useful, the original post should set expectations. Explain what type of response is wanted, whether members should reply in the same thread and whether a moderator will summarize or close the discussion later.
A comment-enabled post is not just a content setting. It is a commitment to provide a place for responses and a visible owner for the resulting conversation.
How to manage comment quality and ownership
The Allow comments toggle controls access to the discussion, but it is not a complete moderation or support process. A well-run community also needs basic ownership rules.
Give each discussion a clear owner
For important posts, identify the person or team responsible for reviewing replies. Ownership does not mean answering every message immediately. It means someone knows which responses need attention and what should happen next.
Use one thread for one question type
If members ask about billing, technical use and program content in one announcement thread, the conversation becomes difficult to search and maintain. Direct different question types to separate posts or support channels when appropriate.
Close discussions deliberately
When a deadline passes or an answer has been finalized, edit the post and consider disabling comments. If members still need help, explain where the next discussion should take place.
Review the member experience
After changing the setting, check the post as a member would see it if your account structure allows that. Confirm that the post communicates whether replies are available and that any alternative support path is understandable.
- Is this post an announcement, a question or an ongoing discussion?
- Should members be able to add new replies?
- Who owns the comments if replies are enabled?
- Where should members go if comments are disabled?
- Will the post still be useful after the current campaign or deadline ends?
Limitations of post-level comment management
The GoHighLevel control described here is a simple per-post choice. It should not be confused with a full community governance system.
- It does not replace a documented moderation process.
- It does not by itself classify questions, route requests or assign follow-up work.
- It does not make every post in a community follow the same commenting policy.
- It does not automatically tell members where to continue a conversation after comments are disabled.
If your community is also part of a wider customer or member operation, define how important questions move from the community into the system where they are owned and tracked. For example, a question that requires account research may need to become a support request or CRM activity rather than remaining in a public thread.
This is where a broader CRM architecture and workflow design approach can help connect community conversations with ownership, follow-up and reporting. The goal is not to add automation to every comment. The goal is to make sure meaningful work does not disappear inside an unowned discussion.
Example: separating an announcement from its discussion
Imagine a membership community publishing an announcement about a new program deadline. The announcement contains the date, eligibility rules and required action. Comments are disabled so the key information remains easy to scan. The post then directs members to a separate question thread where comments are enabled.
In this example, the two posts have different jobs. The announcement is a stable reference point. The question thread is an active conversation with an owner. Separating them makes the member experience clearer and allows the team to close the discussion without changing the official announcement.
If the organization later finds that the same questions are appearing repeatedly, it can update the announcement with clearer instructions or create a structured support workflow. Adding more tools is not automatically the answer. The first step is understanding the repeated question and deciding who should handle it.
Operational observations for GoHighLevel community managers
A comment toggle is a workflow decision, not merely a publishing preference.
An announcement should not become the default support queue just because it is the most visible post.
When comments are enabled, ownership of the conversation should be visible before the post is published.
Disabling comments improves clarity only when members have another clear route for unresolved questions.
For teams managing several connected processes, GoHighLevel community settings should be considered alongside the rest of the operating system. ConsultEvo works with organizations on systems, CRM, automation and AI implementation with a process-first approach. The useful starting point is the member journey and the ownership logic, not a new tool or automation for its own sake.
Frequently asked questions
Where do I manage comments on a GoHighLevel community post?
Comment settings are managed in the post editor. Open or create the community post and use the Allow comments setting before saving or publishing the post.
How do I disable comments on a GoHighLevel community post?
Open the relevant post for editing, turn off Allow comments, and save or update the post. Members should then be unable to add new replies to that post.
How do I enable comments on a GoHighLevel community post?
Edit the post, turn on Allow comments, and save or publish the update. Members can then use the available reply or comment control.
Can I control comments for an entire GoHighLevel community with one setting?
The setting described here is applied at the post level. Each post can therefore have its own comment state, so a community may contain both announcement posts with comments disabled and discussion posts with comments enabled.
What should I do if comments are disabled but members still have questions?
Tell members where to continue the conversation, such as a dedicated question post or support process. Disabling comments should close one discussion channel without removing the next step for members.
Make community conversations easier to own
If community discussions, CRM follow-up and internal workflows are becoming difficult to manage, ConsultEvo can help clarify the process, ownership and system design before introducing automation.
