Universal Scheduler

Site

The application should support multiple sites. Sites are containers for areas.

• Each site can be independent but the global admin would be able to make changes to all sites, areas, and child units, and the site admin would be able to make changes to all areas, and child units within a site.

Area

The application should support multiple areas within a site. Areas are containers for child units: each area must have at least one child unit.

• Each area can be independent from the other areas in a site, but the global admin and site admin permissions mentioned above would still apply, and the area admin would be able to make changes to all child units within an area.

Child Units

The application should support multiple child units within an area. Units are functionally the different entities that will be using the service are not simply containers. As such: every site/area must have at least one unit.

The services available by unit are:

• Room reservations
• Equipment reservations within a room
• Device reservations and checkout

Not all services may be available for all units: each unit should be configurable such that the unit admin would specifiy which services would be available. Multiples of each service should be possible. As an example: there may be separate room reservations services for conference rooms and classrooms.

Additional Admins

• Service Admin: Each service within a unit will needs it on admin.
• Service Desk Attendent: Each service will need a role for that allows only the options needed to manage the space: update reservations and such, but not the permissions to change any policies on the service: this will be used by the service desk support staff such as lab monitors