This document provides an overview of Experience Builder in Salesforce Experience Cloud. It defines Experience Builder as a site builder that allows quickly creating and styling custom sites. It discusses how Experience Builder allows presenting different looks, pages, and data to different audiences based on criteria like location, permission, profile, record, and user. It provides an example of how the same URL can display completely different sites for two users and how Experience Builder supports multiple navigation menus. The document also covers guest user profiles and rules for access when records are created by guest users. Finally, it mentions custom theme layouts and other Experience Cloud capabilities like CMS Connect and Mobile Publisher.

1. Experience Builder
Walkthrough

2. About Me
Noor Alam Shuvo
- linkedin.com/in/noor-alam-shuvo
- https://trailblazer.me/id/noor

3. Sites Built On Experience
Cloud

4. Add some demo sites built
on Experience Cloud

6. Experience Cloud vs
Experience Builder

7. Experience Cloud
~ a platform that allows businesses to engage with their customers. Can build digital experiences
(Portal/Forum/Sites/CMS/Mobile Apps) by no-code, low-code, pro-code tools
- Marketing Sites
- Corporate Sites
- Partner Portals
- Communities
- Mobile Apps

8. Experience Builder
- A site builder in Experience Cloud
- Lets you quickly create and style your custom site

9. Experience Builder

13. Audience

14. Audience
~ is a group of users with one or more criteria
- present the same site with a different look and feel.
- Show different pages, components, or data to different audiences

15. Audience Criteria Type
● Location
● Permission
● Profile
● Record
● User

16. Page Variation

17. Two user put the same URL but got completely two
different sites

18. Multiple Navigation Menu
Demo

19. Guest User & Guest User
Profile

20. Use Case

21. Rules enforced for the Guest User
● Guest users cannot be the owner of newly created records or given ownership of existing records
● When a record is created by a guest user, the ownership must be transferred to a default owner
○ the default owner must be an active user in your org
● Guest users now cannot have more then read access to data
○ this can make things complicated as this means guest users do not have edit or delete access to objects
○ Guest users can only update or delete a record in System mode
● To get access to records a guest user sharing rule must be used
○ Again the maximum access granted through this sharing rule is Read
● A guest user cannot be a member of any queues or public groups
● A guest user can also not access records with manual sharing
○ it must be the guest user sharing rule

22. Custom Theme Layout

25. Others
- CMS Connect
- Mobile Publisher