-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AC-1911] Clients: Create components to manage client organization seat allocation #8505
[AC-1911] Clients: Create components to manage client organization seat allocation #8505
Conversation
…rganization-seat-allocation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice start. Got a few points below for you and then we can work through this initial feedback below.
❓ Did you end up getting the feature flag to work? I can't trigger it locally.
✏️ For all net-new files, we should be creating them in a manner where the Billing team owns them so that we don't have to ask other teams for reviews on them arbitrarily. I'd suggest either reorganizing what you have so that it's in a billing folder or updating the CODEOWNERS file.
...src/app/admin-console/providers/clients/manage-client-organization-subscription.component.ts
Outdated
Show resolved
Hide resolved
...src/app/admin-console/providers/clients/manage-client-organization-subscription.component.ts
Outdated
Show resolved
Hide resolved
...c/app/admin-console/providers/clients/manage-client-organization-subscription.component.html
Outdated
Show resolved
Hide resolved
...nse/bit-web/src/app/admin-console/providers/clients/manage-client-organizations.component.ts
Outdated
Show resolved
Hide resolved
...nse/bit-web/src/app/admin-console/providers/clients/manage-client-organizations.component.ts
Outdated
Show resolved
Hide resolved
New Issues
|
…rganization-seat-allocation
…rganization-seat-allocation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work - this is really coming along and looks great on the front-end. I caught one more bug that I left a note for.
Additionally, can you address my comment regarding net-new files? We should either store those files somewhere we own or update the CODEOWNERS for us to own them specifically. AC team won't have context on what to review for these.
Thanks!
...nse/bit-web/src/app/admin-console/providers/clients/manage-client-organizations.component.ts
Outdated
Show resolved
Hide resolved
Sorry, one more thing. I've scaled both of my client organizations in the example below down below their seat minimum, which means the warning shown in this Figma is not working. In my example, each plan has a seat minimum of 100. The single Teams org has 70 seats and the single Enterprise org has 40 seats. If I manage the subscription for the Teams org, I should see the helper text for 30 unassigned seats. |
…onents-to-manage-client-organization-seat-allocation' into ac-1911-create-components-to-manage-client-organization-seat-allocation
…rganization-seat-allocation
…onents-to-manage-client-organization-seat-allocation' into ac-1911-create-components-to-manage-client-organization-seat-allocation
…rganization-seat-allocation
…onents-to-manage-client-organization-seat-allocation' into ac-1911-create-components-to-manage-client-organization-seat-allocation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but I have one business logic question: shouldn't we disable the "Manage seats" option if the selected Organization Plan does not support consolidated billing?
Hi @r-tome, once Consolidated Billing goes live, a Provider will not be able to link an organization that doesn't use one of the supported plans so theoretically, that case wouldn't be possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for answering @amorask-bitwarden!
Good work @cyprain-okeke!
Type of change
Objective
In the Provider Portal, on the Clients tab, implement components according to the Figma designs that allows the Provider Admin to view and manage the number of seats they’ve allocated to each of their client organizations.
Notes
The 3-dot menu to the right of each client organization opens more options including “Subscription”, which opens the manage-client-subscription.component modal and “Unlink organization”, which should behave the same as the current Provider Portal’s client management
The “Add organization” button will not be included in this story. That piece will be tackled in this story after this one has been completed
Code changes
Screenshots
Before you submit
Uploading Screen Recording 2024-04-01 at 14.26.55.mov…