Content Policy
Keyword filtering, approval workflows, and auto-scan on import.
District-wide guardrails for user-generated content. Block keywords, require approval for external links, and scan uploads on import — with audit logs for compliance.
At a glance
The challenge
UGC risk in schools
Students upload inappropriate content; teachers share unvetted links.
How Ember helps
Policy before publish
Automated scanning and approval queues — configurable per school or district.
Real scenarios
When you'll use it
Concrete moments in the school week — not abstract features.
UGC moderation
District-scoped uploads route to a pending queue automatically before classmates ever see them.
Link sharing
External URLs queue for admin approval when your policy requires it.
Audit request
Export exactly who approved, rejected, or flagged each item, and when.
Capabilities
Everything included
Keyword filtering
Block lists with severity tiers and custom district terms.
Approval workflows
External links and file uploads queue for admin review.
Import scanning
Common Cartridge and file imports scanned before release.
Audit trail
Who approved what, when — exportable for compliance.
Scoped keyword filters
Apply filters to all resources, passages only, or AI Tutor conversations plus resources.
Full moderation audit trail
Every approve, reject, and flag decision is logged with the reviewer and timestamp.
How it works
Up and running in three steps
Define policies
Set rules at district or school level.
Content flows through gates
Uploads and links hit filters automatically.
Review exceptions
Admins approve or reject from a single queue.
FAQ
Common questions
Set keyword filters and scopes — all resources, passages only, or AI Tutor plus resources — at the district or school level.
Try Content Policy free
Set up your school or classroom in minutes. No credit card required.
Get startedWorks great with
Features commonly used together.