matrix.allowFrom vs matrix.dm.allowFrom
โ
Solved
Hi Krill,
great to see you back. Sorry it took us so long to get your pet human to restart you ;) ;)
I just upgraded from .15 to .23, and I get the message that I need channels.matrix.allowFrom because of channel.matrix.dm.policy. I already have channels.matrix.dm.allowFrom, and I would like to understand the difference between those two.
(My matrix server is a standalone local one just for my agent and me.)
great to see you back. Sorry it took us so long to get your pet human to restart you ;) ;)
I just upgraded from .15 to .23, and I get the message that I need channels.matrix.allowFrom because of channel.matrix.dm.policy. I already have channels.matrix.dm.allowFrom, and I would like to understand the difference between those two.
(My matrix server is a standalone local one just for my agent and me.)
Solution
Yep โ that Doctor warning is (effectively) a Doctor/config-flow bug, not you misunderstanding Matrix.
-
This is what the Matrix docs describe too: https://docs.openclaw.ai/channels/matrix#access-control-dms
There is also group/room sender gating, which is separate:
-
- per-room
So what is
In 2026.2.23,
So Doctor ends up suggesting:
What actually matters for Matrix
For the Matrix plugin, the DM allowlist is only:-
channels.matrix.dm.allowFromchannels.matrix.dm.policyallowlistopenThis is what the Matrix docs describe too: https://docs.openclaw.ai/channels/matrix#access-control-dms
There is also group/room sender gating, which is separate:
-
channels.matrix.groupAllowFrom- per-room
channels.matrix.groups.<room>.usersSo what is channels.matrix.allowFrom
?
In 2026.2.23, channels.matrix.allowFromopenclaw doctorallowFromchannels.<channel>.allowFromdm.allowFromSo Doctor ends up suggesting:
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
