Agents can view internal KB articles when KB is set to another domain.
Actual behavior:
Agents cannot view internal KB articles, the opened KB says “Page not found”.
Steps to reproduce the behavior:
Zammad is running under the domain like “zammad.example.com”.
Set up a custom domain for the Knowledge Base (KB) like “kb.example.com”.
Everything is good except this issue:
When an agent login zammad.example.com, and try to view internal KB articles, he cannot see articles. The opened webpage says “Page not found. The page you were looking for does not exist.”.
If we set up KB custom url like “zammad.example.com/kb”, no such issue.
I think this is because the login session doesn’t work among different domains.
Yeah I did understand that.
My question is why your agents switch the interface from internal ticket system view to public help page? It’s not required at all…:
Just as MrGeneration said, internal answers are not shown.
A workaround I find is to directly use original url https://zammad.example.com/help. This url still available even you have set up a custom domain kb.example.com