# Lack of Effective Flag Integrity Controls **URL:** \ **Category:** Community Building\ **Created:** [September 16, 2023, 6:35pm UTC](https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246 "2023-09-16T18:35:01Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\ **Post date:** [September 16, 2023, 7:43pm UTC](https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246/6 "2023-09-16T19:43:06Z")
> [@Heliosurge](#): > > I would like to see Flagging integrity. Staff & Category Mods should not be allowed to manage flags they are the target of or the originator of said flag. Being the target or the originator of a flag feels like two separate cases. Preventing a mod from managing flags that they had created seems like it would impact a mod’s workflow. For example, a mod might flag a post as spam and then go back later to handle the flag from the review queue. The case of a moderator being the target of a flag feels like a tricky one. I suspect that for cases like this, a site’s moderators will need to consider the situation together as a team. The risk is that flags could be used in an attempt to pit moderators against each other. > [@Heliosurge](#): > > Very disappointed that a great topic was closed because of it’s broad scope. At a mere suggestion of “sub topic explosion”. The question in that topic’s OP is something I’m interested in. This may be an unreasonable request on my part, but I’m helping to moderate Meta for the next week while a few team members get a much needed break. Instead of questioning the decision to close the topic, could we just accept the suggestion to create separate topics to deal with the various sub issues that were brought up in the topic’s responses? --- _[View the full topic](https://meta.discourse.org/t/lack-of-effective-flag-integrity-controls/279246)._