Discourse for Private Communities


(Erlend Sogge Heggen) #1

Originally published at: Discourse for Private Communities

There are many reasons why a community might be private: Paid memberships; a company intranet; a sensitive subject matter; beta testers; a grassroots movement building momentum before going public. Whatever the reason, we want Discourse to function well in private contexts. We reached out to 23 private Discourse communities to learn more about their use…


(Dave McClure) #2

An opportunity I see for making Discourse continue to improve for private communities (particularly company intranet sites), is to have more integrations with other private systems

The slackdoor plugin gives Slack some ability to unfurl links to private discourse instances, but going the other way would be cool too (i.e., having the ability to Onebox links to private Slack instances).

Same goes for things like Google Docs. The current solution is better than it used to be, but it’d be great if Discourse could be configured to have the necessary authorization to actually fetch and onebox private docs.

These are just a couple examples that come to mind - I imagine each private instance would have their own thoughts on what integrations like this would be valuable.