Lightning Web Security and Content Delivery Network

Enable these Salesforce org settings so S-Docs Lightning components load reliably and perform as expected.

Enable these two Salesforce org settings before users work with the S-Docs Lightning components.

They affect how Salesforce loads component code and how that code runs on the page.

If either setting is off, users can see slow loads, inconsistent component behavior, or missing actions.

---

Why these settings matter

Lightning Web Security

Lightning Web Security is Salesforce's current client-side security model for Lightning components.

S-Docs Lightning components depend on this runtime to behave predictably inside Lightning pages.

When it is enabled:

• component code runs in the supported security model
• interactions with other Lightning page elements are more consistent
• users are less likely to hit rendering or runtime issues

When it is disabled:

• components may load inconsistently
• actions may not behave as expected
• troubleshooting becomes harder because the page is not using Salesforce's standard LWC security model

Content Delivery Network (CDN) for Lightning Component Framework

This setting controls how Salesforce serves the Lightning framework files used by the page.

When it is enabled:

• Lightning assets load faster
• component initialization is more reliable
• users, especially remote or Experience Cloud users, usually see better page performance

When it is disabled:

• framework files can take longer to load
• S-Docs components may feel slower to initialize
• first-load performance issues are more likely

---

How to correct the issue

1

Open Session Settings

In Salesforce Setup, enter session in Quick Find.

Open Session Settings.

2

Enable Lightning Web Security

Scroll to the Lightning Web Security section.

Enable Use Lightning Web Security for Lightning web components and Aura components.

3

Enable the Lightning CDN setting

Scroll to the top of the page.

Enable Content Delivery Network (CDN) for Lightning Component framework.

4

Save and retest

Click Save.

Refresh the Lightning record page that contains the S-Docs components.

Then verify that:

• Generate Documents (S-Docs) loads templates
• Documents (S-Docs) loads generated files
• actions such as preview, email, refresh, or versions behave normally

If the concern remains

Check these common follow-up items:

• both S-Docs components use the same Object API Name
• the components are placed on the correct record page
• the user has access to the required templates and generated documents

If you are configuring this for an Experience Cloud site, also review Configuring S-Docs Lightning Web Components in Experience Cloud.

These are Salesforce org-level settings.

After changing them, test with the same user profile that reported the issue.