Rename the "Admin group" label linked to EVERY group within Space Permissions/Restrictions to avoid confusion with actual admin permissions

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • Component/s: People and Teams
    • None
    • 17
    • 4

      Background

      Introduced as part of the "Teams in Confluence Permissions", now in the Space Permissions UI (Manage Space → Permissions), EVERY group listed displays an "Admin group" label with a verified badge, regardless of the group's actual permission role in the space.

      For example, a group with only the "Collaborator" role (e.g., confluence-users) still shows "Admin group ", which is identical to a group that actually has the "Admin" role.

      The same happens when adding Restrictions via the Share button.

      Why this is confusing

      In the context of Space Permissions, "Admin" already has a specific meaning — it's the highest permission role a principal can have in a space. Displaying "Admin group" next to every group creates a false impression that all groups have admin-level access, which is:

      • Misleading for space administrators trying to audit permissions
      • Confusing for customers unfamiliar with the distinction between "how a group is managed" vs. "what role it has"
      • Potentially alarming during security audits or compliance reviews

      Request / Expected behavior

      The byline label should either:

      1. Not use the word "Admin" in a context where "Admin" already means a specific permission level, OR
      1. Use a clearer label such as "Org-managed group", "Managed group" or simply "Group" with the badge, OR
      1. Only show "Admin group" for groups that actually have the Admin role in that space

        1. image.png
          81 kB
          Grant Heimbach

              Assignee:
              Unassigned
              Reporter:
              Rodrigo Bozza (Atlassian)
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: