<!--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=550129) </details> <!--IssueSummary end--> <!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/issues * For information about documentation content and process, see https://docs.gitlab.com/development/documentation/ --> - [x] Start this issue's title with `Docs:` or `Docs feedback:`. ## Problem to solve GitLab does not appear to have explicit documentation detailing the support scope or limitations for third-party extensions in Workspaces. The documentation focuses on: - How to enable the extension marketplace - [Manage extensions](https://docs.gitlab.com/user/project/web_ide/#manage-extensions) - Configuration options for administrators - [Configure VS Code Extension Marketplace](https://docs.gitlab.com/administration/settings/vscode_extension_marketplace/) - Technical setup requirements - [Configure workspaces](https://docs.gitlab.com/user/workspace/configuration/) With no mention of scope of support for the third-party extensions, the handling of support requests for extension related issues is difficult at best. We do have a general support statement, [Out of Scope](https://about.gitlab.com/support/statement-of-support/#out-of-scope) - _Troubleshooting non-GitLab components_, but do we still need to eliminate GitLab being the root cause for a third-party extension not working? ## Proposal Provide a statement that clearly states the scope of supportability for third-party extensions, and to what degree GitLab are committed to troubleshooting their use and interaction with GitLab components, e.g. WebIDE / Workspaces. ## Who can address the issue Product team.