In many organizations, the administrator may want to control what each user can do in the organization's MeetingBooster installation. Actions such as deleting past meetings, managing users and changing the organization's user group setup may result in disruptions and loss of information if performed by someone not authorized to do so, and for security reasons, not all users may be permitted to view other meetings than those they have created, or been invited to attend. To control what each user can and cannot do, you can set up security roles and assign them to your users as appropriate.
A security role is a list of permissions. For each permission, you can set different access levels. When you have created a security role and assigned it to a user, that user's options in MeetingBooster will be governed by the security role you have assigned to him/her and the permissions contained in that role.
There are two types of security roles in MeetingBooster: by user hierarchy and by user group. They are created in the same manner; the difference between them is that they provide the user with access rights based on different structures.
Security roles by user hierarchy define what the user can do in MeetingBooster based on that user's position in the user hierarchy. This is a traditional, top-down way of structuring access to information; usually, top-level users will be granted full access while users further down the hierarchy will have fewer access rights, or even none at all apart from certain default permissions such as viewing and participating in meetings. For more information, see "Managing user hierarchies".
Security roles by user group define what the user can do in MeetingBooster based on that user's position in his or her user group. User groups are flexible groups that can be set up as required and do not necessarily mirror the organization's user hierarchy or organization chart. As they may well be cross-functional and even cross-regional, user groups are a lot more flexible, and can be a lot more complex, than user hierarchies. For more information, see "Managing user groups".