Separate permission for publishing to a KB

What is the challenge?

Knowledge base content can be stored in the same workspace the product team uses to set strategy, track features, etc.

However, just because someone has the ability to edit Roadmap data does not mean they should have the ability to publish public documentation.

How would you solve it?

Add a publishing permission that can be applied to a user.

What impact would it make?

Allow for the KB content to be managed in the product workspace while maintaining publishing control.