Automatically Remap Links in Notes when Featured in other KBs

When creating customer-specific “featuring” Knowledge Bases (KBs) from a source KB (e.g., selecting folders A and B), internal links inside articles keep pointing back to the source KB instead of the customer’s featuring KB. Also, today, links can only be edited in the original/source document, so there’s no way to ensure links resolve within each derived KB version.

I have emailed with the AHA Customer Success about this already and they recommended adding an idea.

This causes confusing navigation because users who expect to stay in their customer-specific KB are redirected to the source KB (and potentially to content that doesn’t apply to them). It also breaks the modular documentation experience, since curated KBs based on purchased modules can inadvertently link to articles outside a customer’s entitlements or intended doc set. Finally, it creates a maintenance and scalability problem: managing multiple customer KB variants becomes error-prone because link behavior can’t be controlled per featuring KB without changing the original source content for everyone.

Implement an Aha-side link rewriting/mapping solution so that links embedded in featured/copied articles are automatically remapped to the corresponding article within the same featuring KB.

How it should work (conceptually):

• When a featuring KB is generated (or synced), the system builds a mapping between “source article IDs/URLs” and “featured article IDs/URLs.”

• Any internal link in featured content that targets an article included in the featuring KB is rewritten to the featured version of that target.

• Example: If folders A and B are featured from the source KB, and an article in A links to an article in B in the source, then in the featuring KB that link should go A -> B within the featuring KB, not to the source KB.

Expected behavior:

• Links stay within the same KB context whenever the destination exists in that featuring KB.

• If a link points to an article not included in the featuring KB, the system can either:

  • keep the original link (current behavior), or

  • optionally flag it / provide a warning (nice-to-have).