Account Strike System

the account strike system lets you enforce progressively rather than identically instead of applying the same action every time a policy is violated, nima tracks an account's violations over time and escalates as they accumulate this is how you separate a first time mistake from a repeat offender from policy → action to policy → account strike system as detailed in actions 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 account 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 account strike system glossary before detailing how to set up your account strike system, a few key notions term description account strike system the mechanism in nima that tracks user violations over time and applies progressive consequences nima can host multiple strike systems, each with its own rules, allowing different areas of the platform to escalate violations independently example a “community forum” strike logic and a “marketplace” strike logic can coexist in the same strike system with separate criteria tiers levels within an account strike system representing the severity of enforcement each tier contains a sequence of policy violations and associated actions milder policies map to lower tiers requiring more violations to escalate, while severe policies map to higher tiers requiring fewer violations example tier 1 (mild) may require 5 violations before the final action; tier 3 (severe) may escalate after just 1 violation number of violations the count of times a user has triggered a policy mapped to a specific tier when the user reaches the required number of violations for that tier, the system applies the final action for that tier example if tier 1 requires 5 violations, the user moves through each step (e g , warning → content restriction → temporary suspension) until the 5th violation triggers the final action actions each policy violation within a tier is linked to a specific moderation action nima automatically applies this action whenever a violation occurs, ensuring consistent enforcement example a tier 2 violation for “hate speech” might automatically remove the content and issue a warning to the user reset time set on each step within a tier, in days — not once for the tier as a whole it is the period after which that violation expires if the user commits no further violations, allowing their strike count to decrease over time example a step with a reset time of 90 days stops counting towards escalation once the user has gone 90 days without a new violation how to set up a strike system strike systems are configured in configure > trust & safety > 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 most platforms start with one strike system covering everything, and that is usually the right choice add a second only when two parts of your platform genuinely warrant different escalation speeds for the same policy — a marketplace listing versus a community post, for example two strike systems mean two sets of tiers to keep aligned, so the cost is ongoing create tiers each account strike system can have up to five tiers (at least one), representing different levels of severity of the policies you will map to the strike system a tier is a sequence of steps, one per violation count add a step for each stage of escalation and configure both fields on it action – the moderation action applied when the user reaches that number of violations you can select any moderation action you have configured reset time – expressed in days, and set on each step individually rather than once for the tier it controls how long that violation keeps counting towards escalation before it expires (e g , 30 days) each tier now displays the policies mapped to it directly in the account strike system configuration view, making it easy to audit which policies are associated with each enforcement level map your policies to tiers once your strike system is configured, map your policies to the tiers of the strike system in policy configuration a policy is enforced through either a moderation action or a tier — not both assigning a tier replaces the policy's direct action from then on, the outcome comes from the account's position in that tier rather than from a single fixed action assign tiers only to the policies you want escalating in policy configuration docid\ r6vgf6m3d k8slkyopppp , the enforcement selector lists your tiers alongside your moderation actions you can open any tier from there to review the steps it contains before assigning it, without leaving the policy screen 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 example mapping policies to tiers and applying the strike system policies and tiers tier 1 (lower severity) hate speech, discrimination tier 2 (higher severity) harassment, csam strike system a – tier 1 1 policy violation → mute/chat 1 day 2 policy violations → mute/chat 3 days 3 policy violations → mute/chat 5 days 4 policy violations → ban/game 7 days 5 policy violations → permanent ban reset time 30 days on each step a user who accumulates 2 hate speech violations and 3 discrimination violations reaches 5 violations in tier 1, triggering a permanent ban strike system a – tier 2 (higher severity) 1 policy violation → ban/game 7 days 2 policy violations → permanent ban reset time 30 days on each step tier 2 allows users to start at a higher strike level for more severe violations for example, accumulating 2 tier 2 violations (e g , 1 harassment + 1 csam) triggers a permanent ban, so fewer violations are needed compared with tier 1 |