The research question
Two employees use separate Windows accounts on one workstation. A desktop CRM may run local services for both, but a convenient shared cache or endpoint can accidentally cross the boundary between their document collections. Localhost communication and physical proximity are not evidence that the second user should inherit the first user’s application data or permissions. Local-first research connects collaboration with ownership and useful offline work. The design challenge is to specify which local operations remain meaningful when other participants or the authority for a business decision cannot be reached.
A concrete design choice
The proposed desktop plan assigns storage, runtime state and protected keys to the appropriate profile. Switching users should not attach the new session to another person’s database, browser state or background process. A local request across profile boundaries needs the same explicit identity and scope checks as a network request. Diagnostic files and temporary exports also belong in the boundary review, because they can contain excerpts even when the main database is separated. The design should be validated under ordinary user accounts rather than only while an administrator runs the application.
What would demonstrate usefulness
Test two simultaneous profiles, fast user switching and identical visible account names in different sessions. Verify data files, local endpoints and cached previews. The useful result is evidence that one profile cannot inspect the other’s collection through routine application paths, not merely separate folders with similar names.