> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/administration/install-configure/installation-upgrade-errors/content-delivery-requirements-for-fall-24-release-and-beyond.md).

# Content Delivery Requirements for Fall ’24 Release and Beyond

As of the **Fall ’24 release**, your Salesforce organization must have the Content Deliveries and Public Links feature enabled prior to installing or upgrading S-Docs. There is no workaround or option to install without this feature enabled.<br>

The Error You Will Encounter If this feature is disabled during installation or upgrade, the package will fail to install, and Salesforce will throw an error referencing the `ContentDistribution` object.

Error Example:

```
Invalid initializer type List<ContentDistribution> found for Map<Id, SObject>
```

**Why is this Required?** To support advanced document generation capabilities, the S-Docs core architecture now directly relies on the standard Salesforce `ContentDistribution` object.

**Steps to Resolve & Prevent**

1. Enable the Feature: Navigate to Setup > Content Deliveries and Public Links in your Salesforce org and enable the feature.
2. Verify Sandbox Environments: Sandbox refreshes often strip certain file preferences. Ensure this setting is enabled in your UAT/QA sandboxes prior to testing S-Docs.
3. Review Profile Permissions (Additional Note): Ensure the Salesforce profiles generating documents have standard Read/Create access to the `ContentDistribution` object. Without this, users may pass the installation gate but fail during document generation.
4. Re-attempt Installation: Once enabled, you can seamlessly proceed with the package installation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/sdocs/administration/install-configure/installation-upgrade-errors/content-delivery-requirements-for-fall-24-release-and-beyond.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
