Follow these steps to set up GoMeddo in a Salesforce Digital Experience
| Note |
|---|
Due to Salesforce limitations, the LWR Experience Cloud templates do not work wit GoMeddo. See this link to read about the Lightning Web Security limitations: https://developer.salesforce.com/docs/atlas.en-us.exp_cloud_lwr.meta/exp_cloud_lwr/template_limitations.htm. |
Step-by-step guide
...
Set up you Salesforce Experience (former communities): https://resources.docs.salesforce.com/212/latest/en-us/sfdc/pdf/communities_dev.pdf
...
Once created, go to Setup and search for Digital Experiences
...
Next to the community you created, click Builder
Add a GoMeddo Lightning Web Component to the page where you want to expose the calendar
...
Set the appropriate GoMeddo objects External Sharing Model according to your organisation's needs: GoMeddo Community Sharing Settings
...
Assign the a GoMeddo license and permission set to your community users: Assign Licenses & Permission Sets
...
Enjoy your GoMeddo Community!
...
| Info |
|---|
You can configure GoMeddo to be used by both authenticated and unauthenticated users in Experience Cloud. This articles elaborates on how to do this. |
Unauthenticated Access (Salesforce Guest User)
Follow this article to set up your Experience Cloud for unauthenticated users.
Authenticated Access
Follow this article to set up your Experience Cloud for authenticated users.
Most Relaxed Sharing Settings
This article elaborates on the most relaxed sharing settings for GoMeddo in Experience Cloud. It may be useful as a starting point, from where you can slowly restrict access depending on your needs.
Salesforce Licensing
Our recommendation is to put in place Salesforce Community Plus licenses (or Partner licenses). Basic Regular Community licenses will may cause problems with sharing 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 GoMeddo 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:
...
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 have this issuelimitation.
Related articles
| Filter by label (Content by label) | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Related issues |
|---|