### Background: GitLab uses Groups to organize users. We should consider an explicit organizational concept of a Team in GitLab, and what might that look like. **What questions are you trying to answer?** * How should we build a Team in GitLab? Are they subsets of Groups, or are they a new, standalone concept? * Do teams span across Groups? How might we do this on GitLab.com? * How do I create/view/update/delete a team? What does this look like? * Do we need public/internal/private visibility for Teams (or some similar mechanism)? * How do roles and permissions work? Thus far, the most compelling use-case for Teams is to help us with team-based assignments in Issues and MRs. * How do we assign issues and MRs to Teams? * Should we be able to assign multiple Teams to an issue or MR? * When assigning or designating a Team assignment, who gets what notification? When do team members stop getting the notification? ### Links / references: * [Existing epic](https://gitlab.com/groups/gitlab-org/-/epics/122) * [How other products approach Teams](https://docs.google.com/document/d/1KZgINoTr3pv8P_aNwztK98-K4eTIlEi4fcubat725SI/edit) * [Group assignees](https://gitlab.com/gitlab-org/gitlab-ee/issues/6008)