I have posted about this before but…
Have a company with 3 fixed computers running Rhino in a production shop environment plus one owner/manager and one other senior employee who have laptops and may need to use Rhino from time to time remotely, but probably not at the same time as the other fixed computers. Any shop employee can use any of the three fixed computers, some of them are dedicated to running machines such as a laser, CNC etc.
Team creation:
Owner/administrator sets up a Cloud Zoo account using a company e-mail and password only they know (so it’s only them who have access to the account). Owner puts 3 or 4 licenses into the team section of the account.
Shop setup 1 possibility:
The admin automatically has access to a team license on their laptop. The admin invites the other person who has a laptop to create their own account and join the team.
The admin personally sets up the Rhinos on the fixed computers by logging into the account using their password. The normal users of these computers do not have access to the log-in, but as the computers are always running and logged in this should not be a problem. Basically the three fixed machines “belong” to the admin. Worst case, it’s the admin that needs to re-log a computer if it gets logged out. The users of the fixed computers do not need to have a Rhino account/login and do not have access to the licenses outside of the workplace.
Shop setup 2 possibility:
The admin invites all the people who might use the fixed computers plus the person with the laptop to create their own Rhino account and join the team. Nobody really cares whose session is actually logged in when using a given fixed computer, if it gets logged out, anyone who is a team member can log it back in with their individual Rhino account which is linked to the team.
Any member of the team can possibly log in from home or away and use one of the team licenses - thus possibly preventing someone at the workplace from using one if the number of licenses is limited and the person who took the license remotely can’t be reached to log out. As far as I know, with the Cloud Zoo the admin does not have the possibility to remotely disconnect a user. Not sure if removing a member from the team will immediately disconnect the user and free the license they’re using, I think not. So a certain small usability risk here.
Other possibilities? I know Setup #2 looks to be the “preferred” way.