BOULDER, Colo. - ColoradoDesk -- When moderation behavior changes unexpectedly, the first question is always the same: what changed, and who changed it? With Moderation Policy Audit Logs, you don't have to guess.

What Are Moderation Policy Audit Logs?

Moderation Policy Audit Logs give your team a complete record of every change made to your moderation setup, who changed what, when, and what it looked like before and after. Every time a policy or rule is created, updated, or deleted, a log entry is automatically generated with the actor, timestamp, and a full look at the change.

How It Works

Each log entry includes a one-line summary, the user who made the change, the configs affected, and the policy under which it was made. For updates, a See Changes view opens a structured comparison table showing exactly which settings were modified, with old values in red and new values in green. Only the settings that actually changed are shown, unchanged settings are hidden, so you're not sifting through noise.

More on Colorado Desk

• Governor Polis Marks Dobbs Anniversary: While Other States Restrict Healthcare Colorado Strengthens Access
• Colorado: Lt. Governor Primavera and CCIA announce Tribal and American Indian/Alaska Native Affairs Roadmap
• Governor Polis and the Colorado Department of Health Care Policy and Financing Open Applications for $160 Million to Reduce Healthcare Costs and Improve Access to Healthcare in Rural Colorado
• City announces plans to create Colorado Springs 911 Authority
• Colorado Springs: City Council leadership announces additional funding for the Pikes Peak or Bust Parade

The comparison table covers everything across your moderation stack:

• AI text config — actions set per harm label and severity level (e.g. Threat → flag changed to Threat → remove)
• AI image config — image moderation setting changes
• Blocklist config — blocked words and phrases added or removed
• LLM config — custom LLM moderation label changes

When list items are involved, like adding a new severity rule for one label and removing another, the log groups changes by item and only surfaces what was added, removed, or modified.

Finding What You Need

The log list includes filters designed to cut through volume fast:

Action Taken lets you isolate specific change types: policy created, updated, or deleted, and the same for rules. Stack multiple options to widen the view.

Resource Type filters span policy changes and rule changes without requiring the selection of each action individually.

More on Colorado Desk

• The Calida Group Announces Promotion of Joshua Nelson to President, Advancing Next Phase of National Growth
• Cango Mobility x Hikvision Announce Strategic Partnership
• HomeCentris Healthcare Signs Definitive Agreement to Acquire S&K Holdings, Expanding Mid Atlantic Platform
• Nayarit Strengthens Its Position as a Global Surf Destination; Sayulita to Become Mexico's First Official Surf City
• Century Fasteners de Mexico Exhibiting at 2026 Farnborough International Airshow

Combined with date filtering and actor visibility in every summary line, you can trace any config change back to the person and moment it happened.

Who It's Built For

Policy Audit Logs are built for teams where moderation configuration changes carry real consequences:

• Trust & Safety leads investigating unexpected moderation behavior, a sudden spike in removed content, a new harm label that wasn't flagged before, or a rule that stopped firing.
• Compliance teams that need a defensible record of policy changes for regulatory audits, DSA reporting, or internal governance reviews.
• Distributed moderation teams where multiple people have configuration access and visibility into who changed what prevents misconfigurations from going unnoticed.

Get Started

Moderation Policy Audit Logs are available now in the Stream Moderation Dashboard at Getstream.io. Navigate to the Audit Logs section to start reviewing your team's configuration change history.