Add new categories for Auth
Closes gitlab-org/manage/general-discussion#17464 (closed)
Currently, ~"group::authentication and authorization" only has 1 category: ~"Category:Authentication and Authorization". This results in everything being lumped together. It is difficult to get a sense of which areas make up ~"group::authentication and authorization" , and the sole category having the exact same name as the group doesn't make much sense.
The group has grown, and there are distinct areas within Authorization and Authentication that make sense to split out into separate categories. This will help us more clearly communicate our vision, segment features, and define the boundaries of Auth both internally and externally. We can also more clearly articulate which categories within the group are getting the most development effort, which are ARR drivers, and which are seen as more platform-level.
Proposal
| Category | Description | Marketing Category? |
|---|---|---|
| User Management | Lifecycle management of users, from provisioning to de-provisioning and everything in between | Yes, includes features like SAML and SCIM, which allow ease of user management at scale |
| Permissions | Framework for what a user can and can't do within GitLab, boundaries defined within current permissions matrix. This will include custom roles & the provide the framework for other groups to contribute their permissions sets | Yes, the ability to add custom roles will be a paid feature |
| System Access | Authentication through all points of GitLab: UI, CLI, API | No - expected base level service of the system. Without System Access, customer cannot use GitLab. |
| Credential Management --> Moved out of this MR and into [this one] (!100476 (closed)) | Lifecycle management of credentials, including tokens, for both users and group owners/admins | Yes. Visibility into credentials and the administrator control of them is something that customers are willing to pay for. |
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
VP of Product @david -
The Product GM/Director relevant to the affected Section(s) @ogolowinski -
The Engineering Director relevant to the affected Section(s) @m_gill @timzallmann -
Director of Product Design @vkarnes
The following people need to be on the merge request so they stay informed:
-
Chief Technology Officer @edjdev -
Vice President of Development @clefelhocz1 -
Vice President of Quality @meks -
Vice President of User Experience @clenneville -
The Product Marketing Manager relevant to the stage group(s) @cblake -
Senior Manager, Technical Writing @susantacker
After Approvals and Merge
-
Create an issue in the triage-ops project to update GitLab Bot automation -
Mention the product group Technical Writer to update the documentation metadata -
Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels