Plans supporting content access settings in the knowledge base portal
| Professional | Business | Enterprise |
|---|---|---|
You can control access to your knowledge base content at the project, workspace, or language level. Team accounts and groups can have access enabled or restricted at each workspace or language level based on your requirements.
Managing content role & access
To manage content role and access,
From the Knowledge base portal, navigate to Settings() > Users & Security > Content access.
You can view all the workspaces and languages available in the project.
The Manage content access section is on the right side of the screen. It displays the existing content access settings for your project's team accounts and team account groups. From here, you can review and manage access permissions to ensure the right users have the appropriate level of access.
On the Manage content access section, hover the Team accounts or groups, and three icons appear:
Edit (): Modify the content access for a team account and click the Save() icon to apply changes or Cancel() to go back.
Deny (): Restrict access to specific content for the team account.
Remove (): Delete the team account from the access list.
Select the checkboxes next to team accounts to apply bulk actions such as edit, deny, or remove.
Click the required icon to perform the respective function.
You can filter the Team account data available based on Project, Workspace, and Language on this page using the Filter option on the top right or by clicking on the tree-view workspace and language selection displayed on the left side.
Click the Assign project access button to assign complete project-level content access to any existing Team accounts and Team account groups.
The Assign project access: Complete project popup appears.
Click the Change content role dropdown to choose one of the content roles: Editor, Draft writer, and Reviewer.
The Content access field will be set to Project level by default.
NOTE
If a user belongs to multiple reader groups with access to the same content, and one of those groups has restrictions, the restriction will take precedence. This means the user will be denied access to the content, regardless of the permissions granted by other reader groups.
Block inherited accounts
The Block Inherited Accounts toggle becomes visible only when you select a specific workspace and language from the tree-view on the left.
When enabled, this toggle prevents all inherited and future team accounts from accessing the selected workspace or language. However, your team account will retain access since you performed the block inheritance.
For more information, read the article on Block inheritance.
FAQ
If a reader has two accounts with the same email ID, one with the standard login and the other with SSO credentials, will their content access collapse or be overridden?
No, if a reader has two accounts with the same email ID, one with the standard login and the other with SSO credentials, each account will maintain its own content access determined by the assigned roles and permissions.