### Overview The current `/billings` areas for group namespaces don't show enough information about the current subscription. See https://gitlab.com/gitlab-org/gitlab-ee/issues/6898 for relevant product discovery. ### Proposal * Remove the existing promotion table from `/billings` * Replace with subscription table in https://gitlab.com/gitlab-org/gitlab-ee/issues/6898 #### Subscription table  The title for the table will be the name of the active subscription. On the right side of the header there will be a button labeled `Manage`, which will open the customers portal when clicked. The table will have two rows, _Usage_ and _Billing_. The _Usage_ row displays how many seats there are in the subscription and how many have actually been used. The columns in this row are: - _Seats in subscription_: Number of seats that have been paid for. - _Seats currently in use_: Number of active seats. - _Max seats used_: Max number of members there have been in the group at the same time. - _Seats owed_: The difference between _Max seats used_ and _Seats in subscription_. The _Billing_ row displays information relating to the subscription's validity in time, as well as when payments are due: - _Subscription start date_. - _Subscription end date_. - _Last usage revision_: The date the last time the GitLab team (or automatic system) contacted the customer to settle up any outstanding balances. - _Next usage revision_: The upcoming date when the GitLab team (or automatic system) is scheduled to contact the customer to settle any outstanding balances. #### Informational popovers | Seats in use | Max seats used | Seats owed | Last usage revision | Next usage revision | |--------------|----------------|------------|---------------------|---------------------| |  |  |  |  |  | We will add information icons to some of the cells, which will open popovers when clicked. The copy for each one is as follows: - _Seats currently in use_: > Users with a Guest role don’t count towards seats in use. - _Max seats used_: > This is the maximum number of users that have existed at the same time since this subscription started. This is the minimun number of seats you will need to buy when you renew your subscription. > > [Learn more about renewals]() (Link TBD) - _Seats owed_: > GitLab allows you to continue using your subscription even if you exceed the number of seats you purchased. You will be required to pay for these seats on your next usage review. > > [Learn more about usage revisions]() (Link TBD) - _Last usage revision_: > This is the last time the GitLab.com team was in contact with you to settle any outstanding balances. > > [Learn more about usage revisions]() (Link TBD) - _Next usage revision_: > This is the next date when the GitLab.com team is scheduled to get in contact with you to settle any outstanding balances. > > [Learn more about usage revisions]() (Link TBD) ### Other scenarios #### Trial  When a group is on a trial, this will be reflected in the header of the subscription table. The content of the subscription table will behave slightly differently from a normal subscription: - _Seats in subscription_: Since a trial is free, this count should increase automatically as users are added to the group. It will always equal _Max seats used_. - _Seats owed_: For the same reason, this count will always be `0` for trials. - _Last usage revision_ and _Next usage revision_: Since a trial is free, there are no revision dates. The seat usage table will also behave slightly differently: - The _Original subscription_ row will be renamed _Trial start_. - The price per seat will always be $0. - The _Paid on column_ will never have a value. #### Free  If a group is using the free version of GitLab.com, the header for the table will read: > GitLab.com Free In this case, the subscription table will also show some specific behavior: - _Seats in subscription_ and _Seats owed_ will behave the same way as they do in a trial. - The _Subscription end date_ slot will be empty. - Free subscriptions do not have revision dates. The seat purchase history has two peculiarities: - The price per seat will always be `$0`. - The _Paid on_ column will always be empty.