From add0f2232c9d0cb76bb97953b3465c371a7c26c1 Mon Sep 17 00:00:00 2001
From: Doug <6060466+pixlwave@users.noreply.github.com>
Date: Thu, 20 Nov 2025 11:22:48 +0000
Subject: [PATCH] Call out the possibility of redacting events that you don't
 have the power to send. (#2249)

---
 changelogs/room_versions/newsfragments/2249.clarification | 1 +
 content/rooms/fragments/v3-handling-redactions.md         | 3 +++
 2 files changed, 4 insertions(+)
 create mode 100644 changelogs/room_versions/newsfragments/2249.clarification

diff --git a/changelogs/room_versions/newsfragments/2249.clarification b/changelogs/room_versions/newsfragments/2249.clarification
new file mode 100644
index 00000000..7578edc3
--- /dev/null
+++ b/changelogs/room_versions/newsfragments/2249.clarification
@@ -0,0 +1 @@
+In room versions 3 through 12, clarify that when you have the power to redact, it is possible to redact events that you don't have the power to send.  
\ No newline at end of file
diff --git a/content/rooms/fragments/v3-handling-redactions.md b/content/rooms/fragments/v3-handling-redactions.md
index 80d478bf..232cad10 100644
--- a/content/rooms/fragments/v3-handling-redactions.md
+++ b/content/rooms/fragments/v3-handling-redactions.md
@@ -17,6 +17,9 @@ is met:
 2. The domain of the redaction event's `sender` matches that of the
    original event's `sender`.
 
+Note that the first condition holds true even when the `sender` doesn't have a
+high enough power level to send the type of event that they're redacting.
+
 If the server would apply a redaction, the redaction event is also sent
 to clients. Otherwise, the server simply waits for a valid partner event
 to arrive where it can then re-check the above.