Note: July 13 2023 -- closing this epic in favor of this one https://gitlab.com/groups/gitlab-org/-/epics/5872 ## Summary GitLab.com customers have a very difficult time identifying how many and which members are considered billable in their GitLab.com namespace. Currently, they must look at the members list for the parent group, subgroups and projects within that namespace to identify membership. We should serve this information to the customers in an easy self-service fashion. ## Iteration opportunities 1. [x] Billable members API endpoint https://gitlab.com/gitlab-org/gitlab/-/issues/217384 1. [x] Static UI table of users (MVC) https://gitlab.com/gitlab-org/gitlab/-/issues/216899 1. [x] Move table to separate "billable members" page referenced on billing page https://gitlab.com/gitlab-org/gitlab/-/issues/268245 1. [x] Improve table UX https://gitlab.com/gitlab-org/gitlab/-/issues/262874 1. [x] Add "Last Activity Date": 1. [x] UI https://gitlab.com/gitlab-org/gitlab/-/issues/33457 1. [x] API https://gitlab.com/gitlab-org/gitlab/-/issues/297291 1. [x] Allow owners to easily remove members in one consolidated page https://gitlab.com/gitlab-org/gitlab/-/issues/217851 1. [x] Provide ability to search billable members table https://gitlab.com/gitlab-org/gitlab/-/issues/262875 1. [x] Add expandable user information which includes group/subgroup/project level membership including: Access granted date, Access expires date, Last activity date, Role. 1. [x] UX: https://gitlab.com/gitlab-org/gitlab/-/issues/217851/designs/Iteration2___Seat_usage_list_v2.png 1. [x] Dev: https://gitlab.com/gitlab-org/gitlab/-/issues/321560 1. [x] Clarify membership via Invited Group 1. [x] UX: https://gitlab.com/gitlab-org/gitlab/-/issues/325411 1. [x] BE: https://gitlab.com/gitlab-org/gitlab/-/issues/324658 1. [x] FE: https://gitlab.com/gitlab-org/gitlab/-/issues/325412 1. [ ] Add ability to remove users from direct nested location in the expanded user view 1. [x] UI - Additional metadata related to billable members at the group/subgroup/project level (highest role, date added, added by user, etc) https://gitlab.com/gitlab-org/gitlab/-/issues/321560 1. [ ] API - Additional metadata related to billable members (highest role, date added, added by user, etc) 1. [x] Ability to sort by `Last activity` column 1. [x] UX: https://gitlab.com/gitlab-org/gitlab/-/issues/292038 1. [x] BE: https://gitlab.com/gitlab-org/gitlab/-/issues/330055 1. [x] FE: https://gitlab.com/gitlab-org/gitlab/-/issues/330121 1. [ ] Provide ability to filter billable members table 1. [x] UX: https://gitlab.com/gitlab-org/gitlab/-/issues/292038 1. [x] Filter MVC - Filter by name https://gitlab.com/gitlab-org/gitlab/-/issues/330121 1. [ ] Filter v2 - Filter by `last active`, `group invite`, `group`, `project` 1. [ ] BE: https://gitlab.com/gitlab-org/gitlab/-/issues/330059 1. [ ] Filter v3 - Filter by `ldap`, `max role`, `SAML`, `SCIM` 1. [ ] BE: https://gitlab.com/gitlab-org/gitlab/-/issues/334179 1. [ ] FE: https://gitlab.com/gitlab-org/gitlab/-/issues/262876 1. [ ] Explore additional alternatives to pagination (potentially solved by filter capabilities) 1. [x] Provide users ability to download/export the list of users into a filterable file format 1. [x] UX: https://gitlab.com/gitlab-org/gitlab/-/issues/282548 1. [x] BE: https://gitlab.com/gitlab-org/gitlab/-/issues/262877 1. [x] FE: https://gitlab.com/gitlab-org/gitlab/-/issues/293027 1. [x] Provide visibility into non-direct membership members 1. [x] Display badge when member is invited via shared group https://gitlab.com/gitlab-org/gitlab/-/issues/325412 1. [x] Display badge when member is invited via shared project https://gitlab.com/gitlab-org/gitlab/-/issues/334029 1. [ ] Add `last activity date` by nested membership location ([example](https://gitlab.com/gitlab-org/gitlab/-/issues/335101#note_619046528)) 1. [ ] Allow users to bulk edit the Seat Usage page (bulk remove as first iteration)