A personal account and a company workspace can share a login without sharing ownership of every record. Make the owner of each resource explicit so creating, moving, exporting, and deleting data follow predictable rules.
This distinction matters when someone joins a company after using the product alone or leaves a company while keeping their personal account. A global user identifier is not a complete resource-ownership model.
Name the ownership boundary in the product
Show whether the current workspace is personal or company-owned. Store a clear owner reference for each resource and define which roles can read, edit, transfer, or delete it. Avoid interpreting a missing organisation ID as an accidental mixture of personal and shared data.
Define billing scope separately. A personal subscription should not automatically grant company-wide access unless that is the explicit product rule. Likewise, removing a company member should not cancel their unrelated personal subscription.
Walk through a fictional study migration
Imagine Leena creates a personal research study, then joins a company workspace. The company asks to move the study and its responses into the shared account. That is a data transfer with permission and respondent-expectation implications, not just a change to a menu label.
Require an explicit transfer operation with a named source, destination, eligible actor, and stated effect on access. Test whether existing links, reviewer access, exports, and billing entitlements behave as intended afterward. If transfer is not supported, explain the limitation and provide an appropriate alternative rather than silently copying private responses.
Now remove Leena from the company. The company-owned study should remain under the company's rules, while her personal studies follow their own lifecycle. Test account deletion separately because it may affect both kinds of ownership and require additional decisions.
Prevent context defaults from becoming ownership decisions
A default workspace can make creation convenient, but show the destination before consequential actions. A user returning from an invitation may not realise that the active workspace changed. Keep creation forms and uploads attached to an explicit owner.
Review exports and search. Personal results should not appear in company-wide reports unless authorised by an intentional sharing model. Cached results also need the same separation across workspace changes.
The tradeoff is flexibility versus lifecycle complexity. Supporting personal-to-company transfers may be valuable, but it creates rules for links, history, billing, and deletion. A pilot can postpone transfer while still keeping ownership clear from the start.
The StackFlight case study provides related study-product context. Leena's migration is fictional and does not imply that this personal-and-company workflow is currently offered there.
Questions about workspace ownership
Does the creator always own the data?
Not necessarily. The product's explicit workspace and ownership rules determine control, subject to the relevant agreements and requirements.
Should leaving a company delete personal work?
Treat membership removal and personal account lifecycle separately. Test the intended result rather than relying on a broad deletion cascade.
What should be defined before adding teams?
Define resource ownership, creation defaults, transfer, billing scope, and departure behaviour. Bring those transitions to a workspace-model review.