Bulk Editing - Services and Users only: This feature is currently intended to allow only service and user bulk editing. Further configuration entities will be made available at a later date.

¹ Changing User “Services” and “Roles” tabs are disabled during Bulk Editing. Changing roles would have large-scale implications on the existing Service Provisioning and User Assignment Types in Nimbus.

² Changing these Service options in bulk would require simultaneous work on related and dependent Configuration entities.

³ Addon licenses can be (un)assigned in bulk - same as via License Management. However, each service needs to be individually configured, as the related Settings tabs are not yet supported in Bulk Edit.

⁴ Must remain unique for the selected entities during bulk edit, e.g. due to a Service being fixed/synched to a "MS Teams-based" channel.

💡By design: Listed below are active design decisions, please do not report these as issues.

☝ No Undo Option - Bulk editing does NOT provide any way of undoing your changes. We recommend making small changes at first to see the effects.

• Maximum 25 entities can be edited at the same time. 
  • If the total number in a list is larger than 25, “Select All”  is disabled.
  • You can filter your entries below this threshold to apply changes.
• No bulk creation/deletion  - While in bulk edit mode, entities cannot be mass created or deleted (as a precaution).
• Dependent change confirm - Certain features rely on dependencies (e.g. an applied change showing additional feature tabs). For this reason you need you to confirm pending tab changes first before applying further bulk changes.

💡Known Limitations: (technical limitations and issues that we already know about.)

• “Disappearing” Details view - Confirming a bulk change via tab change shows a saving dialog as intended. However, the “Details” inspection feature was only visible on the previous tab bottom and thus cannot be shown on the new tab.
• Limited Bulk Operation view - The “Details” of bulk operations - next to the “Save & Apply” button - only show a complete set of changes, not the delta changes.
  

With this change, it will be possible to modify Organization Units of many entities (e.g. users) simultaneously. ☝ This will inevitably create “Non-Path References” (NPR) warnings in your UI.

What does Non-Path Reference mean?

A Non-Path Reference (NPR) is signaled with a small warning icon in the UI, indicating that “Reading along the path / up to the root” rules were violated with a prior Organization Units change on an entity.

🤔What is an entity? Anything configured within Nimbus that has its own OU - users, services, workflows, profiles, etc. 

🤔Is there a risk to creating NPRs? Your existing Nimbus references (and related services) will continue to operate even with NPR warnings, but the changed entity (e.g. a OU-moved user) will not be visible for selection anymore once removed. All existing dependent entities (e.g. a service defining an “NPR” flagged user) will still consider this user for tasks distribution as long as the user itself is not actively removed from the configuration.