Background Users
Description
There is a need for a type of user (background user) that has Admin level access, but can only handle a small subset of tasks. For example, Jenkins integration. Right now, customers have to either use an existing Admin level user to integration Jenkins with each project, or create an Admin level user to do this (which takes up a license).
There is a demand for a service user for this type of task.
Proposal
The ability to create/enable an Admin level service or background user that doesn't take up a license, but is also limited in the tasks it can run on the server.
Overview
What is it? A new type of user.
Why should someone use this feature? To help with integrating 3rd party tools with GitLab that require authentication and/or admin level access, but shouldn't be taking up a license.
What is the underlying (business) problem? People don't want to use an existing user for this and don't want to pay for a license to enable their 3rd party integrations.
How do you use this feature? Perhaps a new type of user that can be created? Similar to an Auditor user, but one that doesn't take up a license.
Use cases
This would specifically help with the Jenkins integration which requires authentication into GitLab.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml