Q100734: Best practices for using the Team OrgAdmin Dashboard

Luca Muscia

Updated: May 12, 2026 22:43

Created: March 04, 2026 15:00

SUMMARY

In this article we will be discussing the best practices for using the Organization Administration (OrgAdmin) Dashboard. While the OrgAdmin Dashboard is fairly straightforward to use, there are common pitfalls that can cause blocking issues if not avoided. This article contains a list of best practices to keep in mind, especially if you are the administrator for your Organization.

MORE INFORMATION

Please see our recommended best practices for Team licenses below.

Admin:

There must always be an Admin.
It is common for users to become accidentally locked out of their Organization because they remove themselves as Administrator, and do not assign any other user that role. To check who the Admin role is assigned to, navigate to the Users panel, and select Details next to the user.

In the Details page, you will see an Admin toggle. This will be on by default on your user when you access the OrgAdmin Dashboard for the first time. If you would like to remove Administrator privileges from yourself, you can toggle this off. If you are the only Admin, do not toggle this off until you have fully added another user as an Admin via these steps:

How to Promote Users to Admin Status

Employees group:

There must always be a group with the type set to ‘employees’, and all users must be in this group.

When you access the OrgAdmin Dashboard for the first time, you will have a default Employees group already created. If you navigate to your Groups panel, and inspect the Details of your default Employees group, you will see a Type dropdown. This will by default be set to employees.

When adding users to your Organization, you should ensure that they are always added to this default group. You can later add them to any additional groups as well, but you should think of this Employees group as the baseline group.

This can become confusing if your Organization includes people who are not ‘employees’ in the traditional sense (freelancers, for example). It may be tempting to create a Freelancers group, for example, and add new users to that instead. However, this will cause access issues.

More information on creating groups can be found here: Creating Groups to Control Users’ Access to Licenses

Entitlement descriptions:

Descriptions must be added to new Entitlements.

As an Admin, you may want to create a new license Entitlement group - for example, let’s say you wanted an entitlement that only contains Mari licenses. When you navigate to the Entitlements page, you will see that your default entitlement has a Description column, which is populated by default.

When creating a new Entitlement, you will be able to write a description for this Entitlement. You must ensure that this text field is not left blank, as this will cause errors.

Reservations:

It is possible to reserve licenses for users with the OrgAdmin Dashboard. This can be very helpful when you need to ensure a certain artist has guaranteed access to specific licenses. You can find more information about reserving licenses here:
Reserving Seats For Specific Users

However, please note that once a license is reserved for a certain user, it cannot be used by any other user until that reservation is released. Therefore, we do not recommend reserving any licenses unless you have a specific scenario where you need a user to have guaranteed access to a license.

Running earlier Nuke builds:

When running builds of Nuke prior to:

16.0v3

15.2v3

15.1v8

15.0v8

14.1v8

you may encounter an Failed Checkouts error:

This is due to a required server-side change to our licensing system that affected communication between our products and the server.

We provide workarounds and further details for this issue via the following article:

Q100721: Advisory on resolution of Teams Login-Based licensing system errors