Support

Submit a ticket My Tickets
Welcome
Login  Sign up

ADU Management Tool (moving data between ADUs)

ADUs (Appogee Divisional Units) are designed to represent divisions within your company. However, when ADUs are first enabled, you will need to move data (Teams, in particular) to the relevant ADU. 


It is suggested that when your ADU/Team structure has been configured, that moving data between ADUs is kept to a minimum.


The ADU Management tool allows users with the ADU Manager role to move data between ADUs. The ADU Management tool can be accessed by clicking on the ADU Management Tool icon found on the Org Admin > Organization page.



The ADU Management tool allows the following data to be moved to different ADUs:

  • Teams - It is possible to move a Team and it's members to another ADU. This may be useful for existing users when configuring ADUs for the first time, or for the general administration of the system. The option to move a team can be found from the Options menu of a Team Profile. When moving a team, the rules explained above must be kept intact. This means:
    • All team managers and approvers must be a member of the destination ADU, or any parent of. In the case where the manager is also a member of the team, this will always be the case.
    • The Leave Profiles assigned to each team member must exist in the destination ADU, or any parent of.
    • The Virtual Teams assigned to each team member must exist in the destination ADU, or any parent of.
  • Employees - Any user with the HR Admin role is able to register users into their ADU, so long as that users email address is available, and the user is not already activated in a different ADU. Users can be registered manually via a short form, or in bulk via a CSV upload. Users with the Admin role also have the ability to sync with the Google Apps domain. After registration, the user is available for activation. A user is activated by assigning them a Team Profile and Employment Profile. The Team Profile they are assigned will determine the ADU they belong to.
  • Company Documents - Company Documents can be created in different ADUs. When a user creates a new Company Document, it is created in the same ADU in which they reside. However, if this user has the HR Manager or ADU Manager role, assuming they have access to more than 1 ADU, an option will be provided to select which ADU the Company Document should be created.

    Company Documents are inherited down the ADU hierarchy. For example, a Company Document created in the root ADU is accessible to users in sub ADUs. This may be useful for company policy documents that are relevant to all employees in the company. If a Company Document is created in a sub ADU, then it is only accessible to users in that sub ADU (or, if the sub ADU has sub ADUs itself, then those too).

    Note that document level security is applied in addition to which ADU a Company Document is located.

Rules


In order to provide the most flexibility, Appogee HR allows data defined at a higher ADU to be inherited down the hierarchy. To ensure ease of administering ADUs it is important to understand the following rules when configuring ADUs within Appogee HR.


  • Teams:

    • Employees inherit the ADU from the Team they are a member of

    • Managers must reside in the same ADU as the Team, or any parent ADU (higher ADU in the hierarchical structure)

    • Approvers are a subset of managers, so same rules apply


  • Virtual Teams

    • Members can be any Employee from the same ADU, or any child ADU (lower ADU in hierarchical structure)

    • Managers must reside in the same ADU as the Team, or any parent

    • Approvers are a subset of managers, so same rules apply


  • Leave Profiles

    • An employee can be assigned a Leave Profile from the same ADU or any parent ADU.


  • Company Documents

    • Are assigned an ADU (usually the same ADU as the person creating it)

    • Are accessible to employees in the same ADU or child ADU


      Divisional Data Transfer Tool


      To begin moving data, you must select the type of data you wish to move, and the ADU from which data currently resides in (i.e. the source ADU):


      Once you have selected the data you wish to move, you can then click on the 'next' button to then select the destination ADU:


      Once you have specified the destination ADU, the next step will be the validation checks. This section will check to see if there's any issues with making this data move and will provide you with information of what data is failing the validation. You will receive the following message if the validation fails:


      You will receive a validation error, due to the following:

      1. If a team member is a manager of a team which is not accessible for the destination ADU
      2. If a team member is an owner of a company document which is not accessible for the destination ADU
      3. If a team member is in an employment profile which is not accessible by the destination ADU.

    • Once the validation has passed, you will receive the following message:


      By clicking on 'confirm move', the data will then be moved from the source ADU to the destination ADU specified.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.