Improve moderation controls and term management
This commit is contained in:
@@ -55,6 +55,19 @@ ISAC Site Controls stores the site-wide policy:
|
||||
- category review and priority thresholds;
|
||||
- allowed and banned local terms.
|
||||
|
||||
The term registry accepts single rules and batch imports. Batch imports use one
|
||||
term or phrase per line, accept commas and semicolons as separators, infer word
|
||||
or phrase matching, and add no more than 250 unique rules. Word rules match
|
||||
exact forms: `kill` does not match `kills`, `killed`, or `killing`. The import
|
||||
skips duplicates, records each created rule in the ISAC audit log, and leaves
|
||||
the batch editor open for the next list. The registry provides server-side
|
||||
search and displays 25 rules per page by default.
|
||||
|
||||
Each Site Controls category has its own save action. A save validates and
|
||||
updates only that category, increments the moderation policy version when
|
||||
applicable, and records a specific ISAC audit event with before and after
|
||||
evidence. Unsaved changes in other categories remain local drafts.
|
||||
|
||||
Site Controls requires `site.settings.manage`. Community Oversight handles text
|
||||
decisions through the existing comment and profile permissions. Avatar
|
||||
Oversight handles custom images through `avatars.review`.
|
||||
|
||||
Reference in New Issue
Block a user