Context
After the soft-delete work in #4670, /settings/projects is now the place where superusers go to cancel a scheduled sandbox deletion or to delete a soft-deleted sandbox immediately. So this page is part of the recovery flow now.
The thing is, this page wasn't really designed with sandboxes in mind. A superuser opening it sees root projects and sandboxes all mixed together with no visual distinction. There's no way to tell which sandbox belongs to which parent project. And there's only one filter, which is search by name. For workspaces with a lot of sandboxes, finding the right row means knowing the name exactly.
Proposal
A few things worth thinking about:
-
Distinguish sandboxes visually. A small "Sandbox" badge on rows where the project has a parent, ideally with the parent name shown next to it. Or a dedicated parent column.
-
Show the relationships between projects. Today the list is flat. We could group sandboxes under their root, indent them, or just sort by root then by name so they appear together.
-
More filter options. Right now it's only name search. Things like "only root projects", "only sandboxes", "only scheduled for deletion" would help a lot.
Things to consider
- This is an admin-only page so the polish bar is lower than user-facing surfaces. But the soft-delete recovery flow lives here now.
- Sandboxes are projects, so anything we build should naturally cover both.
- Grouping or hierarchy is a bigger UI swing than just adding a badge or filter. Worth talking through scope before someone picks this up.
Not super urgent, the support escalation path works today, but it would help superusers a lot when managing workspaces with many sandboxes.
Context
After the soft-delete work in #4670,
/settings/projectsis now the place where superusers go to cancel a scheduled sandbox deletion or to delete a soft-deleted sandbox immediately. So this page is part of the recovery flow now.The thing is, this page wasn't really designed with sandboxes in mind. A superuser opening it sees root projects and sandboxes all mixed together with no visual distinction. There's no way to tell which sandbox belongs to which parent project. And there's only one filter, which is search by name. For workspaces with a lot of sandboxes, finding the right row means knowing the name exactly.
Proposal
A few things worth thinking about:
Distinguish sandboxes visually. A small "Sandbox" badge on rows where the project has a parent, ideally with the parent name shown next to it. Or a dedicated parent column.
Show the relationships between projects. Today the list is flat. We could group sandboxes under their root, indent them, or just sort by root then by name so they appear together.
More filter options. Right now it's only name search. Things like "only root projects", "only sandboxes", "only scheduled for deletion" would help a lot.
Things to consider
Not super urgent, the support escalation path works today, but it would help superusers a lot when managing workspaces with many sandboxes.