Skip to content
ConversionIQ Docs

Account – Settings – Comment Responder – Filters

Route

Section titled “Route”
  • Path: /account/settings/comment-responder/filters (TBD)
  • Parent: settings-comment-responder.md

Purpose (business goal)

Section titled “Purpose (business goal)”

Define which inbound items are eligible for automation/moderation (source, rating, keywords, language, etc.).

User roles & permissions

Section titled “User roles & permissions”
  • Workspace Admin, Manager
  • Permissions: comment_responder.manage (TBD)

Reference: Roles & Permissions Model

Layout structure

Section titled “Layout structure”
  • Filter builder UI
  • Preview affected volume (optional)

Components used

Section titled “Components used”

TBD

States

Section titled “States”
  • Empty: TBD
  • Loading: fetch filters
  • Error: invalid rule / save failure
  • Complete: filters updated

Business logic (high-level)

Section titled “Business logic (high-level)”
  • Filtering influences downstream queues and automation eligibility.

Domain refs:

API dependencies

Section titled “API dependencies”
  • GET /apps/comment-responder/settings/filters
  • PUT /apps/comment-responder/settings/filters

Enterprise constraints

Section titled “Enterprise constraints”
  • Filters affect automation/moderation eligibility at scale; defaults should be conservative (TBD).
  • Filtering must be workspace-scoped and must not leak channel data across workspaces.

Edge cases

Section titled “Edge cases”
  • Filter rules exclude all items; moderation queue becomes empty (TBD).
  • Conflicting rules; precedence/ordering is TBD.

Security & compliance considerations

Section titled “Security & compliance considerations”
  • Filters can materially change automation behavior; audit all changes.

Reference: Security & Compliance

Analytics events (if applicable)

Section titled “Analytics events (if applicable)”
  • comment_responder.filters.updated

Reference: Analytics Events (MVP)