Skip to main content

i4connected Knowledgebase 5.6

Move Organizational Unit


Check out this article and learn more details about the Move Organizational Unit panel, available under the Move entity feature.

When moving an Organizational Unit, the user needs to select as an entity the desired Organizational Unit to be moved, using the Object filters panel.


The Object filter panel


Selection of the destination Organizational Unit will be organized using the Object filter panel. For more details about the Object filter, please visit the dedicated article

After all the move entity and destination entities are selected, the user can click either the Apply button, to proceed with the move operation, or the Close button, to dismiss the operation.


The selection of moving Organizational Unit


Moving an entity can take a long time to finish. A notification will be shown when the process is finished.

The move operation starts in the background by clicking the Apply button. A server notification message is displayed when the Organizational Unit is moved to the destination entity.


The server notification message


Since the Move entity panel itself is not guarded by specific permission, the users having the "View Organizational Units" permission enabled, will be able to select as Move entity or Destination entity, all the Organizational Units that he/she can see. However, when the actual move operation is initiated, the system will check if the Move entity or the Destination entity can be managed or not.

When not enough rights are available, a warning toast message will be displayed on the screen.


Example of toast message

When moving an Organizational Unit, the assigned entities are transferred to the new structure, as follows:

  • The organizational unit keeps its directly assigned roles, along with their assigned roles and permissions. To this list, the users inherited from the new higher hierarchical structure(s) are added, and their effective permissions are recalculated;

  • The organizational unit assigned to the moved organizational unit will also be transferred to the new hierarchical location, along with their dependencies, and the directly assigned users with their roles and permissions. The sub-organizational units will also inherit the list of users, assigned to the new hierarchy, from all the structures positioned on a higher hierarchical level.

  • The moved organizational units and sub-organizational units will carry their devices to the new location, along with their device dependencies:

    • All the directly assigned users to a device will be transferred as dependencies of that device. Similar to the organizational unit, the device will also inherit users assigned on a higher hierarchical level;

    • All the Signals, their assigned users along with Signal measurements;

    • All the assigned Device Response Teams;

    • All External Alarms;

    • All the Alarm script lists;

    • The Device's i4designer Application Mappings, if there is one set to Default;

  • The moved organizational units will be transferred along with their Measure aggregations, Organizational units response teams, and Entity variables;

  • All KPI Cross-links;

  • All shifts.


    When moving the Organizational Units with shifts assigned, the system checks if the destination Organizational Unit also has shifts assigned. In case the destination Organizational Unit already uses the shifts of the origin Organizational Unit, the shift assignments will be removed, in order to avoid the creation of duplicates.

    Further on, in case the destination Organizational Unit does not have the respective shifts assigned, the origin Organizational Unit will preserve its shift assignments.

  • If a default i4designer application is available for the moved organizational units, this will be transferred, as well.

The Move Organizational Unit operation is marked by the system as an auditable event. For more details about the Audit Events, please visit the dedicated article: