Page Comparison

Follow these steps to set up Booker25 in a Salesforce Digital Experience

Step-by-step guide

1. Set up you Salesforce Experience (former communities): https://resources.docs.salesforce.com/212/latest/en-us/sfdc/pdf/communities_dev.pdf

2. Once created, go to Setup and search for Digital Experiences

3. Next to the community you created, click Builder

4. Add a Booker25 Lightning Web Component to the page where you want to expose the calendar
   
   

   

   
   
   

5. Set the appropriate Booker25 objects External Sharing Model according to your organisation's needs:  https://help.salesforce.com/articleView?id=security_owd_external_setting.htm&type=5 (More information on licensing can be found in the next section) Booker25 Community Sharing Settings

6. Assign the a Booker25 license and permission set to your community users: Assign Licenses & Permission Sets

7. Enjoy your Booker25 Community!
   
   
   

   

Licensing

Our recommendation is to put in place Salesforce Community Plus licenses (or Partner licenses). Basic Community licenses will cause problems with access, as every Community user only has access to records from custom objects that have a lookup to their Account or Contact record. In most cases, every Community user needs access to all Booker25 Resources based on their availability. This means Resources need to be publicly accessible and thus shared with everyone. This in turn means the organization-wide sharing setting need to be set to Public Read/Write. Unfortunately this is not possible with sharing sets (which are used with basic Community users) as per the documentation:

The Available Objects list excludes: 

• Objects with an organization-wide sharing setting of Public Read/Write 

• Custom objects that don’t have an account or contact lookup field

This means if we set the Resource object to Public Read/Write, it will not be accessible to Community users when using Sharing Sets (which come with basic Community licenses). Community Plus licenses have full access to the Salesforce sharing model and will not cause this issue.

Related articles