Skip to main content

​
Policy summary

  • Canonical user-facing knowledge experience: /knowledge_base
  • Legacy surface: /knowledge

​
What this means for customers

  • Follow knowledge setup and operations docs that reference Knowledge Base (/knowledge_base).
  • Treat /knowledge as legacy compatibility surface where still present.
  • New workflows and support runbooks should reference /knowledge_base only.

​
Deprecation posture

  • /knowledge may still exist for backward compatibility.
  • Documentation is standardized on /knowledge_base to avoid contradictory guidance.
  • Any migration timeline updates will be published in release notes.

​
Support guidance

  • If a customer is using legacy paths, guide them to /knowledge_base workflows first.
  • Escalate only if required behavior exists only in legacy path and cannot be replicated.