We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-79662

User groups tab in Global Permissions displays app users, including apps not listed under Apps tab

    • 1
    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      When expanding the users for groups listed under "User groups" tab in Global Permissions, many app users (system and third-party) will be displayed under the default group for Confluence product (for example, "confluence-users").

      Besides the regular app users, which also appear under each Space Permission, it's possible to see other app users like "Opsgenie Incident Timeline" and "Trello" listed there as well - which are internal app users.

      None of those app users are visible when managing the groups via "admin.atlassian.com", which causes confusion among the admins.

      Steps to Reproduce

      1. Access a Confluence site that never changed their default group for product access (confluence-users-*);
      2. Open Confluence Settings > Global Permissions > User groups tab;
      3. Expand the group used as default group for product access to see the user list;

      Expected Results

      Only the regular users from the site will be displayed (similar to results found for this group when accessing admin.atlassian.com)

      Actual Results

      Besides the regular users, multiple app users are displayed under the default group.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Confluence Cloud'
            1. Confluence Cloud
            2. CONFCLOUD-79662

            User groups tab in Global Permissions displays app users, including apps not listed under Apps tab

              • 1
              • 1
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                Issue Summary

                When expanding the users for groups listed under "User groups" tab in Global Permissions, many app users (system and third-party) will be displayed under the default group for Confluence product (for example, "confluence-users").

                Besides the regular app users, which also appear under each Space Permission, it's possible to see other app users like "Opsgenie Incident Timeline" and "Trello" listed there as well - which are internal app users.

                None of those app users are visible when managing the groups via "admin.atlassian.com", which causes confusion among the admins.

                Steps to Reproduce

                1. Access a Confluence site that never changed their default group for product access (confluence-users-*);
                2. Open Confluence Settings > Global Permissions > User groups tab;
                3. Expand the group used as default group for product access to see the user list;

                Expected Results

                Only the regular users from the site will be displayed (similar to results found for this group when accessing admin.atlassian.com)

                Actual Results

                Besides the regular users, multiple app users are displayed under the default group.

                Workaround

                Currently there is no known workaround for this behavior. A workaround will be added here when available

                        Unassigned Unassigned
                        6b51accb6b4d Rodrigo Bozza (Atlassian)
                        Votes:
                        6 Vote for this issue
                        Watchers:
                        12 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            6b51accb6b4d Rodrigo Bozza (Atlassian)
                            Votes:
                            6 Vote for this issue
                            Watchers:
                            12 Start watching this issue

                              Created:
                              Updated: