When we started designing the Community module, the first deliberate decision was to NOT build a Reddit or Discourse clone. The B2B audience does not want that user experience, and if we shipped one we would actively damage the product. Below is why.
Partner-portal vs. classic forum
The classic forum (Reddit, Hacker News, Discourse default) runs on anonymous registration, viral voting-driven sort, and heavy post-hoc moderation. This works extremely well for a consumer audience where opinion diversity and content discovery are the core value.
A B2B partner-portal is different. The user is not an unknown: they are a colleague at a peer company whose employer has a contractual relationship with the vendor. A name and a company name are attached to every post. The controller of a 47-person pharmaceutical-logistics firm doesn't want to argue with an anonymous forum poster they can't even confirm is not at a competitor. They DO want to read how another, named pharma tenant handled the same NAV integration edge case.
So a partner-portal is curated (the admin role is active), identity-verified (the user is approved by their tenant), and contracts-aware (the chat agent knows which plan the tenant is on and answers accordingly).
The hybrid we considered and rejected
We spent two weeks in design exploring a hybrid: identity-verified "official" sections + anonymous "free" sections. We rejected it for two reasons.
First, the B2B audience psychologically does not use free-for-all. Enterprise software buyers don't want to argue with unknown users, no matter how well moderated. The anonymous section would be dead terrain by week four.
Second, the moderation overhead compounded: two rule sets to maintain, two attribution modes, two data-deletion flows. Killing the hybrid idea was simpler.
The 3 forum features we borrow
We're not reinventing the wheel. Three things are textbook forum best practice and we took them:
- Threaded replies. Multiple answers per question, replies to replies. Discussion structure is now standard expectation for B2B users too.
- Search. Postgres full-text + filter (tag / author / date / resolved-flag). It's the one feature every user tries on day one.
- Tagging. Tenant-scoped tag namespace, but with a vendor-curated recommended base set ("finance", "logistics", "erp-migration", etc.) so categorisation stays consistent across tenants for vendor-mediated discovery.
The 5 forum features we deliberately omit
- Anonymous posting. See above: B2B is identity-aware. A peer-company colleague without identity does not produce the trust that makes a forum worth using.
- Upvote-driven sort. In B2B, content value does not always correlate with likability. A solid answer to an obscure technical question might only matter to three people, but it matters fundamentally to those three. Default sort is
most-recent-with-unanswered-priority, nottop-voted. - Karma points. That's the consumer-app model. In B2B your identity IS your company card, not an abstract number. Human credit (peer-marked "Helpful Answer") replaces it.
- Badges-for-volume. We don't want people posting just to unlock a badge. See the gamification post for detail.
- Public DM. Cross-tenant DM does not exist. If two peer tenants want to talk about something, they open a thread. This is deliberately inconvenient: it nudges knowledge into the forum, not into two-person dead ends.