Per-document access control in knowledge bases

What is the challenge?

Today, users can create separate knowledge bases for public consumption vs private consumption (via SSO or password), but they cannot create a single knowledge base that contains and manages access control of both types of information

What is the impact?

Knowledge base creators must create separate knowledge bases to manage a mix of public and access-protected information

Describe your idea

Allow for password access at the document or folder level within public knowledge bases