How do you deal with users who are in two different companies?

If you create a group, put the user in the group and then provides access to the assets to that group - that could work…

Not exactly sure what assets you are referring to...that could change things, but maybe groups is your answer.

Or, maybe they have work specific email addresses they can use, therefore, the same person, but two different logins - assuming in two diff branches then.

Sounds like you are using the email address as the username? If you are OK with a single user having more than 1 profile, you can create a different username (assuming you haven't selected the hard option that only allows the email to drive the username (username = email).

As mentioned above, you can use groups to grant access to assets not necessarily in the same domain. Same goes for catalogues and other parts where groups are allowed for controlling visibility. (ie: channels)

When you mention “different company” are you referring to two different instances or are you using extended enterprise and this is a sub domain?

​@Bkatzman We’ve always forced unique email addresses, so somebody has to change. Our rule of thumb was first one in gets to keep it.

​@lrnlab thanks for the suggestion. Yes, the situation involves an Extended Enterprise client who is trying to import providers that are already in the root domain under their company. 

I would suggest you create a 2nd domain and not leave anyone at the root. You’ll have better control this way. Also if you ever wanted to enable SSO for one group and not the other, the using a 2nd domain will allow that since if you enabled this at the root, those that are in your SSO directory could not get in, unless you leave the login panel with the SSO button in place. You’ll have additional config options when using the sub domains...just a thought.

Unfortunately, the user database is shared across any extended enterprises or domains you would create. Best way is unique usernames for each account