Should 1 user be able to be in two organisations

[peterdudfield]

Should 1 user be able to be in two organisations. @katyalmohit to fill in more

[katyalmohit]

I wanted to clarify the expected behavior around users and organisations, as I'm seeing something a bit confusing while testing via the toolbox UI and gRPC.

What I tried

1. created two orgs: org_a and org_b
2. created a user test_user in org_a
3. verified with Get User Details --> user belongs to org_a

4. added the same user to org_b using Add User to Organisation

5. fetched user details again just to check if the org is updated or not

6. tried removing the user from org_a

7. tried fetching user details again

[katyalmohit]

Observations

• it looks like the user is still associated with org_a even after being added to org_b
• after removing from org_a, the user seems to be removed entirely, instead of still existing in org_b

So, I have a few questions with that:

• is a user intended to be a single-organisation only or multi-organisation?

• when calling add_user_to_organisation, is it supposed to:
  move the user from old or to the new one? or add an additional org membership?

• when removing a user from one org, should the user still exist if they belong to another org?

[devsjc]

This is a good find, and thanks for the screenshots. The RemoveUserFromOrg deletes the user entirely from the users table, in order not to have users lying around that are not associated with an org. I suspect we don't want users associated with multipple orgs, so that's where the error is here.

You shouldn't have been able to create two users with the same oauth id, but it looks like here you might have done. Can you do the following, in a fresh instance:

Make two orgs, then add a user with the same oauth id to each one (this should fail) - and let me know if it does?