Account – Settings – Comment Responder – Shield

Route

• Path: /account/settings/comment-responder/shield (TBD)
• Parent: settings-comment-responder.md

Purpose (business goal)

Configure safety, compliance, and risk controls applied to generated replies (blocking, disclaimers, redaction).

User roles & permissions

• Workspace Admin
• Permissions: comment_responder.manage, compliance.manage (TBD)

Reference: Roles & Permissions Model

Layout structure

• Policy toggles
• Block/allow lists (TBD)
• Required disclaimer rules (TBD)

Components used

TBD

States

• Empty: TBD
• Loading: fetch policies
• Error: invalid policy / save failure
• Complete: policies updated

Business logic (high-level)

Shield policies are enforced at reply generation and before send.

Domain refs:

• Security & Compliance
• Domain: Comment Responder
• Domain: Knowledge Bases

API dependencies

• GET /apps/comment-responder/settings/shield
• PUT /apps/comment-responder/settings/shield

Enterprise constraints

• Shield policies are part of enterprise compliance posture; changes must be auditable and access-controlled.
• Policies must be consistently enforced across channels/apps for the workspace (TBD).

Edge cases

• Policies conflict (e.g., allow-list vs block-list); precedence rules are TBD.
• Policy change affects in-flight queues; rollout behavior is TBD.

Security & compliance considerations

• Enforce least-privilege access; prevent policy bypass.
• Audit all policy changes and surface who/when/what changed.

Reference: Security & Compliance

Analytics events (if applicable)

TBD

Reference: Analytics Events (MVP)