TABLE OF CONTENTS
- Explanation of terms
- Configuration
- Behavior in the system
- This is how our customers use this
- More articles on this topic
Explanation of terms
Organizational unit
Organizational units are areas of responsibility of users and areas of validity of objects.
Users can see and select for actions only those objects that are within their scope of responsibility (and provided they have the necessary permissions). Objects can be selected only in the same scope.
Example
Correspondence templates for the "Hamburg" area of validity cannot be selected for applications in the "Munich" area of validity.
Organization level
Organizational units are arranged hierarchically in a tree structure. This structure extends in depth over so-called organizational levels.
Attention
In our authorization system, users only ever act downwards or on the same level, so that no one can exceed their authority. Elements that are created in the system, however, inherit the other way around. If a correspondence template should be selectable in every organizational unit, it must be created globally. It is exactly the same with locations.
If a location should be available everywhere, then it must be created on the top/global level.
You can read more about this here: View and action authorization
Configuration
Open the page Organizational Units or Organizational Levels. Here you can create organizational units, create organizational levels or edit both.
Behavior in the system
- The first and highest organizational level is often called Global. It contains exactly one organizational unit.
- You can create any number of additional organizational levels below it.
- Each organizational level holds any number of organizational units.
- Organizational units of the same level are isolated from each other in terms of permissions.
- Each organizational unit has a directly parent organizational unit, with the exception of Global.
- When assigning a directly parent organizational unit, organizational levels can be skipped.
- Data on organizational units can be evaluated via the oData Reporting API.
This is how our customers use this
By naming appropriate organizational levels and units, many customers have mapped their company structure. Often, the top level is still called global. Users often understand the implications better this way and we can provide support a little easier.
How the levels are named depends on the structure.
Examples
- Global, country, location, department
- Global, country, administrative unit, professional group
- Global, country, company
- Group, carrier, educational institution
- Administration, Destination, Hotel/Company