If an admin can do everything that a mod can do, what’s the thought process behind these automatically created accounts being set to both?
If there’s something that mod can do that admin cannot, maybe an article needs to more clearly state that, 'cause I searched before posting and could not find this info.
Hey tknospdr 
Not sure what you’re referring to when you say ‘super admin’. Discourses’ nomenclature only uses ‘admin’ and ‘moderator’ together they are referred to as ‘staff’
I’ve taken your question to mean: why are prebuilt accounts, system and discobot granted admin.
Here’s what 
Discourses’ AI had to say about this.
Here’s why both the prebuilt ‘system’ and ‘discobot’ accounts in Discourse have admin and moderator roles:
system account is a special, built-in user that acts automatically on behalf of the platform. It performs automated tasks such as:
discobot is the built-in onboarding “narrative bot”. It guides new users through tutorials, sends automated messages, and can interact programmatically with most features to assist users.“Discobot must remain an administrator; this role cannot be removed.”
(see the official guide)
Both accounts are designed to run in a trusted, automated capacity and are protected by platform constraints. Do not use these accounts for regular staff activity or modify their privileges, as this may impact core Discourse automation.
If you have further questions about customizing these accounts or concerned about their scope, please let me know!
there are differences in permissions between mods and admins
https://meta.discourse.org/t/trust-level-permissions-reference/224824
There is a ‘special admin’ role as well who can do a couple of extra tricks. In the guide it’s referred to as Developer:
I’m not sure why system is both. An admin should be able to do everything a moderator can. Maybe it’s just to cover all the bases and make double sure they can really do everything. 
But for the ‘special’ admin/first admin created along with the site - I think that used to only be granted the admin role, but this was changed to add the mod role too. I believe it was something to do with sites more likely to have only one person running the place in the beginning and auto-adding the mod role makes sure they don’t miss any of the mod notifications.
Incorrect assumption. The question is why are they both mod AND admin?
I checked that grid. It doesn’t show admin perms. But again, the question wasn’t are there differences, the question is, “Can a mod do something that an admin cannot?”
Maybe this is the answer, are there notifications that mods get that admins do not?
Admins are not notified about messages in the inbox of the moderators group. I think one of the reasons the first admin is now a moderator by default was this option
Moderators are also notified about unhandled flags and users in the review queue, as well as users who are ignored by other users.
And I think even though admins can read all messages, Discourse behaves differently when you reply to a message that was sent to a group as a member of that group. Then the individual user isn’t added to the conversation. When an admin visits the moderator inbox and replies to a message, the individual admin is added. Example from Meta: as you can see, the users who are admin and moderator were not added, but the admin was added when he handled the flag which has sent an automatic reply.
If an account is later removed from a group, they lose access to the conversations they had access to because of being a group member, but not to those where their account was added because they were not a member of the group. So pmusaraj will still be able to look at our conversation even without admin permissions, while the others will lose access once they are no longer admin or moderator.
Thanks, that was very concise and perfectly answers my question.
Now I know, and knowing is half the battle…
Alright old dudes! GI JOE!!
