Description
Help Centers are currently limited to three levels of collections. For a Help Center that serves more than one audience and covers several product areas, that limit gets used up quickly.
A common setup looks like this:
- Level 1: audience (for example, "For admins" and "For end users")
- Level 2: product area
- Level 3: task or topic within that area
That leaves no room to group related product areas together. When a product brings several existing features under a new parent area, the Help Center can't mirror it. We either flatten collections that work well as they are, or add a naming prefix to several top-level collections to fake the grouping. Neither matches how customers find their way around the product.
What would help
- At least one more collection level (four in total), or a configurable limit.
- Or a lightweight grouping option, such as a section or heading inside a collection that can hold sub-collections, without counting as a full level.
Why it matters
- The Help Center can mirror the product's own navigation, so customers find articles where they expect them.
- Teams can restructure when a product changes without breaking or flattening existing collections.
- Clearer hierarchy should also help AI answers and search pull from the right place.