Feature Request: Ability to Hide/Restrict Entire Community Sections & Expose Hidden Status via API
Objective / Summary
Currently, community admins can only hide individual categories, not entire sections. Additionally, the community APIs lack a parameter to indicate whether a category or section is hidden. We need the ability to completely hide or role-restrict entire sections in the UI, alongside API support that accurately reflects these visibility states.
The Problem
-
Administrative Overhead (UI): When we need to retire or temporarily hide an entire section, we are forced to manually drill down and hide every single category within that section one by one. This is tedious and inefficient.
-
Data Inconsistency (API): Because the API does not return a "hidden" status parameter for categories or sections, there is a major discrepancy between what is configured in the backend and what the API pulls. This breaks custom integrations or external dashboards that rely on accurate content architecture.
Proposed Solution
-
Section-Level Controls: Add an option in the community backend to completely hide an entire section or restrict its visibility to specific user roles with a single toggle.
-
API Visibility Parameters: Update the API payload to include a boolean parameter (e.g.,
"isHidden": true/false) for both sections and categories so external applications can respect the backend configurations.
Business Value / Impact
-
Efficiency: Saves administrative time when archiving content, restructuring the community, or managing seasonal/beta sections.
-
Data Integrity: Fixes the inconsistency between backend configurations and API outputs, allowing developers to build reliable, seamless custom community experiences.