Administrator Workflows

Modified on Mon, 6 Oct at 11:45 AM

Do end users need individual accounts? Can we use shared accounts?


Cloud Licensing is designed to be used with individual accounts for each user. The Chaos account

provides access to all Chaos products and license types, including named and floating licenses, and

cloud credits.

Using Cloud Licensing with individual user accounts unlocks the full benefits and features of Chaos

products – including the Cosmos library of assets, Cloud rendering, Cloud Collaboration, AI-powered

features. Some of these services are only useful if each user has a separate account.

For administrators, having separate accounts for each user also provides visibility into which user is

currently using a license, as well as historical statistics for license utilization that can be useful for

planning.


What is the easiest way to give all our users access without adding them one

by one?


We offer the ability to add users in bulk to the organization in My Chaos by uploading a list of email

addresses.

Customers can also integrate their corporate IdP to enable single sign-on (SSO) and automatic

provisioning of user accounts. This makes it easy for large organizations to manage user accounts

provisioning and de-provisioning.


Can we transfer a user’s seat to another person immediately?


Yes - you will not lose this flexibility with Cloud Licensing.

Floating license seats are released as soon as the user stops their application. This makes the license

available for any other user in the organization who needs it, on a first-come, first-served basis.

Named licenses need to be assigned to an individual user via the My Chaos portal. However, if the

assigned user no longer needs their license, the administrator can assign it to another user - the

change takes place immediately.


Do I need to log in on my render node machines?


Render Nodes can still use the centralized License Server setup, especially if you don’t have GUI access

to login on the machines.


What’s the recommended setup for render farms: Cloud Licensing or a

License Server?


For a large number of render nodes, we still recommend the License Server deployment, as a way to

centralize management.

For individual customers and small teams, signing in with your Chaos account to access licenses

directly from the cloud would be the easier approach.


Can we transfer seats from a license server to the cloud without downtime?


Yes. Switching to Cloud Licensing is seamless as long as the individual users are added to the

organization. This can be done in bulk from My Chaos.


How do we handle shared lab machines or classroom settings? Are student or

lab environments supported without individual logins?


Individual users can benefit from using their own accounts. This provides them with their own space in

Cloud Collaboration and access to all cloud-based and AI services that require a login. Large

organizations can implement single-sign on (SSO) to minimize the need for account management by

automating provisioning and de-provisioning.

Alternatively, you can still use your existing License Server setup if you prefer.


Can I automate my installation with a script?


Yes. You can create a silent installation script and deploy the same product with the same configuration

to multiple machines. You can read more about it in the Silent Installation pages of the product

documentation. Here’s some examples: Enscape for SketchUp, V-Ray for 3ds Max.

With Cloud Licensing, each user will be asked to log in with their account only once.


What is the EOL timeline for the on-premise License Server? Will there be

security patches for it?


The on-premise License Server remains actively supported with no EOL planned. We will keep updating

the License Server with improvements, security and bug fixes.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article