> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/integrations/public-cdn-links/set-up-a-cdn-placeholder-for-expired-assets.md).

# Set up a CDN placeholder for expired assets

### What is the Expired Asset CDN Placeholder?

The **Expired Asset CDN Placeholder** allows Client Admins to set a replacement image (placeholder) for assets that are no longer permitted to be displayed via the CDN, such as assets that are **Deleted, Archived, Sensitive, or have an expired License**. 

When an asset falls to this states, its current CDN URL will no longer display the original image. Instead, the system can display the placeholder image configured in **Archive Settings**.

👉 Note: Editing Warning Indicator is an **Additional Feature** and must be enabled by a Client Admin in **Settings**. If your organization is unable to enable it, please contact the HIVO Support team.

<details>

<summary>This feature helps</summary>

* Prevent expired or no longer valid assets from continuing to appear on websites or integrated systems.
* Avoid broken images when an asset's CDN URL is no longer available.
* Allow organizations to use a replacement image that matches their branding or communicates the asset's status.

</details>

### How to Set Up the Expired Asset CDN Placeholder

#### **🔹** Step 1: Access Archive Settings

* Go to **Client Profile -> Settings ->  Archive Settings**.
* At the bottom of the page, locate the **Expired Asset CDN Placeholder** section.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FiUfMGzZyCFVKjL0SDSAY%2FGroup%201115.png?alt=media&amp;token=8a083362-f17d-473a-80be-4a2bd20e38a1" alt=""><figcaption></figcaption></figure>

#### **🔹** Step 2: Choose a Placeholder Image

Click **Choose Image** to upload the image you want to use as the placeholder.

* Supported formats: PNG, JPEG, GIF, WebP
* The maximum image size is **10 MB**.

Once uploaded, the image will appear in the preview area.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FJg1NRIV65hz3KHSGVaao%2FGroup%201113.png?alt=media&amp;token=6b73c38e-924a-4e58-808c-bfb541aca00b" alt=""><figcaption></figcaption></figure>

#### **🔹** Step 3: Change or Remove the Placeholder

* To replace the current image, click **Choose Image** and upload a new one.&#x20;
* If you no longer want to use the current image, click **Clear**, then save the Archive Settings again.

#### **🔹** Step 4: Save the Settings

* After selecting an image, click **Submit Archive Settings** to save your changes. This image will be used as the CDN placeholder for assets that are no longer eligible to display their original image.

The placeholder may be applied when an asset:

* **Deleted** asset
* Has been **Archived**.
* Is marked as **Sensitive**.
* Has an **expired License**.

In these cases, the CDN URL for the original image will be removed or will no longer be used to display the asset. The configured placeholder image will be displayed instead, helping ensure that content that is no longer valid does not continue to appear unintentionally on websites or in Connectors integrated with HIVO.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/integrations/public-cdn-links/set-up-a-cdn-placeholder-for-expired-assets.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.