βGetting started
Just a couple of steps and you'll be on your way.
Migrating from RBS 1.0
If your agency was invited to onboard to Resource Booking System (RBS) 2.0, it is especially important that you understand the following set up:
Your data will be automatically transferred over from the previous version of RBS. This includes your agency's existing:
Agency settings
Users and user groups
List of resources
Presets assigned to resources, such as additional services, availability schedules, booking usage, and built-in amenities
Bookings, past and present
Terminology
Some of the terms used in RBS 2.0 may be different from what youβre used to. Here's a list thatβs organised in alphabetical order for you to refer to.
Current term | Was previously called | Explanation |
---|---|---|
Resource item (Beverage) | Extra services that users can request for when they make a booking. To fulfil these requests, agencies may need to make prior preparations.
| |
Operating hour | Schedule that determines when a resource will be available for booking.
For example, weekdays from 9am to 6pm. | |
Availability schedule effective dates | Operating period | Dates where the availability schedule will take effect.
Dates are inclusive. For example, if the effective dates are |
Operating type: Session | Type of availability schedule where users must choose from fixed time slots, which the admin can customise. | |
Operating type: Interval | Type of availability schedule where users can choose the duration of their booking, as long as it's available. | |
Booking ID | Booking reference or ref. number | A unique combination of letters and numbers used to identify a specific booking. |
Booking owner | Booked for | The user who owns the booking, and can:
|
Resource item (Amenity) | A feature that's part of a
Examples include | |
Resource type | Second level in the hierarchy for the organisation of resources.
| |
Resource category | First and highest level in the hierarchy for the organisation of resources.
| |
User provisions | Permissions and settings configured at the user group level, specifically:
| |
User who made the booking | Booked by | The user who made the booking. This might be different from the booking owner if the user is making a booking on behalf of someone else. |
Last updated