# Editing posts cause notification **URL:** \ **Category:** Support\ **Created:** [December 22, 2018, 12:34am UTC](https://meta.discourse.org/t/editing-posts-cause-notification/104873 "2018-12-22T00:34:51Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![tshenry](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tshenry/32/119495_2.png) [@tshenry](https://meta.discourse.org/u/tshenry)\ **Post date:** [April 19, 2021, 7:46pm UTC](https://meta.discourse.org/t/editing-posts-cause-notification/104873/17 "2021-04-19T19:46:49Z")
> [@Grayden\_Shand](#): > > The notification is being sent to users who joined the group after the post was originally created. Ah ha, thanks for that! I definitely see the same behavior. Sending mention notifications through a post edit is an important function that I know I and others use from time to time, so we want that to stay, but the way it’s working with groups feels off. My opinion at this point would be to only notify a group once per post. Users added to a group **after** an initial group mention was made should **not** receive a group mention notification as a result of subsequent post edits. The JIT education banner about notifying the group should **not** display during the editing of a post if there are no new group mentions since the post was last saved. If a group that was not previously mentioned is mentioned in an edit, they **should** be notified. That’s how it works with user mentions. We should also see the relevant educational banner if there is a newly mentioned group. I’m thinking we can just add some conditional logic based on the existence of a record in the `group_mentions` table. We create a record [at the time of saving a post](https://github.com/discourse/discourse/blob/5bec0e57637ed4351300ad17808b89b585df9568/app/services/post_alerter.rb#L108). What do you think @codinghorror? --- _[View the full topic](https://meta.discourse.org/t/editing-posts-cause-notification/104873)._