In MeetingBooster, you can set up a user hierarchy to organize your users.
The basic structure of a user hierarchy is quite simple: one person is the manager of one or more other persons who may in turn be the managers of several others. This is a traditional, top-down tree structure that is easy to understand and which reflects the typical structure of many organizations. Once you have defined a user hierarchy in MeetingBooster, you will be able to set up security roles based on this user hierarchy. For more information, see "Understanding security roles" and "Assigning security roles".
In a normal user hierarchy, users do
not have any rights over users from other branches of the hierarchy. If
you need to set up more complex organizational structures than a traditional
user hierarchy (for cross-functional project groups, development teams,
task forces, or similar), set up a user group instead. For more information,
see "Managing user groups".
In MeetingBooster, a user hierarchy is set up by simply assigning managers for users. In other words, you define who a given user should report to, not which other users the given user is the manager of.
A manager relationship between two users
is also known as a dependency.
It may be helpful
to draw up a sketch of the organization's desired user hierarchy before
you start. This may help you visualize the structure you should set up.
Click Settings
and select Admin.
Click
User Management in the menu or
Users in the main window.
Select
a user to whom you want to assign a manager.
Click
the Manager field, select a manager
for the user in the dialog that opens, and click OK.
Click
Save.
The user selected in the Manager field is now the direct manager of the user edited. The user edited is listed on the Direct Reports tab of the manager's user profile.
Example: To set up a user hierarchy in which the user Adam Smith is the manager of the user Brian Jones, edit the user profile of Brian Jones, selecting Adam Smith in the Manager field. If you then need to make Brian Jones the manager of other users, simply edit those users, selecting Brian Jones in the Manager field of each one. Remember to save your changes as you go along.
You cannot select a manager who is lower
in the user hierarchy than the user being edited. In other words, in the
example above it would not be possible to make Brian Jones (or any user
below Brian Jones) the manager of Adam Smith unless you first removed
Adam Smith as the manager of Brian Jones (see "Deleting a user dependency"
below). You can only select managers who are on the same hierarchy level
or higher.
To remove the manager of a user:
Open
the user profile.
Click
the Manager field.
Select
[None] in the dialog that opens,
and click OK.
Click
Save.
If you delete only some of the dependencies
in the user hierarchy, all remaining dependencies are unchanged. For example
(continuing our example above), if you removed Adam Smith as the manager
of Brian Jones but did not remove
Brian Jones as the manager of Charlotte West, Charlotte West would still
report to Brian Jones, and Brian Jones would be moved to the top level
of the user hierarchy (because he no longer has a direct manager in the
user hierarchy). Always double-check that the user hierarchy looks and
works the way it should when editing or deleting dependencies.
If you remove all dependencies between
a manager and his reports so that he no longer has any reports, that user
still has any security roles by user hierarchy that you may have assigned
to him. To restore his default security role, edit his profile and remove
the now redundant security roles by user hierarchy.