[platform] Each member instance should get its own named context (default plus username), not a shared or leftover one #305

Closed
opened 2026-06-18 06:00:26 +00:00 by mik-tf · 1 comment
Owner

When a member instance is provisioned, the member should land in their own workspace context by default. Right now the context model is muddled on a live member: the desktop is operating in a context called "geomind", hero_office defaults to a context called "demo" (its DEFAULT_CONTEXT value), and the member's actual user is "joriss", so there are three different names and none of them is clearly the member's own space. A member also should not see an admin style context switcher that lists other contexts (core, demo, geomind).

The fix is at provision time: give each member a sensible default context plus a context named for their username, set HERO_CONTEXTS and DEFAULT_CONTEXT (used by hero_office and the desktop) to that member context, and make the desktop and the Office app default to it with no context picker shown to a regular member. This gives each member a clean, sovereign per user workspace and removes the "why am I in geomind or demo" confusion.

This is mostly deployer provisioning work, plus aligning the desktop and hero_office context defaults.

When a member instance is provisioned, the member should land in their own workspace context by default. Right now the context model is muddled on a live member: the desktop is operating in a context called "geomind", hero_office defaults to a context called "demo" (its DEFAULT_CONTEXT value), and the member's actual user is "joriss", so there are three different names and none of them is clearly the member's own space. A member also should not see an admin style context switcher that lists other contexts (core, demo, geomind). The fix is at provision time: give each member a sensible default context plus a context named for their username, set HERO_CONTEXTS and DEFAULT_CONTEXT (used by hero_office and the desktop) to that member context, and make the desktop and the Office app default to it with no context picker shown to a regular member. This gives each member a clean, sovereign per user workspace and removes the "why am I in geomind or demo" confusion. This is mostly deployer provisioning work, plus aligning the desktop and hero_office context defaults.
Author
Owner

The desktop landing part of this (each member lands in their own named workspace) shipped and is live on all members. The two remaining parts, Office defaulting to the member's own workspace and hiding the admin-style context switcher from regular members, are now tracked together with the rest of the member Cockpit work in lhumina_code/home#306 (the context switcher part depends on the workspaces backend, lhumina_code/hero_osis#66). Closing here in favor of that single tracking issue.

The desktop landing part of this (each member lands in their own named workspace) shipped and is live on all members. The two remaining parts, Office defaulting to the member's own workspace and hiding the admin-style context switcher from regular members, are now tracked together with the rest of the member Cockpit work in https://forge.ourworld.tf/lhumina_code/home/issues/306 (the context switcher part depends on the workspaces backend, https://forge.ourworld.tf/lhumina_code/hero_osis/issues/66). Closing here in favor of that single tracking issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/home_lhumina#305
No description provided.