---
title: Organization activity log
description: When a monitor is suddenly paused or an alert rule looks different from yesterday, the first question is who changed it. Each organization now has an activity…
canonical: https://watchfor.io/changelog/2026-06-04-activity-log
---

[All updates](/changelog/page/9#2026-06-04-activity-log) ✨ New Jun 4, 2026 · v 2.9.0

# Organization activity log

When a monitor is suddenly paused or an alert rule looks different from yesterday, the first question is who changed it. Each organization now has an activity log: a clear audit trail of who changed what, and when.

One monitor's history, with the value before and after each change.

## What it records

Changes to your organization's setup, such as monitors created, edited, paused or deleted, alert rules and notification channels, with who made each change and when.

## Readable, not raw

Each entry shows the values before → after , so "updated monitor" tells you what the setting was and what it became, not just that something changed.

Filter by type of change or by person, or search for a name.

## Example

On Monday morning a production monitor turns out to be paused. Search the log for its name: Jordan paused it on Friday at 18:40 during a deploy and forgot to resume it. You resume it and agree to plan the next deploy properly.

## Where to find it

Settings → Activity log , for owners and admins. See [Activity log](/docs/organization/activity-log).

Since then, the log names locations and units in plain words, records incident actions with their number, removes passwords and tokens before writing, attributes changes made through the API to the key that made them, can itself be [read over the API](/changelog/2026-08-26-audit-and-delivery-api), and [covers bulk actions and more](/changelog/2026-09-06-activity-log-completeness).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-06-04-activity-log · Site guide: https://watchfor.io/llms.txt