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

Allow organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

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

      Suggestion :

      Allow the organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

       

      Workaround : 

      • Billing and technical contacts can be changed by other contacts in the product.
      • If the sole billing and technical contact already left the company, check with the IT team if it is possible to reactivate the email address of the user to temporarily be used to change the contact for the affected product. 
      • If the managed account is an organization admin of the organization that they are billing/technical contacts for, then the organization admin can gain access via discovered products and then navigate to https://admin.atlassian.com/o/<organization ID>/billing/paymentdetails and click "Manage contacts" and remove the managed account from the contacts list.

       

       

            [ACCESS-1636] Allow organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

            Srividya Ramaswamy made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4
            Cole Norman made changes -
            Labels New: guard-s7
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Tyler B [Atlassian] made changes -
            Description Original: Suggestion :

            Allow the organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

             

            Workaround : 
             * Billing and technical contacts can be changed by other contacts in the product.
             * If the sole billing and technical contact already left the company, check with the IT team if it is possible to reactivate the email address of the user to temporarily be used to change the contact for the affected product. 

             

             
            New: Suggestion :

            Allow the organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

             

            Workaround : 
             * Billing and technical contacts can be changed by other contacts in the product.
             * If the sole billing and technical contact already left the company, check with the IT team if it is possible to reactivate the email address of the user to temporarily be used to change the contact for the affected product. 
            * If the managed account is an organization admin of the organization that they are billing/technical contacts for, then the organization admin can gain access via discovered products and then navigate to https://admin.atlassian.com/o/&lt;organization ID>/billing/paymentdetails and click "Manage contacts" and remove the managed account from the contacts list.

             

             
            Anusha Rutnam made changes -
            Link New: This issue is related to ACCESS-1683 [ ACCESS-1683 ]
            Ramon M made changes -
            Remote Link New: This issue links to "ENT-1763 (Hello Jira)" [ 820185 ]
            Ramon M made changes -
            Description Original: It is good to have a feature that allows organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

            Currently, the process of updating the billing and technical contacts for products owned by their managed accounts when the user leaves the organisation is as below:
             # Reactivate these users' email addresses with the help of the IT team.
             # Once accounts are reactivated they need to visit the [Atlassian account recovery site|https://id.atlassian.com/login/resetpassword] and enter the corporate-owned domain email address of an authorized contact listed
             # Once the email account is activated they need to log in to [my.atlassian.com|http://my.atlassian.com/] account and add a new person as billing/technical contact.
             # To establish a new Primary Billing or Technical Contact, the new contact will need to log into their [my.atlassian.com|http://my.atlassian.com/] account and select *"Make Primary".* The existing Primary Contact will then be demoted to a secondary contact and can be removed so the account deletion can be processed.

             

             
            New: Suggestion :

            Allow the organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

             

            Workaround : 
             * Billing and technical contacts can be changed by other contacts in the product.
             * If the sole billing and technical contact already left the company, check with the IT team if it is possible to reactivate the email address of the user to temporarily be used to change the contact for the affected product. 

             

             
            Ramon M made changes -
            Description Original: It is good to have a feature that allows organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

            Currently, the process of updating the billing and technical contacts for products owned by their managed accounts when the user leaves the organisation is as below:
             # Reactivate these users' email addresses with the help of the IT team.
             # Once accounts are reactivated they need to visit the [Atlassian account recovery site|https://id.atlassian.com/login/resetpassword] and enter the corporate-owned domain email address of an authorized contact listed
             # Once the email account is activated they need to log in to [my.atlassian.com|http://my.atlassian.com/] account and add a new person as billing/technical contact.
             # To establish a new Primary Billing or Technical Contact, the new contact will need to log into their [my.atlassian.com|http://my.atlassian.com/] account and select *"Make Primary".* The existing Primary Contact will then be demoted to a secondary contact and can be removed so the account deletion can be processed.

            (i) The above process is not appropriate as once the user leaves the organisation their IT team would not like to reactivate or recreate the email accounts to proceed with the verification and then update the contacts.

             
            New: It is good to have a feature that allows organisation administrators to configure billing and technical contacts for products owned by their managed accounts.

            Currently, the process of updating the billing and technical contacts for products owned by their managed accounts when the user leaves the organisation is as below:
             # Reactivate these users' email addresses with the help of the IT team.
             # Once accounts are reactivated they need to visit the [Atlassian account recovery site|https://id.atlassian.com/login/resetpassword] and enter the corporate-owned domain email address of an authorized contact listed
             # Once the email account is activated they need to log in to [my.atlassian.com|http://my.atlassian.com/] account and add a new person as billing/technical contact.
             # To establish a new Primary Billing or Technical Contact, the new contact will need to log into their [my.atlassian.com|http://my.atlassian.com/] account and select *"Make Primary".* The existing Primary Contact will then be demoted to a secondary contact and can be removed so the account deletion can be processed.

             

             

              Unassigned Unassigned
              b23de49ea095 Abhishek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: