-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow a project owner to disable shared workspaces #6328
Comments
FYI, This is also cross-linked[1] in the docs. 🎗️ |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Introducing We also recently disabled snapshots for repositories users don't have access to in #8306. |
Currently the docs say:
Would it be technically feasible with the existing GitHub API to for example, allow anyone with a GitPod account that is linked to a GitHub account which has access to this repo to access the workspace? Thank you. |
GitHub organization could be a good security boundary to allow/deny. Not sure if other platforms (i.e. GitLab, etc.) have a similar construct. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
+1 for instance and team level setting to deactivate workspace sharing. From the docs it seems you are well aware of the risks. I see this as a blocker for a wider rollout, as sharing a workspace like this equals leaking SCM credentials. |
Based on feedback we received via the docs feedback widget: "Can we disable sharing globally for teams (as a security measure)?"
The text was updated successfully, but these errors were encountered: