follow up to #569, we covered what happens to shares when the share's owner leaves, what else might be open? #654

New issue

Open

opened 2026-09-23 01:02:07 +00:00 by Cordy · 1 comment

Cordy commented

2026-09-23 01:02:07 +00:00

Owner

this issue is a deep-dive into scenarios. we solved what happens to the shares, spaces which the departed user is not the owner are out of scope as they simply leave them. as far as i remember, we implemented something for spaces which owner departs, double check this and report back here into a comment what would happen.
what happens to their personal folder when there is no shares? would this be able to be transfered if needed? or what would happen to the storage space? would that get free'd up? is it observable from anywhere from the Admin dashboard?

report findings here.

this issue is a deep-dive into scenarios. we solved what happens to the shares, spaces which the departed user is not the owner are out of scope as they simply leave them. as far as i remember, we implemented something for spaces which owner departs, double check this and report back here into a comment what would happen. what happens to their personal folder when there is no shares? would this be able to be transfered if needed? or what would happen to the storage space? would that get free'd up? is it observable from anywhere from the Admin dashboard? report findings here.

Cordy added this to the v0.7 — Closed beta (dogfood + hardening) milestone

2026-09-23 01:02:07 +00:00

Cordy commented

2026-09-23 01:12:24 +00:00

Author

Owner

Cross-reference: the transfer-scope work (shares-only by default per the approved departed-transfer-scope-rev1 mockup) surfaces this same question from the other side — a shares-only transfer deliberately leaves an encrypted remainder in /home/<departed>, summarised on the Departed-owners row ("n files · size, encrypted") with "Transfer remaining files" as its only exit until this issue adds the delete-unread one. When this lands, the estate row gains the second action; the summary line and the estate cache from the scope slice are the plumbing it will reuse. Tackled after the scope slice ships.

Cross-reference: the transfer-scope work (shares-only by default per the approved departed-transfer-scope-rev1 mockup) surfaces this same question from the other side — a shares-only transfer deliberately leaves an encrypted remainder in `/home/<departed>`, summarised on the Departed-owners row ("n files · size, encrypted") with "Transfer remaining files" as its only exit until this issue adds the delete-unread one. When this lands, the estate row gains the second action; the summary line and the estate cache from the scope slice are the plumbing it will reuse. Tackled after the scope slice ships.

Cordy referenced this issue

2026-09-23 01:34:09 +00:00

Transfer scope: shares-only by default, estate summary, full handover explicit (#597 scope) #655

Cordy referenced this issue

2026-09-23 22:11:23 +00:00

QA re-verification run: confirm the fixes for the #656 findings (post-fix pass for Opus) #697

Cordy referenced this issue

2026-09-24 00:52:12 +00:00

QA re-verification run: confirm the fixes for the #656 findings (post-fix pass for Opus) #697