Why are system and super admin both mod and admin?

Hey tknospdr :waving_hand:

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 :robot: Discourses’ AI had to say about this.

Why System and Discobot Have Elevated Privileges AI

Here’s why both the prebuilt ‘system’ and ‘discobot’ accounts in Discourse have admin and moderator roles:

1. system account

  • The system account is a special, built-in user that acts automatically on behalf of the platform. It performs automated tasks such as:
    • Sending critical system notifications and digests.
    • Posting default pinned topics.
    • Running background moderation (e.g., automatic closing, flagged post actions).
  • It must have both admin and moderator privileges to access the full system, perform actions on any Topic, and override all category or user restrictions. Most core platform automation relies on these elevated powers.
  • There is no supported way to remove its privileges, as this could break essential Discourse features.
  • Changing the username of the system account is not recommended, as it may cause confusion or be reverted on update; see the discussion here: Is it recommended to change Discobot and System username?.

2. discobot account

  • 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.
  • Admin rights are required because discobot needs to:
    • Send messages or perform actions regardless of category restrictions or user trust level.
    • Access inboxes, send private messages, and replicate all staff behaviors needed for onboarding.
  • According to the documentation:

    “Discobot must remain an administrator; this role cannot be removed.”
    (see the official guide)

  • Discobot is not a moderator by default, but always has admin rights.

Security Considerations

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.

References:

If you have further questions about customizing these accounts or concerned about their scope, please let me know!