Account Strike System

from policy → action to policy → strike engine as detailed in docid\ lsfkyoqsi365x alowit1 , each policy or sub policy can be linked to a single moderation action this policy → action model ensures consistent enforcement once a policy is matched, the assigned action is automatically applied however, this model has limitations it does not take into account whether a user has previously violated other policies, nor does it support progressive enforcement for repeated violations of the same policy the strike system addresses these gaps it allows nima to track users’ violations over time and apply progressive consequences based on their history for example, a first violation might trigger a warning, a second violation could result in a temporary suspension, and repeated violations could escalate to permanent account restrictions strike system glossary before detailing how to set up your strike system, a few key notions true 125,462 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type 1 1 unhandled content type how to set up a strike system strike systems are configured in settings > account strike system define the scope if you want the strike system to target a specific subset of content, use the criteria similarly to the rule engine you can define the scope based on detection source, labels, content types, or any custom attributes this allows you to create strike systems for different parts of your platform independently if you will be using only one strike system, you do not have to set up criteria create tiers each strike system can have multiple tiers , representing different levels of severity of the policies you will map to the strike system for each tier, configure actions – the moderation action applied when a user reaches a precise number of violations you can select any moderation action you have selected reset time – how long a tier remains active before violations expire, allowing the user’s strike count to decrease over time (e g , 30 days) map your policies to tiers once your strike system is configured, map your policies to the tiers of the strike system in policy configuration for each policy or sub policy, choose the tier that matches its severity within the strike system milder policies should map to lower tiers (requiring more violations to escalate), while severe policies map to higher tiers (escalating after fewer violations) when a user violates a mapped policy, they will either enroll in the tier or continue progressing within it according to the number of accumulated violations true 62,318 1346153846154,320 86538461538463 1 unhandled content type 3 1 unhandled content type