Category access inherited to sub-categories
under review
Kasper Ahrensburg
Today when assigning access to roles to specific categories, this access is not inherited to sub-categories. This puts a huge limitation to the use of differentiated access for different security groups, because new sub-categories will not automatically be included in the security group.
If access to a particular category could be automatically inherited to sub-categories - both existing and any future sub-categories, this would greatly expand the use of using security groups.
Log In
D
D360 Product Management
Merged in a post:
Nested categories don't inherit permissions
J
Jason Massae
When applying permissions to a first-level category in the Documentation area, articles below that first-level category inherit the category's permissions.
This issue is with sub-categories and articles below sub-categories; they do not inherit the permission, but do show the inheritance.
To grant permissions to sub-categories and articles below, you have to go into the reader groups and select the sub-categories.
Request: Sub-categories inherit permissions from the parent category. This will make permissions management much easier and is the expected result. This is how normal file system management would operate. If permissions need to be excluded, you can simply deny access for a specific category or article.
Mohamed Shakheen
Hi Jason
Thank you for bringing this to our attention.
Currently, when permissions are applied to a first-level category, the articles directly under it inherit those permissions. However, sub-categories and the articles within them do not automatically inherit the same permissions, even though the UI indicates inheritance. This requires manually assigning access for sub-categories through the reader group settings, which adds complexity to permission management.
We understand that having sub-categories and their articles automatically inherit permissions from the parent category - similar to how file systems manage inheritance - would make access management more intuitive and efficient.
We plan to address this behavior as part of the Team Accounts and Reader Management revamp roadmap item. Once it is considered for development, we’ll share an ETA update with you.
G
Gary Kimmelman
This was originally requested in 2021 and still has been implemented.
In March 2025 D360 Product Management said it's been prioritised on the roadmap, however it's not October 2025 and we've still had no update.
Can we can get an update please
N
Nilesh Kirti
Clare Green
D
D360 Product Management
Hi Kasper, Thanks for sharing the feedback.
This has been prioritized in our roadmap. We will keep you updated on the estimated timeline.
Chaz Gauchay
D360 Product Management Any roadmap status update for this feature? This limitation is a growing pain point for our team and would love to have it resolved. Thanks! cc Giselle Magat
Kesavan M
Adding Paul Latoza to this request. As they are looking for a similar feature within the widget’s content access selection.
Jonas Pommerening
Repeating and adding to what Alexander Gaeta said:
When managing category access for reader groups, you must select all sub-categories for those reader groups to have access.
When adding new subcategories, these are not "selected" by default (i.e., group base access is not added automatically).
Consequently, users will not get access to those new categories or articles within them, until access has been granted on the group level.
HOWEVER, when you look at those categories and articles within them (Security -> Knowledge Base Site Access Control) it does look as if group access from a top-level category is Inherited (which it is not).
j
justin severn
Talked to Sid today about this. This feature needs to be included.
D
D360 Product Management
Merged in a post:
Consistency for category inheritance
Alexander Gaeta
When editing content permissions for a team account group, if you click a top-level category, all of the nested sub-categories will “inherit” the permission and appear for the user (so you don’t need to individually click them all).
For Reader groups, however, this is NOT the case. Admins need to individually click each and every sub-category (there is no inheritance), making it messy to maintain as the content of your KB grows (e.g. if a new sub-category gets added by a contributor, I have to then turn it on manually for the reader group).
Hoping to get a toggle button to turn inheritance on/off for categories, or just match the reader group behavior to the current team account group behavior.
Felix DUSSER
This feature is essential for us as well. The management of rights between Team Accounts and Readers differs significantly. Team Accounts inherit rights to sub-categories, whereas Readers do not. As a result, we have to manually update the rights multiple times per week to ensure Readers can access newly created folders. Implementing inheritance for Readers would resolve this issue entirely.
Load More
→