# Private vs public community: what you gain and lose Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: Private vs public community: gains and losses Meta Description: What a private community gives you, what a public one gives you, and the middle option for support teams: public by default, private per question. URL: https://forumcat.com/blog/private-vs-public-community An online customer community can be public or private. A public one is readable by anyone, including search engines. A private one sits behind a login, so only members get in. For customer support, public usually wins, because one answer keeps helping the next person who has the same problem. Private wins when named members need to talk candidly. Most support teams want public threads with the option to make one question private. This post explains what each model gives you, what each one costs you, and how to pick. It is about software for customers, not about social networks. ## What public and private mean here Public means a visitor can read and search the community without an account. They arrive from a search engine or a link, open a thread, and read the answer. A thread is one question with its replies. No sign-up screen stands in the way. Private means every page requires a login. A person has to be invited, or approved, before they can read anything. Search engines see nothing, because a search engine cannot log in. Most communities still ask people to sign in before they post. That is normal in both models. The difference is reading, not posting. Put one test to any tool you look at. Check whether a stranger can read a thread without an account. ## What you gain with a public community A public answer keeps working after you write it. That is the whole case for public, and it is a strong one. One reply can serve hundreds of readers over a year. The customer who asked reads it once. Everyone with the same problem reads it later, at whatever hour they are stuck. You wrote it once, in office hours, and it answers people while you sleep. Public pages can be found in search. Somebody types their problem into a search engine and lands on your answer. They never open your contact form, because they did not need to. New customers can read before they buy. Someone deciding on your product can see how questions get answered and how fast. Prospects reading your support answers is a good thing. A prospect is a person thinking about buying from you. Honest answers in public build more confidence than a page of claims. ![A Forumcat portal as a signed-out visitor sees it, listing questions with a sign-in link in the corner](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/40-anon-home-1788501903071-compressed.png) _Public means this page loads before anyone logs in._ Public also lowers the cost of every future answer. Each solved thread is a page you can link the next time the question arrives. Over a year, that pile of pages does real work. The same argument applies to answering in [public instead of by private email](https://forumcat.com/blog/public-answers-beat-private-email). ## What you lose with a public community Public costs you privacy, and you should count that cost with open eyes. Nothing on the forum is confidential. Anything a customer pastes can be read by anyone, including detail they did not mean to share. Complaints are visible. An unhappy customer writes in public, and the thread sits there while you work on a fix. Your competitors read it. They will see your bugs, your gaps, and the questions your product raises most often. Bad answers are visible too. A wrong or rushed reply is on a page anyone can find. The honest counter is that a support inbox has the same complaints. They are just hidden from you and from everyone else. A public complaint with a good public answer often reads better than silence. You lose the ability to keep problems quiet. The problems were already there. ## What you gain with a private community Private buys you candor. Candor means people say what they really think, because the room is small and everyone in it is known. Behind a login, people share things they would never post to the open web. They paste account numbers, revenue figures, and screenshots of internal tools. They complain in front of peers instead of in front of search results. They ask questions they would be embarrassed to ask in public. That is worth a lot for specific groups. A beta group testing unreleased features needs to talk about things you have not announced. A beta is an early version given to a few customers. A paid member group, a partner program, and a customer advisory council all work the same way. An advisory council is a small set of customers who meet to give feedback on your plans. Those rooms have a real job. The job is trust among a named few. ## What you lose with a private community A private answer helps one room, once. It never builds up into anything. Nobody finds it in search, because search engines cannot log in. It does not lower your support volume, because the people who email you are not in the room. It dies when the member leaves, because the next customer with that question will never see it. There is an ongoing cost too. Someone has to create accounts, send invitations, and chase people who never accepted them. Someone has to review access, which means checking who still belongs there when jobs change and contracts end. That work is small each week and constant forever. ## The middle option most support teams want Public threads by default, with the ability to make one question private, covers almost every support case. Here is the split in practice. The question about how refunds work is public, because it helps everyone. The question about this customer's refund on invoice 4471 is private, because it is one person's business. Private at the thread level means visible to the asker and staff only. The rest of the forum stays open to the web. Nobody else sees the thread, and a search engine never indexes it. Index means a search engine stores the page and can show it in results. ![A private question in a Forumcat portal as a staff member sees it, marked private](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/06-thread-private-staff-1788501892480-compressed.png) _One thread can be private while the rest of the forum stays public._ Used well, this keeps the public side clean. Account detail leaves the open pages. The answers that help strangers stay where strangers can find them. Most teams choosing [a customer community platform](https://forumcat.com/community-platform) are really looking for this shape. ## How to choose, in three rules Three rules settle almost every case. If the answer would help a stranger, make it public. Billing rules, setup steps, error messages, and product limits all fit here. Write them once in the open. If the answer contains one customer's data, make it private. Account numbers, invoices, personal addresses, and anything about their specific plan belong out of public view. If almost every answer contains one customer's data, you want a help desk, not a forum. A help desk is a tool that handles private one-to-one cases through email or a portal. Some businesses genuinely have no repeatable public answers. Their questions really are all individual. A forum will stay empty for them, and that is a fair reason to skip it. ## Where Forumcat fits, and where it does not Forumcat is public by default. A portal is a public question-and-answer site on your own domain or a subdomain. Customers read and search it without an account. Asking a question needs a sign-in, by magic link, six-digit email code, or Google. A magic link is a sign-in link sent to email, so nobody invents a password. A question can be made private, so only the asker and staff can see it. That covers the account-specific case described above. Forumcat is not built for a fully closed member community. The public, searchable pages are the point of it. If you need every page gated to invited members, pick a different tool. If you want [a hosted support forum](https://forumcat.com/support-forum) that is public with private questions where they are needed, that is the shape Forumcat has. It is $9 one time on a Forumcat subdomain, with a 7-day free trial and no card. Keep reading: [how to build a customer community](https://forumcat.com/blog/build-a-customer-community) and [a Discord alternative for customer communities](https://forumcat.com/blog/discord-alternative-for-customer-communities). ## FAQs Q: What is the difference between a public and a private community? A: A public community can be read and searched by anyone, with no account. Search engines can find its pages and show them in results. A private community requires a login on every page, so only invited or approved members see anything. Both usually ask people to sign in before posting. Q: Should my customer community be public or private? A: For customer support, public is the better default. Answers you write once keep helping people who arrive later from search. Choose private when the point of the room is candid talk among a named few, such as a beta group or an advisory council. Many teams run public threads and mark individual questions private when they involve one customer's account. Q: Is a private community better for support? A: Usually not. Support questions repeat, and a private answer helps only the people already in the room. It never reduces the number of emails you get, because the people emailing you are outside. Private is better for confidential feedback, not for answering the same question many times. Q: Can a community be part public and part private? A: Yes, at the level of a single question. A thread can be visible to the asker and staff only, while the rest of the forum stays open to the web. That is different from a private area for a group of members, which is a separate feature that not every tool offers. Q: Do private communities help SEO? A: No. SEO means getting your pages to show up in search results. A search engine cannot log in, so it never sees pages behind a login. Only public answers can appear in search results. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. ---