Section-level access and privacy controls

It would be useful if Access & Privacy settings could be configured independently for each section of a Sleekplan portal, rather than applying one privacy setting to the entire portal. Our use case We have different audiences and purposes for different parts of our portal. For example: Changelog: We want this to remain completely public. We use it as an outward-facing, promotional way of demonstrating that the product is actively developed and continually improving. Roadmap: We want this restricted to customers. It contains information about where the product is heading that is useful to customers, but that we don’t necessarily want competitors to see. Wishlist: We also want this restricted to customers, as this is primarily a space for customers to suggest, discuss and vote on future improvements. At the moment, the overarching privacy setting means having to choose between making everything public or restricting everything. Suggested improvement Allow administrators to configure Access & Privacy per section, potentially with a global default that individual sections can override. Why this would be useful Different parts of a product portal naturally serve different audiences. A changelog can be a valuable public marketing and communication tool, while a roadmap and wishlist may contain commercially sensitive information intended specifically for existing customers. Section-level controls would let us use Sleekplan for both purposes without having to expose customer-focused product planning publicly or hide content that we’d actively like prospective customers and the wider market to see.