<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ### Problem to solve As we move towards [Mass integration at the group and instance level](https://gitlab.com/groups/gitlab-org/-/epics/2137), "Project services" are increasingly mis-named. A "Project service for a group" is really weird. The following makes sense when it's on a `Project Settings` page, but what happens when this functionality is available at the group too? [](https://gyazo.com/9144136a9962fc8fd4ca43650c470e8c) ### Further details * Whatever name we go with shouldn't include "projects" * "services" can mean other things in other contexts ### Candidate names * Integrations * Services * _Something else? Say so in the comments!_ ### Proposal 1. Update places in the UI where we refer to `Project Services` (i.e. on `http://gitlab.com/<group>/<project>/-/settings/integrations`) 1. Update the docs to scrub any reference to this and change to new name 1. Change names in the codebase to reflect new naming