Remove an abuse report?

There's not a way to delete an abuse report outright. Appealed/Approved status of abuse reports is taken into account when calculating things like Author quality.

Which threshold/setting are you referring to when you say 2? There are a number of settings around Abuse that might be able to alleviate the issue of an accidental report.

Hi  , I was referring to "Possibly Abusive Threshold" = 2.

What other settings might I change to help mitigate this?

There's several different things going on here around the abuse system:

• The reason the user was immediately determined to be abusive was because it was an admin (someone with "Manage Abuse" permission) who reported them. This is an automatic/immediate action that bypasses the standard calculations of the abuse scoring system (that compare an author's scores regarding potential for abuse against reporters's scores regarding accuracy of abuse reports) to make a determination on if a content/author is possibly abusive. Other regular users of the site have much less power in that regard, as their reports will not trigger an automatic action but instead be incorporated in the aggregate calculations that the automated abuse system uses to determine if something should bubble up to a moderator's attention.
• The "Possibly Abusive Threshold" is simply a hard check that will prevent the abuse system kicking in when there is too little information - just like the report made by a "Manage Abuse" (ie, trusted) user is a shortcut to override a potentially slower automated system that would typically rely on multiple reports. Once a user has more reports than the Possibly Abusive Threshold setting, that doesn't mean they will automatically be flagged as suspicious and sent to the Moderation Queue - it's just that the system will now be doing its normal process of comparing scores against one another to determine possible abuse.
• On that note - The score used for this on the creator user side is called the Abuse Creator score, which uses a baseline value adjusted by the Abuse Creator Effectiveness metric. This score is actually improved over the baseline for a user that has had a flag be reviewed and Approved (ie, found not abusive). The idea being that this user has had some moderator scrutiny already and was found to be within the rules and not an abusive member.

In conclusion, the fact that the user has one report that has since been Approved is not a concern for additional risk of future action by the abuse system down the road. If you'd still like to make settings adjustments, here are a few to consider:

• Possibly Abusive Threshold: you can increase this number to delay the impact of single reports until more have been received. Once the threshold is reached, all reports will still be calculated into the abuse determination, so the effect really is just a delay before the abuse system starts using its normal process of comparing calculated scores. Note that another accidental report by a moderator will still immedately put them in the abuse workflow.
• Member Account Protection settings: There are built-in waiting periods before automated abuse system takes very drastic action like deleting or disapproving accounts, but you can reduce the minimum account age and minimum post requirement to further ensure that any possible automatic action is mitigated for established users.
• Adjusting the weight of Abuse Creator metrics: increasing the weight of the "effectiveness" metric over the baseline metric will have the effect of both further increasing the abuse system's confidence in those whose flagged content/account has been reviewed and Approved, and further reducing the abuse system's confidence in those whose content/account has been reviewed and Rejected (confirmed abusive).

More reading about the Abuse and Spam systems can be found in the documentation here: community.telligent.com/.../how-does-moderation-and-abuse-work

 , this is the most thorough, helpful, and instructive response that I have ever received on any user forum...anywhere. I can't thank you enough for taking the time to write this up. Very, very helpful and I'll consider changes to our settings accordingly.