Logic of Which Team to Pull License (Domain Linked, Multiple Teams)

I have a couple questions regarding managing users, licenses, and teams:

Scenario 1:
Team A - 10 licenses of Rhino 7 - 20 members added to team (all with email @microsolresources.com)
Team B - 10 licenses of Rhino 7 - Domain Linked (microsolresources.com)

When a member of Team A opens the software for the first time and logs in with their email, will it prioritize pulling the license from Team A, despite having an email with the same domain as the domain linked Team B?

Scenario 2:
Team A - 5 licenses of Rhino 7
Team B - 1 license of Rhino 7

User A is a member of both teams and assume that when they login it pulls a license from Team B. Will it prevent other users that are only in Team B from accessing any more licenses (even though another license is available for User A in Team A)?


@jfreund Recognize this is an old thread, but was wondering if you got an answer to this? Specifically we’re wondering about the ability to have two Domain joined teams, to “secure” the licenses from Team A against use by users only in Team B.

In our idea a user would only be a member of a single team.

I have the same question here. I have two licenses assigned to Team A (2 users) and Team B (1 user).

Team A: License 1 for User X, User Y
Team B: License 2 for User X

When user X logs in, it uses the license 1 for Team A. User Y can’t find a license. Is there any way to change team while getting licenses?

So you want User X to be able to use up to two licenses, and if they’re using both, then User Y can’t use any licenses? But if User Y gets a license first, then User X can only use one? Why?

It’s not possible to have two different domain linked teams belonging to the same domain. But without domain linking, you can do what you describe.

Not exactly that. Nobody will use two licenses at the same time.

Firstly, each user has a single Rhino account.
User X uses Rhino in two separate locations in different days where Team (company) A and Team (company) B has their own licenses, let them name LicA and LicB.
User Y is a member of Team A only and is unrelated to Team B.

User X goes to Team B establishment and opens Rhino, but the license manager takes LicA instead of LicB (because obviously license manager doesn’t know where X is working at that time). This causes User Y in establishment of Team A to not find a license because the single one was taken by User X although X is in Team B.

We may need a license switcher so Rhino accounts can choose which license they are using in that session.

@brian Thanks for confirming. Without domain linking, we loose the SSO feature and single point of management which is unfortunate.