# Why are we unable to create subcats for mods within the Staff category?

**URL:** <https://meta.discourse.org/t/why-are-we-unable-to-create-subcats-for-mods-within-the-staff-category/148578>\
**Category:** Product Support\
**Created:** [20 april 2020 om 07:55 UTC](https://meta.discourse.org/t/why-are-we-unable-to-create-subcats-for-mods-within-the-staff-category/148578 "2020-04-20T07:55:18Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [17 juli 2020 om 06:23 UTC](https://meta.discourse.org/t/why-are-we-unable-to-create-subcats-for-mods-within-the-staff-category/148578/20 "2020-07-17T06:23:53Z")

</div>

But it has nothing to do with backwards compatibility. In this topic you’re the _only_ person pushing for a change. What you’re proposing still requires development time, still requires testing and still requires maintaining. Thousands of installations working with the existing config means there are also thousands of admin/moderation teams who don’t mind the as-is setting.

This topic is months old. You could have implemented the _correct_ way to do this back in April, why would you expect CDCK to finance a change to their software, something which has worked this way for seven years, for a _single_ site? Why should anyone do **anything** if you’re unwilling to make the simplest change to your own configuration? Your unwilling to follow guidance doesn’t encourage action by anyone else.

There’s nothing special about the staff category, as suggested months ago you could create a _different_ category with the appropriate permissions. Problem solved.

It’s **vastly** simpler for your to implement a small change on your community, than **any** of the above.

---

_[View the full topic](https://meta.discourse.org/t/why-are-we-unable-to-create-subcats-for-mods-within-the-staff-category/148578)._
