Hi Sam -- thanks for your response. The use case is that at my company we organize our knowledge base around knowledge type, rather than team. We do this to encourage cross-functional thinking.
I'd like to structure Questions the same way -- but since people are so prone to thinking in teams, we want to restrict topics to require that people center on a topic. The way the software works right now is counter to this -- if someone types in the name of a team (instead of selecting a featured topic), then it shows up as a trending topic, then the next person uses it, and soon it's showing up both in our Questions list, and also when someone is going to ask a question (so actually, on the same interface as a "featured topic" -- partially why that feature doesn't help).
Another problem is that is someone creates a new topic, nobody is going to see that unless they're watching the ENTIRE Questions feature. Since we're relying on email to drive traffic to our instance, we don't want to bombard people by asking them to watch the whole forum, and we also want people to have a good experience (i.e., have their question answered) when they first use it.
The ability to restrict who can create a topic would be a huge step forward and would really enable us to both scale and increase adoption of our instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.