Uploaded image for project: 'Admin Experience'
  1. Admin Experience
  2. AX-386

The ability to obtain information about the relevant organization when you verified same domain on another organization.

XMLWordPrintable

    • 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.

      Description

      Currently, organization administrators have the ability to verify the same domains across multiple Atlassian organizations.

      However, at the moment, there is no way to detect the following situations:

      1. For example, if Organization A has already verified a specific domain and then that domain is verified in Organization B, the administrator of Organization A cannot become aware of this event.
      2. In the context described above, when an account has already been claimed by Organization A, the administrator of Organization B cannot determine which organization has claimed that particular account.

      Suggestion

      You need to add ability, which allows organization administrators to obtain the above information.

            [AX-386] The ability to obtain information about the relevant organization when you verified same domain on another organization.

            Rodrigo B. made changes -
            Component/s Original: Domain Claim - Maintenance [ 66394 ]
            Component/s New: Domain Verification - Maintenance [ 80146 ]
            Key Original: ACCESS-1864 New: AX-386
            Support reference count Original: 4
            Project Original: Atlassian Guard [ 18910 ] New: Admin Experience [ 24210 ]

            Вадік «Chifty» Дудар added a comment -

            another suggestion: allow move(claim) user from Org-A to Org-B through e-mail link confirmation
            That`s may help with case, when I don`t know who is "another organisation" and haven`t any contacts... 

            Example workflow: 
            1. Admin (with approved domain) send "request" to user for switching (like request for changing user info). 
            2. user confirm this by clicking "approve transfer" link in e-mail

            Вадік «Chifty» Дудар added a comment - another suggestion: allow move(claim) user from Org-A to Org-B through e-mail link confirmation That`s may help with case, when I don`t know who is "another organisation" and haven`t any contacts...  Example workflow:  1. Admin (with approved domain) send "request" to user for switching (like request for changing user info).  2. user confirm this by clicking "approve transfer" link in e-mail
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            SET Analytics Bot made changes -
            Support reference count New: 1
            Takeshi Muramatsu created issue -

              Unassigned Unassigned
              a5d57c498007 Takeshi Muramatsu
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: