Zeitwart has a very differentiated rights and role system that can also be used to map a very complex organisation such as a university or a large company. In such a large organisation, there can be several thousand users who have just as many booking options. Typically, however, not all users have access to all resources. There are subgroups of users who are allowed to book subgroups of resources, for example, students on a certain course of study should be able to book certain PC workstations, employees should be able to book certain meeting rooms or members of the management should be able to book a company car with upscale equipment.

These many different authorisations can be maintained very poorly and unsatisfactorily in an elaborate and error-prone 1-to-1 relationship. With 1,000 users and 1,000 resources, there would be 1,000,000 possible relationships.

Roles

Zeitwert uses a role system, for one thing. Each user can belong to any number of roles, for example student, employee or member of the management. In the example, the user Clara Clever has the roles employee and management. Administrative rights are also assigned via roles, so there is also the classic admin role. Any number of roles can be created.

Organisational units

While users are organised into roles, resources are grouped into organisational units. Again, each resource can belong to any number of organisational units. In the example, all PCs within a PC pool, all meeting rooms and all company cars with upscale equipment are grouped together.

Rights between roles and organisational units

The rights are now defined in Zeitwart exclusively between the roles and the organisational units, never between individual users and individual resources. The role Student can be given booking rights to the organisational unit PC Pool. Thus, every user who has the role Student can book a PC in this pool.

Booking rules

In addition to the right to book, booking rules can be created that define the conditions under which members of a role can book the PCs: for example, opening hours, a maximum of 3 bookings per week and at least 24 hours before each booking. In this example, the role "employee" can access the PCs without restriction.

Hierarchical organisational units

The individual organisational units can additionally be organised hierarchically in a tree structure. For example, several PC pools can be combined in a common organisational unit PC pools. If booking rules such as opening hours are defined in this organisational unit, they automatically apply to all resources below it. Of course, exceptions can also be defined; the opening hours could be different in one of the pools. The assignment of rights between the roles and the organisational units also takes the hierarchical structure into account: if a role has the right to book for PC pools, they apply to all PCs below it according to the booking rules defined in each case.