How to arrange the organisation tree in OfficeMail

The P/I OfficeMail organisation should reflect the reporting structure for company personnel using P/I OfficeMail. 
This may or may not be reflected in the company's AD directory structure. 
The primary purpose of the P/I OfficeMail organisation is to provide a framework for role based access control and for reporting usages by company and department. 
In addition, the structure allows for supervisors to authorise print jobs submitted by subordinates.

Note: supervisor would only able to authorise job from and generate job report for job submitted by subordinate within the department and sub-department.

The primary unit in the P/I OfficeMail organisation is the department. 
A department is a container unit similar to an AD Organisation Unit (OU). 
The tree must start with a department, a department can contain other departments or positions. 
Each created department contains one implied position of department manager which is created automatically. 
The department manager position may or may not have a user assigned to it.

Positions are used to represent the companies reporting structure within a department. 
Positions typically have a user assigned, but they may be vacant.
Positions provide a permanent structure that remains while users may change. 
There is no direct equivalent to positions in AD, as objects in an OU have no hierarchy within the OU. 
Objects in an OU can be members of a Group, but this just indicates membership, not hierarchy. 
The key difference is that a P/I OfficeMail department may have ten 'Tester' individual positions defined while a group, may have ten users that are 'Testers' and those ten users do not have to be in the same OU. 
It is not possible to create positions automatically from AD using the LDAP integration.

Users represent individuals who access the P/I OfficeMail system. 
Users are assigned to a position and then roles are assigned to a user.
In the organisation tree, each user will appears as:
This cannot be changed or removed.
By default, if drag and drop user to department (instead of position), it will automatically assign with position of "Manager".

Roles define the tasks a user can perform. 
In effect a role gives a specific right, such as the ability to log on to P/I OfficeMail or it can grant access to a set of resources, such as paper stocks or inserts. 
As well as access to resources, roles indicate whether a specific print submitted by a user needs authorisation and whether a particular user can authorise a particular print. 
There is a similarity to AD groups, but they are distinct; an AD group is used to indicate a collection of objects and assign the same right or rights to each object in the collection. 
A role is a collection of one or more rights that can be granted to a user. 
The role can be granted to more than one user, but each grant is an individual action. 
It is possible to use inheritance to grant roles to all users below a user and in this case the individual grants are applied automatically by the system.

More details can be found in Admin Webiste user guide.
Environment Details

UPDATED:  April 21, 2017