> For the complete documentation index, see [llms.txt](https://docs.adaptiva.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adaptiva.com/anywhere/configmgr-settings/configmgr-settings-publication-settings.md).

# Publication

Publication is the process of preparing and storing ConfigMgr content so that it is accessible to the Adaptiva client. This allows all content transfers use Adaptiva's peer-to-peer technology.

There are two locations where you can choose to have content published:

* **Content Library**
  * Folder on the server where all on-premises content is located.
  * By default, clients will get this content via peer-to-peer sharing. However, if none of clients have a piece of content, they will retrieve it from the content library.
* **Cloud Storage**
  * Location in the cloud where content is stored permanently.
  * For internet based clients

Additionally, content is delivered through a Content Delivery Network (CDN), which provides temporary, geographically distributed caching for consistent global delivery. Content is published to Cloud Storage by the server and automatically replicated to the CDN as needed.

Publication Settings allow you to configure how to publish content for all or some individual content types. You can control which content is automatically published and published depending on priority.

In doing so, you can ensure more important content is prioritized to lessen the burden of downloading all types of content all of the time.

## Modify Publication settings globally

Select **Settings > Publication** from the side navigation.

### Auto-Publish Settings

{% hint style="info" %}
The Auto-Publish settings are an advanced topic. Please reach out to our [Support Team](https://adaptiva.com/support) for assistance.
{% endhint %}

In this section, you can add a workflow that publishes content based on certain criteria. For example, you may have server devices that are close to a Distribution Point that do not have the OneSite client's installed thus you do not need any content published in Adaptiva. You can define a workflow that can look at the source folder of the content and ignore anything that has 'server' in its path.

### Publication Settings

Publication settings lets you choose what content to automatically publish to Adaptiva for each piece of content. This includes future or existing content, or ONLY future content. For instance, you may want to publish only new OS images and not pull in existing OS images from ConfigMgr.

This setting also allows you to unpublish all existing content and prevent future content to be auto-published depending on your needs.

For more information regarding the individual content types, please see [Content Publication Settings](/anywhere/content-publication-settings.md#configmgr-content).

The following options are available for you to select.

{% hint style="info" %}
**Publish All Existing Content** cannot be selected by itself, and **Unpublish Published Content** is only available after deselecting **Automatically Publish Content**.
{% endhint %}

* **Automatically Publish Content**
  * Publishes future content going forward ONLY.
  * All new content will be auto-published, but no existing content will be published.
* **Publish All Existing Content**

  * Publishes future content going forward.

  AND

  * Retrieve all content already existing in ConfigMgr and then publish to Adaptiva.
* **Unpublish Published Content**
  * No longer going to publish future content.
  * Will unpublish existing content.

Click **Save**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.adaptiva.com/anywhere/configmgr-settings/configmgr-settings-publication-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.