Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-14

Organization Admins should be added to the domain in which they belong or better distinguished

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • 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.

      Problem Statement

      When more than 1 Cloud URL is associated to the same domain, it causes confusion and has serious implications to other cloud instances associated to the said domain.

      When we migrate the domains of a site to an Organization, all active site-admins are added as Organization admins to that Organization without their knowledge.

      As a result, admins residing in other instances are inheriting changes they did not make. There is nothing preventing a see-saw effect where admin in instanceB makes a change that impacts impactsA and vice versa unless the admins are aware of each others existence.

      Suggestions:

      • The account that established the Organization could be added to the Organization Details section to help distinguish between the existing site-admins
      • Do not add site-admins to the Organization unless the are directly associated to the domain (i.e. email match, etc), otherwise group the users at the top so that site-admins can visually distinguish any accounts that belong to another domain
      • In instancename.atlassian.net/admin/users, highlight the account in the instance that established an Organization
      • Record such events in the audit log for historical and troubleshooting purposes

              hxue Helen (Inactive)
              jworley Jason Worley (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: