The "Organization Units" (OU) page allows to reflect your Organization Unit structure, mainly to categorize assets, users and other configurable elements and not "overburden" selection dialogues to Assistant users.

About Organization Units:

Many configurable items and shared resources (or more general "entitites") in Assistant have a 1:1 Item to OU assignment. This ensures that users only see the required items for selection that relate to their organizational structure.

  • Entities - such as a User - can be placed on root level or a child OU.
  • The OU rule follows an "up the tree to the root" rule.  This means the system shows items from a higher OU but not from another branch.
  • Rule of thumb: The deeper inside a child-OU an entity (e.g. a User) is placed, the fewer other entities will "know" about it and can see it in configuration dialogues.

Examples: 

  • When reading top to bottom: Items assigned on "Swiss Flight Stars Airline" level will be visible down the tree to "Valued Customers | "Reservation" but not visible to "Swiss Global Bank (Call Center)" as it is a different OU-branch.
  • When reading bottom to top:  "Concierge Service" can read up to > "Valued Customers" > "Swiss Flight Stars Airline", but not read items on "Reservation" on the same branch level and not from "Swiss Global Bank (Call Center)" as it is a different OU-branch.

    Example OU Structure:


Add Organization Unit

  1. To add add root node upon clicking link. 
    → A Pop-Up to define the new OU opens.
  2. Name the OU as needed and/or define a parent node.
    (lightbulb) In this case the new OU child node will be shown as under the parent OU.
    (warning) Note that the OU name must be unique. Otherwise a warning will appear.

Edit Organization Unit

Each organization unit can be managed over appropriate icons that are displayed on mouse over the name of specific organization unit:

You have the following options:

  • icon - edit name of organization unit and change Parent organization unit.
  • icon- remove the organization unit.
  • icon - add child organization unit directly underneath.

Remove Organization Unit

Organization unit deletion has a certain set of restrictions, depending on existing child-OUs and users assigned to them:

Deleted Organization Unit is:

Unit without assigned Users

Unit with assigned Users

Root without child units

Root unit is deleted immediately.

  • System does not allow to delete the root unit.
  • According 'Remove' pop-up appears with the list of assigned users.

Root with child unit(s)


  • Root unit is deleted. System does not allow to delete the child unit.
  • Child unit is added to the superordinate OU.
  • According 'Remove' pop-up appears with disabled option for deleting of child units.
  • System does not allow to delete the root unit.
  • According 'Remove' pop-up appears with the list of assigned users to the root unit.

Child unit

Child unit is deleted immediately.

A Pop-Up Appears with the following options:

  • Delete the root unit and add the children to the superordinate OU.
  • Delete the root unit with its children.
    List of users assigned to child unit is displayed on window.

Child (Parent) unit with additional child unit(s).

A Pop-Up Appears with the following options:

  • Delete the parent unit and add the children to the superordinate OU.
  • Delete the parent unit with its children.
    List of users assigned to child unit(s) is displayed for 'Delete the parent unit with its children.' Option.

A Pop-Up Appears with the following options:

  • Delete the root unit and add the children to the superordinate OU.
  • Delete the root unit with its children.
    List of users assigned to parent or its child is displayed depending on selected option.

Example Pop-Ups