7.3. Core Features and Constraints

7.3.1. Introduction

This section describes core capabilities and constraints of Room Booking Module. It may be useful to assess whether it meets your needs.

Note that Room Booking Module is NOT supposed to be a general purpose "room management" or "room booking" software.

It was built with _conference_ rooms in mind. Its main purpose is to make conference organization easier. We see room booking as a part of conference organization. (But you _can_ book rooms without defining an event).

7.3.2. Core Features

7.3.2.1. General

  • Standalone and "in-conference" mode.

    • Standalone mode allows you to book, manage bookings and do administration stuff. You don't have to create Indico event. (Bookings will not be assigned to any Indico event).

    • "In-conference" mode allows you to book rooms for your event. You can assign booked room to conference, lecture, meeting, session, contribution or break.

  • Repeating bookings ('every day', 'every week', 'every 3rd Wednesday of a month', etc).

  • E-mail notifications (to users and room managers, about every important action).

  • Three user roles: (1) Indico administrator, (2) room manager and (3) ordinary user.

  • Optional booking moderation. Each room may work in one of the following modes:

    • Bookings require explicit confirmation of room manager, or

    • Bookings are automatically accepted

7.3.2.2. User

  • Book a room

  • Manage own bookings (track, modify, cancel)

  • Search for rooms

  • Search for bookings (including archival)

7.3.2.3. Room Manager

  • Accept and reject PRE-bookings (for his room)

  • Reject bookings (for his room)

7.3.2.4. Indico Administrator

  • Switch on/off Room Booking Module

  • Configure room booking plugins in admin section

  • Add/remove location

  • Define room attributes specific to the location

  • Define possible room equipment specific to the location

  • Manage meeting rooms (add/modify/remove)

7.3.3. Constraints

The room must have its manager. It is not possible to define multiple managers for a single room. (You can workaround this by creating Indico account shared by several people).

The room must have defined its building, which must be a number. This is mandatory. If you don't need building, put any number there (like '0'). If your buiding naming scheme have letters, we are sorry - the software is not flexible enough for you.

The room must have defined floor (alphanumerical) and room 'number' (alphanumerical in fact).