3B Portals & Mobile App: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 5: Line 5:


== Initial Setup ==
== Initial Setup ==
Make sure that you are running the latest version of 3B Onboarding before following this guide.
=== Permissions ===
=== Permissions ===
Make sure that the Guest Site/Guest Community has the appropriate permissions. Since 3B Portals runs by default using a Guest User Profile, you need to grant access to the following resources to your running Guest Profile:
Make sure that the Guest Site/Guest Community has the appropriate permissions. Since 3B Portals runs by default using a Guest User Profile, you need to grant access to the following resources to your running Guest Profile:


* VisualForce Pages: b3o.Portal, b3o.FlowEmbeddedComponent
* VisualForce Pages: b3p.Portal, b3p.FlowEmbeddedComponent
* Apex Classes: b3o.GlobalRemotingRouter
* Apex Classes: b3p.GlobalRemotingRouter
* Any component specific Object/Field level permissions (check the [[3B Onboarding Portal Components]] documentation)
* Any component specific Object/Field level permissions (check the [[3B Onboarding Portal Components]] documentation)
* If you are embedding the portal in an iFrame outside of Salesforce, make sure to configure your [https://help.salesforce.com/s/articleView?id=sf.extend_code_cors.htm&type=5 CORS whitelist]
* If you are embedding the portal in an iFrame outside of Salesforce, make sure to configure your [https://help.salesforce.com/s/articleView?id=sf.extend_code_cors.htm&type=5 CORS whitelist]
* If using 3B Portals with 3B Onboarding, grant access to the page 3bo__P instead of 3bp__Portal


=== Custom Settings ===
=== Custom Settings ===
3B Portals requires that the "Portal" custom settings is present. You can enter your third party API keys and other base configuration in the custom settings. Here's a description of each config item in the custom settings:
3B Portals requires that the "Portal" custom settings is present. You can enter your third party API keys and other base configuration in the custom settings. Here's a description of each config item in the custom settings:


* Google Fonts API Key - this is the API key provided to you by your google admin. This is used for enabling custom fonts installation in the builder.
* API fields – elect a new API - only user. This user will be used for the communication between the portal and Salesforce
* GCM Key – do not update the default key. If the client wants to use their own GCM key for push notifications, you can update this field.
* Google Fonts API Key – do not update the default key. If the client wants to use their own Google Fonts API for portal fonts, you can update this field.
* Site URL – Important setting that will allow us to serve the portal, display custom components and more.


== Running and Embedding Portals ==
== Running and Embedding Portals ==