Content Checker Alerts

1. Business Summary

Manages a queue of alerts triggered by content events (Account/Job/Opportunity); processes pending alerts and dispatches via security viewers.

2. Business Value

Surface compliance/quality alerts to the right reviewers.

3. Users / Stakeholders

Ops, compliance, brand managers.

4. Workflows

• sentContentCheckerAlert() fetches alerts in pending status (0).
• Branch by entity_id (4=Account, 2=Job, 7=Opportunity).
• Resolve viewers via security tables (relation_type_id=1).
• Update status: 0→2 (processing), then 1 success / 2 error.

5. Sub-Features

• Alert queue, status flags, per-entity routing.

6. Business Rules

• Entity-type branching defines viewer logic.
• Errors retained as status=2.

7. Data Entities

ContentCheckerAlert.

8. Entry Points

• content_checker/* cron.

9. Inputs & Outputs

• Inputs: pending alerts.
• Outputs: emails/alerts to viewers.

10. Integrations

• Email/messaging.

11. Calculations / Logic

• Status state machine.

12. Status Lifecycle

• 0 pending → 2 processing → 1 sent / 2 error.

13. Permissions

• System cron.

14. Reports & KPIs

• Alert volume, error rate.

15. Risks & Observations

• Hardcoded entity branching limits extensibility.

16. Source Code Evidence

• app/Controller/ContentCheckerController.php (~1,377 LOC).
• app/Model/ContentCheckerAlert.php.