### Problem to solve Organization's workflows are split across many projects and they want programmatic access to execute them with non-user accounts. In https://gitlab.com/groups/gitlab-org/-/epics/2587 we shipped Project Level Access Tokens. ### Background Example customer use case: In our GitLab setup, we have a group that contains multiple projects, as is recommended in the documentation. This allows us to make milestones and issue boards which span multiple projects, with one project being our primary and the others as support. Our pipeline is set up to create releases with release notes parsed from issue text using the project token and API. We also wanted to complete our automation by having the pipeline job close milestone issues, delete the issue board, and close the milestone. With a project token, the first is possible. However, it seems that the project token is not able to delete the board or close the milestone since they are part of the group, not the project. This is logical since you would not necessarily want to give a project the ability to alter its parent, but it does mean that we have no API route to alter group-level items using tokens. ### Intended users Developers, Release Managers ### User experience goal Users should be able to fully access the API for groups and projects underneath without needing to create a user or tie the token to a user. ### Proposal Introduce access tokens at the Group level. ### Permissions and Security Group maintainers. ### Workaround for self-managed If you are an administrator of a self-managed GitLab instance, you can create a group access token in the Rails console. The steps are documented in https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html#group-access-tokens