-
Suggestion
-
Resolution: Unresolved
I setup domain verification with our organization and immediately, over 3000 of our users were pulled into the Managed accounts. However, the billing showed that we would be charged over $800 for around 254 users which is confusing because I hadn't granted anyone but myself access to any of the products. Also, I had received a message that we would be charged over $2000 soon for another 1000 users because support for Trello was being extended to Atlassian Cloud and we had no plans to use Trello.
The only solution I was able to receive was to disable managed accounts, however, Admins are not able to do a bulk change to disable accounts. That means I have to disable over 3000 accounts one by one.
SUGGESTIONS:
- By default, when a domain is verified and managed accounts are pulled into the system, those users shouldn't be billed yet either by not granting access immediately and/or disabling them.
- Admins should be able to do bulk changes to managed accounts.
- It should be obvious on the billing site exactly why we are being billed.
- EXAMPLE: What product/site were 254 users being billed $800 for?
- It would be helpful if there was a walk-through during setup to help Admin with using the Atlassian Access feature that includes how billing is managed. Confluence page was very general with its description but the billing behavior didn't seem to match the description.
MY EXPECTATIONS AS ADMIN
- Subscribe to Atlassian Cloud Products
- Create Organization
- Verify Domain
- Setup SAML single sign-on
- Assign users/groups to specific products to control access and billing
[COMMERCE-16] Improve ability to manage billing for Managed Accounts from organization domain.
| Component/s | Original: Commerce - Billing - Preview [ 71890 ] | |
| Component/s | New: Billing - Preview [ 79602 ] | |
| Key | Original: CLOUD-10721 | New: COMMERCE-16 |
| Support reference count | Original: 2 | |
| Priority | Original: Low [ 4 ] | |
| Project | Original: Atlassian Cloud [ 14613 ] | New: Commerce [ 24011 ] |
| Support reference count | New: 2 |
| Component/s | New: Commerce - Billing - Preview [ 71890 ] |
| Labels | New: recent-comment |
| Workflow | Original: OnDemand v1 - Restricted [ 3713923 ] | New: JAC Suggestion Workflow 3 [ 3721883 ] |
| Status | Original: Open - untriaged [ 10059 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: OnDemand v1 [ 3070718 ] | New: OnDemand v1 - Restricted [ 3713923 ] |
| Workflow | Original: OnDemand v1 [ 3070718 ] | New: OnDemand v1 - Restricted [ 3709750 ] |
| Workflow | Original: OnDemand v1 [ 3070718 ] | New: OnDemand v1 - Restricted [ 3705578 ] |
| Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
| Description |
New:
I setup domain verification with our organization and immediately, over 3000 of our users were pulled into the Managed accounts. However, the billing showed that we would be charged over $800 for around 254 users which is confusing because I hadn't granted anyone but myself access to any of the products. Also, I had received a message that we would be charged over $2000 soon for another 1000 users because support for Trello was being extended to Atlassian Cloud and we had no plans to use Trello.
The only solution I was able to receive was to disable managed accounts, however, Admins are not able to do a bulk change to disable accounts. That means I have to disable over 3000 accounts one by one. SUGGESTIONS: * By default, when a domain is verified and managed accounts are pulled into the system, those users shouldn't be billed yet either by not granting access immediately and/or disabling them. * Admins should be able to do bulk changes to managed accounts. * It should be obvious on the billing site exactly why we are being billed. ** EXAMPLE: What product/site were 254 users being billed $800 for? * It would be helpful if there was a walk-through during setup to help Admin with using the Atlassian Access feature that includes how billing is managed. Confluence page was very general with its description but the billing behavior didn't seem to match the description. MY EXPECTATIONS AS ADMIN * Subscribe to Atlassian Cloud Products * Create Organization * Verify Domain * Setup SAML single sign-on * Assign users/groups to specific products to control access and billing |