The discussion revolves around the delay in revoking admin status for a user, despite immediate revocation of moderator status. hhlp notes that admin revocation took about 4 days, unlike moderator revocation, which was instant. ondrej clarifies that admins cannot revoke their own admin status; it must be done by another admin. pfaffman suggests the issue might be due to the user being listed in DISCOURSE_DEVELOPER_EMAILS in app.yml, which prevents admin status changes via the UI. hhlp confirms the user wasn’t added to this list but suspects it might be the case and plans to check. hhlp adds that another admin can see the admin revocation option, but they cannot, and the issue was resolved after 4 days. The problem appears to be related to backend configurations rather than user interface limitations.
I’m slightly confused. But if you’re an admin which is what it looks like, you can’t revoke your own admin, Another admin has to do that for you. Whereas, any admin can grant/revoke their own moderator status and other users’ moderator status hence why you can see that button.
I’m guessing that the user has their email address in DISCOURSE_DEVELOPER_EMAILS in your app.yml.
If a user is made an admin that way, they will always be an admin and you can’t change it from the UX. Someone will need to edit the app.yml and destroy and restart the container (or rebuild).