This documentation is for Dash Enterprise.
Dash Enterprise is the fastest way to write & deploy Dash apps and
Jupyter notebooks.
10% of the Fortune 500 uses Dash Enterprise to productionize AI and
data science apps. Find out if your company is using Dash Enterprise.
This page applies to Dash Enterprise 5. If your organization uses Dash Enterprise 4, users can self-assign license seats by initializing an app or going to Usage & Guides.
Dash Enterprise has license seats for you to assign to members of your organization who manage Dash apps. License seats are required for users to create apps, become co-owner of apps, and view documentation. They are not required to access and use Dash apps.
You must be an administrator to see license seat information and manage license seats.
If a user without a license seat attempts to perform an action restricted to licensed users, they’ll see a License Seat Required message.
<img>
You can view license seat information in Dash Enterprise by going to Users. The number of assigned license seats is displayed under License Seats.
When you assign a license seat to a user, the number of assigned license seats will update the next time that the user logs in.
Subtract the number of assigned license seats from the total that your organization purchased to know how many are available.
You can allocate license seats to users by assigning them the licensed_user role in Keycloak. Removing the licensed_user role revokes the license seat.
About revoking license seats: Revoking license seats causes users to lose ownership and co-ownership of apps, and is not fully supported. Dash Enterprise does not currently support transferring apps between users,
so we recommend caution when managing license seats. Instruct Dash app developers to begin using Dash Enterprise once you are satisfied with how theirlicensed_userrole is assigned, and
be careful not to accidentally remove the role.
For full details about assigning roles, including how to speed up role assignment by mapping roles to groups, see Assigning Roles.
When Plotly makes changes to your license, such as updating the expiration date or adding more license seats, you’ll need to apply the change to Dash Enterprise.
Important: You’ll need to run some kubectl commands at the end of this procedure in order for Dash Enterprise to remain in a healthy state. These commands rotate pods,
which causes a short downtime (a few seconds to one minute) while new pods are spinning up. Plan accordingly when applying license changes.