After talking with support, I got a clean answer here:

Each user has their own workspace. Any 'work' (experiment runs for example) done on a workspace by a user will be saved on his own workspace (by default). User A can invite user B to his workspace. Any 'work' done by user B on the A's workspace will be saved there. User B can leave the workspace of user A and all their 'work' (Experiments) will remain in the workspace of user A.

There is no 'organization' concept in the community server (

). It's all users and workspaces. Users can invite colleagues into their workspace so they can create a central workspace to work from.

Changing 'ownership' of a workspace is not a supported feature currently, this is why I suggested handing over the account credentials to a colleague.

Our solution was to create a new workspace under an administrator account for our company and invite all users in the company to that workspace. Enterprise was waaaay too expensive.