<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=509064) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> We mention using the PAT scope `ai_features` [here](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#personal-access-token-scopes) to address a JetBrains security vulnerability, but starting from [this](https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin/-/merge_requests/313/diffs#8ec9a00bfd09b3190ac6b22251dbb1aa95a0579d_43_40) MR, we updated the configuration steps to use the `api` scope of PAT and this was subsequently ported over to the [documentation](https://docs.gitlab.com/ee/editor_extensions/jetbrains_ide/setup.html#create-a-personal-access-token). It was noted from a test 5 months ago that there were some issues with using the PAT scope `ai_features`: https://gitlab.com/gitlab-org/editor-extensions/gitlab-jetbrains-plugin/-/merge_requests/447#note_1958848396. We may need to make some tests to confirm if there are still issues before updating the documentation back to `ai_features` scope for JetBrains IDE. <!-- If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"` -->