This release includes the following changes:
Updated behavior for adding licenses
Before you begin
This release note details how to add seats before May 2025, when the e-commerce site was launched. For the most up-to-date way to update licenses, see Add or remove licenses.
We’ve simplified the behavior for adding seats in the CMMS. Users can now add licenses via the Account Settings feature if they are either:
- An administrator, or
- An account owner and assigned a user group that has the necessary permissions (described below)
This means that an administrator must assign the necessary permissions to a user group that their account owners are part of. Otherwise, the account owners won't be able to add licenses.
The following permissions are required to add licenses:
- The Can See Settings and Can See Account Settings Menu Item menu permissions:
- The Account Settings page permissions:
- The Add More Licenses page permissions:
Notes
- Administrators can add licenses in both Account Settings and when activating a new user, regardless of whether they are account owners.
- Non-admin users who aren't account owners can't add licenses, even if they're assigned a user group with these permissions enabled.
- In v6 user management, non-admin account owners can't add licenses when activating a new user; they can only add them in Account Settings. If they try to activate a user but don't have enough licenses left, a message appears directing them to contact their administrator.
The table below shows four example user configurations and whether that user would be able to add licenses in Account Settings:
| User | Administrator | Account owner | User group has necessary permissions | Can add licenses |
|---|---|---|---|---|
| Carolyn | Yes | No | Yes* | Yes |
| Anuj | No | Yes | Yes | Yes |
| Kevin | No | Yes | No | No |
| Annie | No | No | Yes | No |
* Administrators are assigned all permissions automatically, meaning that this user would already have the necessary permissions.
To learn more,
Bug fixes
The following bugs were fixed in this release:
| ID | Description |
|---|---|
| 46436 | Fixed an issue where Requestor and Requestor email details were not displayed in notifications sent from custom workflows, despite these fields being available in the workflow. |
| 60306, 63658, 66563, 66739, 67951, 75869, 78406, 79670, 94726 | Fixed an issue in some tenants that caused work order statuses or assets to be displayed incorrectly when configuring widgets. |
| – | Fixed an issue where you could delete parts from asset records, even if they were part of a BOM group. |
| – | Fixed an issue where v6 usernames were not recognized by the import feature, resulting in some users unable to import work orders and scheduled maintenance records. |
| – | Fixed an issue where the work order list would not refresh when it was reopened. |
| – | Fixed an issue where an unrelated error message would display when moving assets with closed work orders. |