[deployer] A new deployment should always land in a real organization; keep Unassigned as a recovery view

mik-tf commented

2026-06-17 13:27:39 +00:00

Owner

Today the Launcher deploy flow already requires an organization (you pick an existing one or name a new one), but a lower level standalone add can leave a member with no organization, so they show up under the Unassigned view. Unassigned reads like a limbo state, and we do not want to reintroduce a hardcoded default organization (that was built once and reverted, because it couples the server to a fixed label and shows up as a fake deploy target).

Proposed model: every new deployment produces a real, named organization. For a single person, prefill a sensible name (the member username, or a name like "Alice's organization") that the operator can rename, so a solo deploy still gets a real, settings capable home from the start. Unassigned then stays only as a small recovery view for members that predate organizations or were orphaned when their organization was deleted, surfaced as a call to action to move them into an organization, never settings capable and never a deploy target.

Out of scope for now: a consumer mode that hides the word organization for solo users. The model above stays compatible with adding that presentation layer later.

Part of the Launcher work in lhumina_code/home#291.

Today the Launcher deploy flow already requires an organization (you pick an existing one or name a new one), but a lower level standalone add can leave a member with no organization, so they show up under the Unassigned view. Unassigned reads like a limbo state, and we do not want to reintroduce a hardcoded default organization (that was built once and reverted, because it couples the server to a fixed label and shows up as a fake deploy target). Proposed model: every new deployment produces a real, named organization. For a single person, prefill a sensible name (the member username, or a name like "Alice's organization") that the operator can rename, so a solo deploy still gets a real, settings capable home from the start. Unassigned then stays only as a small recovery view for members that predate organizations or were orphaned when their organization was deleted, surfaced as a call to action to move them into an organization, never settings capable and never a deploy target. Out of scope for now: a consumer mode that hides the word organization for solo users. The model above stays compatible with adding that presentation layer later. Part of the Launcher work in https://forge.ourworld.tf/lhumina_code/home/issues/291.