# Pre-Seeded Site Feedback Category - Allow Modifying Security Rules

**URL:** <https://meta.discourse.org/t/pre-seeded-site-feedback-category-allow-modifying-security-rules/158033>\
**Category:** Feature\
**Created:** [17 ביולי,‏ 2020,‏ 12:57pm UTC](https://meta.discourse.org/t/pre-seeded-site-feedback-category-allow-modifying-security-rules/158033 "2020-07-17T12:57:56Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![markersocial](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/markersocial/32/170136_2.png) [@markersocial](https://meta.discourse.org/u/markersocial)\
**Post date:** [17 ביולי,‏ 2020,‏ 12:57pm UTC](https://meta.discourse.org/t/pre-seeded-site-feedback-category-allow-modifying-security-rules/158033/1 "2020-07-17T12:57:56Z")

</div>

So for the pre-seeded Site Feedback category, when editing, under the security tab there is a warning.

> Warning: This category is a pre-seeded category and the security settings cannot be edited. If you do not wish to use this category, delete it instead of repurposing it.

I can understand there there is probably some good reasoning behind locking the Staff category security rules. However, there is no locking of the pre-seeded ‘Lounge’ category security rules. I’m thinking that the ‘Site Feedback’ category should be treated the same as the Lounge, with editable security rules.

Not sure if I’ve overlooked some detrimental effects of being able to edit the security settings for the Site Feedback category. All the other category options for it don’t appear to be locked.

---

_[View the full topic](https://meta.discourse.org/t/pre-seeded-site-feedback-category-allow-modifying-security-rules/158033)._
