Content access levels assigned to a user (Workspace/Language, Category, or All) apply identically to both the knowledge base portal and the published knowledge base site. There is currently no way to give a user broader visibility on the published site than in the portal, or the reverse, without assigning them a second content role.

Suggested Enhancement: Allow content access levels to be configured separately for the knowledge base portal and the published knowledge base site, similar to how article-level access control already separates portal and site visibility for Editor and Contributor roles.

Customer Benefit: Users could see exactly the content appropriate to each surface, with less setup effort and fewer role or account combinations required to reach the intended visibility.