This release includes more information about the No Site behavior update, which was initially launched to a small set of customers in 2022.
The No Site behavior update will be released for all users in v5 and v6, but only affects users in multi-site configurations.
No Site new behavior summary
We’ve changed the behavior of the default site No Site. These changes aim to simplify multi-site functionality and improve user experience overall.
No Site is the default site assigned to assets and work orders when a specific site is not selected.
Previously, assets and work orders labeled No Site behaved differently than other sites, including remaining visible when site filters were applied and affecting dashboard access. Notably, users assigned permissions (like Admin, Manager, or Technician) in No Site had those permissions reflected tenant-wide, retaining those permissions across all sites.
Now, No Site mirrors the behavior of other sites. No Site can be viewed, selected as a location filter, and assigned in permissions just like labeled sites. Also, permissions in No Site no longer apply to all sites, and so users assigned as Manager or Technician in No Site won't have those same permissions applied across all sites. However users with No Site Admin permissions will still retain Admin permissions across all sites, so that Admins do not lose permissions in this change.
No Site behavior change table
|
Previous behavior |
Updated behavior |
| Permissions assigned to Admins, Managers, and Technicians in No Site were applied to all sites. | Manager or Technician permissions assigned in No Site are applied to No Site only. Admin permissions still apply site-wide so that they don't lose access with this update. |
| Users’ No Site permissions affected dashboard access. | Users’ specific site permissions determine their dashboard access. |
| No Site remained visible when site filters were applied. | No Site adheres to filter rules. |