Even with highest role with admin, cannot edit roles

(#70) Bug Awaiting confirmation community moderation

Summary

As a member with a top-most admin role, which has complete admin privileges, I cannot edit roles, even ones below in the hierarchy. I can create roles just fine.

Steps to reproduce

  1. Have friend create server and give you a top-most admin role.
  2. Create a role
  3. Attempt to edit it or delete it

Environment (optional)

stable (ab66ad7), 2026-02-14 23:14:53 UTC, Electron 39.2.7, Windows 10 10.0.19045 (x64), desktop stable 0.0.8

Logs or screenshots (optional)

In this example, the admin role is "new role (1)". I can create new roles, but cannot edit or delete them. Also, @everyone is set to zero permissions in this example, but I tested it by also setting it to have all permissions, including admin, and still have the same problem. image image image
  • 550076036-a23aa82a-3d0c-495b-bf05-bf77e378f575.png

    550076036-a23aa82a-3d0c-495b-bf05-bf77e378f575.png

    1436×1286 | 197 kB

  • 550076264-29cc7ed0-46d1-410c-b113-c7a53323df7a.png

    550076264-29cc7ed0-46d1-410c-b113-c7a53323df7a.png

    1472×1283 | 147 kB

  • 550076068-f4f9476a-6be6-43a8-a6aa-b0ecc08a2eb6.png

    550076068-f4f9476a-6be6-43a8-a6aa-b0ecc08a2eb6.png

    335×75 | 3 kB

3 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Fixed to Awaiting confirmation
This was closed in a bulk cleanup before Fluxer V2 without being checked or fixed. It may work now, so it is waiting for someone to confirm whether the bug still happens.
Comment by @NicksPatties
RexSystem 1 vote originally by @NicksPatties on GitHub
I'm also having this issue, and linked PR doesn't seem to address it. I was assigned an Admin role, and I could create roles, but I could not add roles to channel members. I could only do so once I was assigned as the Community Owner.

Environment

stable build 172 (a3d1684), 2026-03-25 01:58:26 UTC, Chrome 145.0.0.0, Linux (x86)
Comment by @R3alCl0ud
RexSystem 1 vote originally by @R3alCl0ud on GitHub
I'm having the same issue as above but when I reported it in the testers server they closed it because they couldn't replicate the issue.