What is the challenge? |
We have several documentation sets in Aha! Knowledge serving different user groups and languages, but right now we can only configure a single base URL for each knowledge base. We need to publish different content (sometimes overlapping) under different subdirectory paths (slugs), such as /portal for portal users, /opcenter for Op Center users, or /en and /es for different languages. Our IT team can't work around this at the DNS or server level. |
What is the impact? |
We can't provide clear, maintainable, and audience-specific links to our users. This limits our ability to support multiple user groups, regions, and languages under a unified domain. We end up with awkward workarounds or too many subdomains, which is messy for both our team and our customers. |
Describe your idea |
Allow us to config knowledge bases that are accessible via custom subdirectory slugs (e.g., https://product.help.domain.com/portal, https://product.help.domain.com/opcenter, https://product.help.domain.com/en, etc.)—not just at the base URL/root level. Each slug should be able to point to a different knowledge base or variant (for user group, product line, or language). This would help us serve differentiated content to specific audiences and languages, all under a clean, unified help domain for the same product. |