<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> Each time [you create a project access token](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html#bot-users-for-projects), a bot user is created and added to the project. These bot users do not count as licensed seats. Currently those bot users are place in [*pending approval* state](https://docs.gitlab.com/ee/user/admin_area/moderate_users.html#users-pending-approval) like regular users. An administrator must approve them to allow the token to work. As discussed in [this issue (internal link)](https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/582#note_1077867788), this feature should allow the bot users to be approved automatically without going into *pending approval* state and without requiring an administrator approval. <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->