Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

Follow these instructions to perform a clean install and configure Booker25

1. Install Booker25

You will find the latest installation link here: Install the latest version

Important! Make sure to always install “For Admins Only”.

2. Assign Licenses

Assign Booker25 licenses and Permission Sets to any user in your org that will work with the Booker25 calendar: 
Assign Licenses & Permission Sets

3. Remove Double Booking permission from System Administrator profile

When installing a package, Salesforce automatically assigns all custom permissions in that package to the System Administrator profile. This is fine for all permissions except the Double Booking permission, as this can give the impression that the conflict checking is not working. Only assign this permission deliberately to users who should always be able to double book.

  1. Go to Setup > Profiles

  2. Go to the System Administrator profile

  3. Under the Custom Permissions section, remove B25.Allow Double Booking

4. Set permissions

Enable real-time calendar updates

Make sure relevant users see updates on the calendar in real-time: 

Enable real-time calendar updates

(Optional) Add Reservation Contact permissions

If you intend to link multiple Contacts to Reservations, follow this article: 

Add Reservation Contact permissions

5. Start configuring Booker25

Add Resources to your org

Define a Resource Type and Resource hierarchy for your org: 

Set up the Resource Types & Resources hierarchy

Set up the reservation titles and hovers

Define what information should be shown on the Reservation blocks and the Reservation hovers: 

Customise the Reservation fields shown on the calendar and hovers

6. Migrating to a Sandbox

If you have Booker25 installed on your production org, and you create a partial sandbox, Booker25 will most likely not work properly. This is due to not all configuration records being copied to the sandbox. If you want to maintain your production org's Booker25 configuration, there are several options:

  1. Create a full copy sandbox.

  2. Create a partial sandbox and migrate all your Booker25 config data from production to the new sandbox.

  3. Create a partial sandbox and reset the Booker25 config data

The last option is fairly low effort and can be enough if you only want to test certain functionality. How to reset Booker25's configuration is described here:

Reset configuration data (Sandbox Refresh)




On this page:


  • No labels