Logs and Change History
Kicklet has three separate places for looking back at activity. Choose the one that matches the question you need to answer:
| Place | Use it for | It does not show |
|---|---|---|
| Audit Log | Who changed a supported product configuration, what changed, and whether a version can be restored. | Normal chat moderation events or general diagnostic messages. |
| Logs | User-visible system messages and diagnostics that need attention. | Admin-only system logs or a version history of settings. |
| Moderation history | Messages that were moderated automatically and the rule that triggered. | General diagnostics or configuration version history. |
All three are scoped to the Kicklet account you are currently working on.
Audit Log
Open Data Management → Audit Log to review tracked configuration changes across your account. The list can include commands, command groups, periodic messages, moderation rules, stream-title settings, global messages, alert messages, and giveaway lifecycle events.
Each entry identifies the changed item, action, actor, source, and time. Use the filters to narrow the list by item type, source, actor, or time range. Changes made together by the AI assistant can appear as one related group. Open an entry for its available change summary, details, and diffs.
The Audit Log records product configuration changes. It is not a record of ordinary runtime effects, such as a command running, points changing during a command, queue activity, cooldowns, or an external chat action.
Restore a configuration version
Some tracked configuration versions can be restored from their detail view. Use Restore earlier state to return the item to the state before that change, or Restore later state when that option is offered. A restoration replaces the current configuration and is recorded as a new Audit Log change.
A restore button appears only while the needed version data is available and the current state can be restored safely. The page explains when a conflict blocks restoration. Version-specific detail data and restore data can expire even though the Audit Log entry remains visible.
For non-Premium accounts, only the five most recent Audit Log entries remain fully visible; older entries are locked. Restoring a version requires Premium.
Logs
Open Data Management → Logs when something in your setup needs diagnosis. This page contains user-visible system messages, including the context and error code that were recorded for an entry when available. It does not expose admin-only or internal system logs.
Open an entry to inspect its message and context. Filter the list by minimum level, message text, area, entity field, and time range. The available areas are commands, periodic messages, alert messages, custom messages, and stream titles. Entity filters can target values such as a command name or ID, periodic-message ID, alert type, global-message type, render-job ID, trigger-message ID, or cache scope.
Use Logs to investigate an error or warning that affects your account. It is not a history of changes to settings; use the Audit Log for that.
Moderation history
Open Moderation and use Moderation history to review automatic moderation actions in chat. A history row can include the user, action, message, rule details, and matched text where available. Search by user to inspect a viewer's recent moderated messages, and open the linked rule when you need to adjust it.
Moderation history describes what a moderation rule did to chat. It does not replace the Audit Log: changing a moderation rule is a configuration change, while a message matched by that rule is a moderation event.