Uploaded image for project: 'Commerce'
  1. Commerce
  2. COMMERCE-82

Eliminate ambiguity regarding how billing accounts are displayed in the billing console

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • CCP - Billing
    • 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 Definition

      In the improved billing experience, there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

      A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a mix of subscriptions billed on either the original and improved billing experiences.

      Suggested Solution

      • Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has some billing rights(documentation: Which Atlassian roles have billing permissions?), but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
        Billing admin Billing user
      • Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
      • Find ways to create a greater sense of separation between a "billing account" and an "Atlassian organization"
      • After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:

      Why this is important

      • The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
      • The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

      Workaround

      • If an org. admin wants to view the subscriptions related to a specific organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
      • Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations

        1. billing_admin.png
          billing_admin.png
          470 kB
        2. no_billing_admin_rights.png
          no_billing_admin_rights.png
          325 kB
        3. Screenshot 2025-01-23 at 22.36.01.png
          Screenshot 2025-01-23 at 22.36.01.png
          394 kB
        4. Screenshot 2025-01-24 at 09.39.42.png
          Screenshot 2025-01-24 at 09.39.42.png
          350 kB
        5. Screenshot 2025-01-24 at 09.41.00.png
          Screenshot 2025-01-24 at 09.41.00.png
          470 kB

            [COMMERCE-82] Eliminate ambiguity regarding how billing accounts are displayed in the billing console

            pqz made changes -
            Component/s Original: Commerce - CCP - Billing [ 71502 ]
            Component/s New: CCP - Billing [ 79604 ]
            Key Original: CLOUD-12195 New: COMMERCE-82
            Support reference count Original: 1
            Project Original: Atlassian Cloud [ 14613 ] New: Commerce [ 24011 ]
            Derrick Nguyen made changes -
            Description Original: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights(documentation: [Which Atlassian roles have billing permissions?|https://support.atlassian.com/subscriptions-and-billing/docs/understand-billing-administration/#Which-Atlassian-roles-have-billing-permissions]), but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:
            !Screenshot 2025-01-23 at 22.36.01.png|thumbnail!

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!             		New: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights(documentation: [Which Atlassian roles have billing permissions?|https://support.atlassian.com/subscriptions-and-billing/docs/understand-billing-administration/#Which-Atlassian-roles-have-billing-permissions]), but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * Find ways to create a greater sense of separation between a "billing account" and an "Atlassian organization"
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:
            !Screenshot 2025-01-23 at 22.36.01.png|thumbnail!

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!
            SET Analytics Bot made changes -
            Support reference count New: 1
            Derrick Nguyen made changes -
            Description Original: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:
            !Screenshot 2025-01-23 at 22.36.01.png|thumbnail!

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!             		New: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights(documentation: [Which Atlassian roles have billing permissions?|https://support.atlassian.com/subscriptions-and-billing/docs/understand-billing-administration/#Which-Atlassian-roles-have-billing-permissions]), but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:
            !Screenshot 2025-01-23 at 22.36.01.png|thumbnail!

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!
            Derrick Nguyen made changes -
            Security Original: Atlassian Staff [ 10750 ]
            Derrick Nguyen made changes -
            Description Original: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!             		New: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:
            !Screenshot 2025-01-23 at 22.36.01.png|thumbnail!

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!
            Derrick Nguyen made changes -
            Attachment New: Screenshot 2025-01-23 at 22.36.01.png [ 480730 ]
            Derrick Nguyen made changes -
            Description Original: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a specific organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!             		New: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a _specific_ organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!
            Derrick Nguyen made changes -
            Description Original: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a specific organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI


             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations             		New: h3. Problem Definition

            In the [improved billing experience|https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience], there is the concept of a "billing account". Multiple product subscriptions from different organizations can be linked to a single billing account.

            A billing account is independent of the organization admin. UI. This means that when looking at a billing account, the admin or billing user will potentially see subscriptions from different organizations. The billing account only displays subscriptions which are billed on the "improved billing experience". A site may have a _mix_ of subscriptions billed on either the original and improved billing experiences.
            h3. Suggested Solution
             * Allow "billing users" to see the menu on the left side of the screen. This may help the billing users orientate themselves and provide visual confirmation that they are looking at a billing account - which is a separate entity to the org. UI. A "billing user" is a user who has _some_ billing rights, but is not a "billing admin". A "billing admin" is able to perform all billing related tasks. This is a comparison between what a billing admin and billing user sees respectively:
            ||Billing admin||Billing user||
            |!billing_admin.png|thumbnail!|!no_billing_admin_rights.png|thumbnail!|

             * Change the breadcrumbs and page title/heading to indicate that the admin is looking at a billing account and not subscriptions belonging to a specific org.
             * After a product subscription is cancelled, the billing user is directed to the billing account page. It might be a better experience if the billing user is directed to the cancelled subscription page instead. Example:

            h3. Why this is important
             * The current experience is ambiguous as the UI does not make it clear that the admin is looking at a billing account and not the subscriptions relating to the particular organization
             * The ambiguity causes confusion and alarm as it appears that unrelated subscriptions from different organizations are unexpectedly appearing in an org. - despite appearances, not all the subscriptions displayed are not connected or related to the org.

            h3. Workaround
             * If an org. admin wants to view the subscriptions related to a specific organization, they will need to go to the "Billing" page(/billing-preview) on the top menu bar of the UI
            !Screenshot 2025-01-24 at 09.39.42.png|thumbnail!

             * Be aware that the UI displays the "billing account" which can contain subscriptions from multiple organizations
            !Screenshot 2025-01-24 at 09.41.00.png|thumbnail!
            Derrick Nguyen made changes -
            Attachment New: Screenshot 2025-01-24 at 09.41.00.png [ 480729 ]
            Attachment New: Screenshot 2025-01-24 at 09.39.42.png [ 480728 ]

              Unassigned Unassigned
              dnguyen4 Derrick Nguyen
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: