Skip to content
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

Epic: Improve control over shared running workspace URLs #12444

Closed
jldec opened this issue Aug 26, 2022 · 4 comments
Closed

Epic: Improve control over shared running workspace URLs #12444

jldec opened this issue Aug 26, 2022 · 4 comments
Labels
feature: share running workspace meta: stale This issue/PR is stale and will be closed soon type: epic

Comments

@jldec
Copy link
Contributor

jldec commented Aug 26, 2022

Shared running workspace can be accessed by anyone with access to the workspace URL. There is no indication to the workspace owner when other users open the shared workspace in their own browser.

Screenshot 2022-08-26 at 16 16 26

Suggested improvements:

  1. Single-use shared workspace URLs
  2. User-scoped shared workspace URLs
  3. Indication (to the workspace owner) when others are accessing their shared workspace.
  4. Confirmation prompt to allow/deny shared workspace access.
  5. Audit trail of shared workspace access.
@atduarte
Copy link
Contributor

Related with #13188

@gtsiolis
Copy link
Contributor

Some thoughts:

  1. I don't think investing time for generating single-use or user-scoped shared workspace URLs is worth the effort.
  2. The fixed share button that also includes the state sounds perfect for surfacing this kind of information, see relevant discussion (internal).
  3. Maybe we could bundle all these Gitpod-specific information in a dedicated Gitpod view in the remote explorer, see relevant discussion (internal).
  4. In the meantime, we could use this fixed space for the share action and state to also surface user avatars that access the shared workspace as described in Improve workspace sharing user flow from the dashboard #4112, and we could also use this pattern also in the dashboard, see screenshot below.
User avatars accessing a shared workspace (Early Design)
image

@stale
Copy link

stale bot commented Dec 23, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Dec 23, 2022
@stale stale bot closed this as completed Jan 3, 2023
@github-project-automation github-project-automation bot moved this to Awaiting Deployment in 🌌 Workspace Team Jan 3, 2023
@github-project-automation github-project-automation bot moved this to In Validation in 🍎 WebApp Team Jan 3, 2023
@loujaybee loujaybee reopened this Mar 23, 2023
@github-project-automation github-project-automation bot moved this from In Validation to Scheduled in 🍎 WebApp Team Mar 23, 2023
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Mar 23, 2023
@loujaybee loujaybee changed the title Improve control over shared running workspace URLs Epic: Improve control over shared running workspace URLs Mar 23, 2023
@stale
Copy link

stale bot commented Sep 17, 2023

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 17, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
@github-project-automation github-project-automation bot moved this from Scheduled to In Validation in 🍎 WebApp Team May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: share running workspace meta: stale This issue/PR is stale and will be closed soon type: epic
Projects
Status: In Validation
Status: Done
Development

No branches or pull requests

4 participants