Resolve Matrix Room Admin Permission Errors by Action

When Element shows M_FORBIDDEN: You do not have permission, first identify the exact action that failed. Most room-management failures are caused by the account’s room power level or membership; a Synapse Admin API failure instead requires a homeserver server-admin account. Ask a current room admin to grant only the needed room permission, or use the Synapse Admin API only when the denied operation is genuinely a server-admin task.

Hypothetical example: Alex helps moderate a Matrix room and can remove spam, but gets M_FORBIDDEN when changing who may invite people. Alex is a moderator in that room, not a room administrator. The example is illustrative; it is not a claim about a tested account or server.

Identify which permission system denied the request

Matrix uses M_FORBIDDEN as a general forbidden-access error. The code alone does not say whether the problem is room power levels, room membership, an account restriction, or authorization for an administrative API. Read the complete error and note what Alex was doing: editing a room setting, inviting or banning someone, joining a room, or opening a Synapse administration tool.

A room’s permissions are stored in its m.room.power_levels state event. Element roles such as Default, Moderator, and Admin are a user-facing way to inspect these values, but the room can set custom levels. A homeserver server admin is a separate role; it does not automatically make that user a room admin. Action: classify the failed action before changing roles, and check whether the error came from Element’s room settings or a /_synapse/admin/ endpoint.

Fix a room action with the room’s power levels

If Alex cannot change a setting in Element, ask an existing room admin to inspect the room’s roles and permissions. In Element Web or Desktop, open the room, open Room Info or the room menu, choose Room Settings, and go to Roles & Permissions. Check Alex’s entry under privileged users and the required role for the specific action. Labels and layout can vary by client version.

For Alex’s invite-permission task, the admin should check both Alex’s own power level and the level required to change that permission. The Matrix specification defines these independently: the invite threshold controls invitations, while changing the power-level event itself requires authority to send that state event. A member might be permitted to invite users yet lack permission to change the invite threshold. The current admin can promote Alex to the lowest appropriate level or make the specific permission change themselves.

In Element’s documented default setup, Admin is typically level 100 and Moderator 50, but rooms can customize the requirements. Do not assume that every room uses those defaults. Also avoid demoting the only administrator: Element warns that doing so can leave the room without anyone able to manage it. Action: have the current admin confirm another trusted administrator remains before saving a role change.

If no one on the team can administer the room, determine whether a current room admin is available on another account or device. For rooms hosted on Synapse, a homeserver server administrator may be able to use Synapse’s Make Room Admin API to grant the highest power available to a local user who is in the room. This is a recovery path for the homeserver operator, not an ordinary client-side permission bypass; the endpoint requires a server-admin credential and may not apply to rooms hosted elsewhere. Use the current Synapse endpoint documentation and keep its Admin API private from public access.

If the error came from Synapse Admin API

If the failed request targets /_synapse/admin/..., room Admin in Element is not enough. Synapse requires a valid access token belonging to a server admin for many Admin API calls. Confirm that the token belongs to the intended account, has not been revoked or mistyped, and is sent using the documented authorization header. Do not paste access tokens into a public issue, browser screenshot, or shared log; treat them like passwords.

Synapse recommends hiding the Admin API from public view with a reverse proxy and typically making requests from the machine running Synapse. An administrator should use the API matching the installed Synapse version. Avoid editing the database directly to elevate a user as a first response: Synapse’s current guidance points operators toward admin commands and APIs once they have a server-admin account.

Check membership, account state, and the result

If the failed action was joining or sending an event, confirm Alex is actually joined to the room and is not banned. Being invited is not the same as being joined, and membership rules can block access even when the account has a high power level. If the error appears across unrelated rooms or during login, it may not be a room-admin issue; check the full error response and whether the account is locked, suspended, or otherwise restricted by the homeserver.

After the right admin changes the permission, have Alex retry the same operation in the same room. Confirm the expected result—for example, that the invite or setting change succeeds—and check the room’s Roles & Permissions view to ensure the intended level is present. If it still fails, capture the exact action, room ID, timestamp, HTTP status, and redacted error text for the homeserver administrator. Do not include an access token.

Use the Matrix Client-Server API specification for the meaning of standard error codes and room power-level rules, Element’s help and support pages for the room settings workflow, and the Synapse Admin API documentation for server-admin authentication and room recovery operations. The exact message text and controls depend on the client, homeserver, room version, and customized power levels.

Leave a Comment

Resolve Matrix Room Admin Permission Errors by Action

Trace M_FORBIDDEN to room power levels, membership, or Synapse server-admin access, then restore only the permission the blocked action needs.

Make Your Matrix Synapse Server Reachable for Federation

Make Your Matrix Synapse Server Reachable for Federation

Configure Synapse discovery, HTTPS, and proxy routing so other Matrix homeservers can find and contact your server.

Connect Element Web to Keycloak Through Synapse OIDC

Configure a Keycloak OIDC client and Synapse provider so Element Web users can sign in through your identity server without exposing client secrets.

Set Up Element Key Backup and Cross-Signing Safely

Set Up Element Key Backup and Cross-Signing Safely

Save a recovery key, verify your Element sessions, and check that encrypted message keys can be restored without confusing backup with your account password.

Stop Matrix Synapse Memory Crashes During Client Sync

Diagnose Synapse out-of-memory failures during sync, adjust caching safely, identify request backlogs, and verify stable memory use.

Resolve Synapse Federation TLS Certificate Errors

Trace Matrix federation certificate failures to the correct server, repair the TLS chain or CA trust, and verify the fix without disabling security checks.

Put a Synapse Matrix Server Behind Cloudflare Safely

Put a Synapse Matrix Server Behind Cloudflare Safely

Route Matrix clients and federation through Cloudflare on HTTPS 443, preserve Synapse discovery, and avoid caching API traffic or breaking media uploads.

Restore Matrix Synapse Safely with a PostgreSQL Dump

Back up Synapse with pg_dump, protect its signing key and media, and restore into a clean PostgreSQL database without reusing stale one-time keys.

Run Mjölnir as a Matrix Room Moderation Bot with Docker

Run Mjölnir as a Matrix Room Moderation Bot with Docker

Set up Mjölnir with a dedicated Matrix account, encrypted management room, Docker Compose, policy list, and permission checks.

Enable Native Matrix Sliding Sync for Faster Mobile Loading

Enable Native Matrix Sliding Sync for Faster Mobile Loading

Skip the retired proxy and configure Synapse’s built-in Sliding Sync. Check client discovery, then measure room-list loading and reconnect behavior on a compatible phone.