Hi Matt, I appreciate the candid feedback on the idea. Thank you.
How about this use case? A Discourse customer wants to do a rebranding of their community and hires Contractor to do the work. Contractor has a great reputation, brilliant work, etc. It seems reasonable to trust the Contractor to have admin status on the Discourse site. The Contractor also hires subcontractors to assist with the work of adding graphic files, changing CSS, etc. Now the Discourse customer has given full, unlimited access to their Discourse installation to three people, simply to rebrand their community site.
That’s a huge risk. If any one of those three people has a hidden reason to take advantage of the trust they have, this could be a disaster. Leaked financial documents, legal documents, private messages, strategic conversations, merger plans, etc. You probably know better than I do the near-daily headlines of hacks, leaks, sabotage, etc. across the software industry.
I think from an enterprise perspective, managing security risks is at the forefront of the C-suite. Here’s the internal organization conversation:
- Let’s use Discourse for private conversations, we can have closed groups and Categories
- But who has access to all the discussions?
- Well, anyone we give admin access too.
- Ok, who gets that?
- Well, the community manager, the Discourse team, and any contractors we need to hire.
- We don’t trust all of those people to have access to all of our company’s internal discussions. How can you guarantee that all of our company information will remain secure?
So what’s the best response to that question?