You are here:
Configure Digital Experiences Settings
Manage settings that apply to all sites built on Experience Cloud.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Applies to: LWR, Aura, and Visualforce sites |
| User Permissions Needed | |
|---|---|
| To change digital experience settings: | Customize Application |
- From Setup, enter Digital Experiences in the Quick Find box, then click Digital Experiences | Settings.
- Make your changes and save.
| Setting | Description |
|---|---|
| Experience Management | |
| Enable Experience Workspaces | Use Experience Workspaces to manage your sites. This setting is on by default, but you can disable it. |
| Assign new records created by guest users to the default owner | When enabled, all new records created by guest users are assigned to a default record owner. If no default record owner is chosen, the default record owner is the site’s owner. |
| Display warning for unsupported browsers | When enabled, users are asked to update or switch browsers when they access an Aura site with an unsupported browser. Display warnings are available by default in Lightning Web Runtime (LWR) sites. |
| Enable ExperienceBundle Metadata API | Provides access to the ExperienceBundle Metadata API, which allows text-based programmatic migration and creation of Aura sites. LWR sites use ExperienceBundle by default. |
| Role and User Settings | |
| Number of customer roles | You can have up to three roles. If you specify one customer role and then decide to increase the number of roles later, the increased number of roles isn’t applied to existing customer accounts. |
| Number of partner roles | When you enable the first external user on a partner account, a user role hierarchy is created for that account. The three roles are Partner User, Partner Manager, and Partner Executive. The role hierarchy rolls up to the account owner (typically, the channel manager). When you create contacts on the partner account and convert them to external users, assign one of these roles to them. If you specify one partner role and then decide to increase the number of roles later, the increased number of roles isn’t applied to existing partner accounts. |
| Allow editing of the Partner Account field on opportunities and leads | Select to allow partner users to edit the Partner Account field. |
| Enable Partner Super User Access | Granting super user access to users with Partner Community licenses lets them access more data and records, regardless of sharing rules and org-wide defaults. Super users can access data owned by other site users who have the same role or a role below them. Super user access applies only to cases, leads, custom objects, and opportunities. External users have access to these objects only if you expose them using profiles or sharing and add the tabs to the portal. |
| Enable report options for external users | Select this option to give external users with Partner Community or Customer Community Plus licenses and the “Run Reports” permission, access to report options on the run report page. |
| Let customer users access notes and attachments | Select to let customer users access notes and attachments on accounts and contacts. |
| Allow customer users to change case statuses | Let users with Customer Community Plus licenses change their case status in Visualforce sites. |
| Allow users to see contacts that haven’t been enabled for partner or customer accounts | Let users see contacts from private accounts that they have read access to when the contact is associated with the parent record of their own contact record. |
| Require unique usernames for partners in this org | Orgs created after Winter ’19 automatically contain username uniqueness at the org level. |
| Allow using standard external profiles for self-registration, user creation, and login | Each external license type is associated with a default profile in the org. Enable this setting to let external users self-register and log in with the default external profile. Salesforce best practice is to clone the default profile and add all the permissions needed to the cloned profile. |
| Hide first and last name fields in SOAP API for site users, when making API calls from within a site with nicknames enabled | This setting applies to SOAP API when used in an Aura controller that is invoked from a Lightning component on an Experience Cloud site. |
| Hide badges from guest users in Experience Builder sites | Hide badges used in gamification from guest users in Aura sites. |
| Moderation Rule Settings | |
| Moderation applies to all feed posts regardless of where they are visible | Apply moderation flags and rules to all feed posts, including those visible across multiple sites. When this setting is disabled, moderation applies only to site-specific feed posts. |
| Moderation rules can be configured for internal users’ feed posts on records | Apply moderation rules to internal users’ feed posts on records that might be visible across multiple sites. |
| Salesforce Mobile Settings for Experiences | |
| Support links to Visualforce pages from site pages made using Visualforce in the mobile app | Keep the Apex prefix in Experience Cloud site URLs so links between Visualforce pages resolve in Salesforce. Enabling this setting keeps the Apex prefix in all of your Experience Cloud site URLs. |
| New User Email Settings | |
| Link expires in [x] days | Select how many days you’d like an activation email to remain active. |
| Account Relationship Settings | |
| Enable Account Relationships | Enable to show Account Relationship objects and their associated sharing rules. After you enable this option, you can't disable it in your org. |
| External Account Hierarchy Settings | |
| Enable External Account Hierarchy | Enable to show External Account Hierarchy objects. After you enable this option, you can't disable it in your org. |
| Embedded Login | |
| Apply Login Page Type to Embedded Login | Applies the site’s login page type (default, Login Discovery, Experience Builder, or Visualforce) to its Embedded Login implementations. |
| Block Redirect to Unknown URL | For the site’s Embedded Login implementations, blocks redirects to unknown URLs that are provided in the state parameter of the OAuth response. Redirects are allowed only when the URL is in the same host or domain as the site or is allow-listed in the Embedded Login salesforce-allowed-domains meta tag. |
| Sharing Sets | |
| Create a sharing set | |
| Convert Site Member Access | |
| Convert Site Member Access | |
Did this article solve your issue?
Let us know so we can improve!
